[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

  • To: "Tian, Kevin" <kevin.tian@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • 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
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcdPZd1PRiWiMh0hR6eatwo259HKHwAtlXJiACBkQ+AADtw0VQ==
  • Thread-topic: [Xen-devel] Taken fault at bad CS c000...

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 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



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.