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

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

  • To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
  • Date: Thu, 15 Feb 2007 09:16:02 +0800
  • Delivery-date: Wed, 14 Feb 2007 17:15:29 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcdPZd1PRiWiMh0hR6eatwo259HKHwAtlXJiACBkQ+A=
  • Thread-topic: [Xen-devel] Taken fault at bad CS c000...

>From: Keir Fraser [mailto:Keir.Fraser@xxxxxxxxxxxx]
>Sent: 2007年2月14日 17:41
>On 13/2/07 11:55, "Tian, Kevin" <kevin.tian@xxxxxxxxx> wrote:
>> Xen-unstable has no such issue, which just happens on my local
>> version with PM patch sets. Though it's very likely to do with my
>> local changes, these changes are assumed to have no impact on
>> normal system running. So can anybody help a bit about
>> possible cause for such warning? Does it mean something wrong
>> in emulate_privilege_op before gpf_emulate_4gb?
>You've screwed something up so you are taking #GP(0) faults from vm86
>The warnings from Xen are only debug-level and are a side effect of this.
>So you need to investigate why these faults are happening in the first
> -- Keir

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.


Xen-devel mailing list



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