WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Taken fault at bad CS c000...

To: "Tian, Kevin" <kevin.tian@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Taken fault at bad CS c000...
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Thu, 15 Feb 2007 08:13:43 +0000
Delivery-date: Thu, 15 Feb 2007 00:13:05 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <D470B4E54465E3469E2ABBC5AFAC390F9E1225@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcdPZd1PRiWiMh0hR6eatwo259HKHwAtlXJiACBkQ+AADtw0VQ==
Thread-topic: [Xen-devel] Taken fault at bad CS c000...
User-agent: Microsoft-Entourage/11.3.3.061214
On 15/2/07 01:16, "Tian, Kevin" <kevin.tian@xxxxxxxxx> wrote:

> Actually I provided wrong info. This also happens on xen-unstable
> even without my changes. The difference is that I set "loglvl=all" in
> modified tree while no such option for base xen-unstable (before
> Rev 13897 which print all). I also tried an old xen-unstable version
> (still, without any change) which uses a 2.6.16.33 xenlinux. After
> setting "loglvl=all", that debug info still jumps out once switching to
> X-windows. So this seems to happen on some box (like with 945
> chipset), and I'm suspecting vm86 emulation has something wrong
> there. Anyway, I'll do some investigation here.

Oh, hmmm, it may be that #GP(0) is a very common reason to exit VM86 mode. I
expect we print that line every time such an exit happens, and it may not
actually be a bug at all. It may be that logging line is too noisy, even for
debug logging level.

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel