Changeset 14402 got me this (not doing anything different than the other times I''ve started the same Vista 64 bit image tho''): I have added a printk to see what seg is at the point of failure (if it happens again). But perhaps it''s obvius from the trace... (XEN) Xen BUG at svm.c:712 (XEN) ----[ Xen-3.0-unstable x86_64 debug=n Tainted: C ]---- (XEN) CPU: 1 (XEN) RIP: e008:[<ffff830000154fa3>] svm_get_segment_register+0xf3/0x110 (XEN) RFLAGS: 0000000000010212 CONTEXT: hypervisor (XEN) rax: ffff8300001a4e20 rbx: ffff830010f7331c rcx: ffff830000fdf000 (XEN) rdx: ffff830010f7331c rsi: 0000000000ff7b60 rdi: ffff8300001c0080 (XEN) rbp: 0000000000000001 rsp: ffff830000ff77f0 r8: ffff830010f7331c (XEN) r9: ffff830000ff7848 r10: 0000000000000000 r11: 000000000024da00 (XEN) r12: 0000000000ff7b60 r13: 0000000000000000 r14: 0000000000000008 (XEN) r15: ffff830000ff7848 cr0: 0000000080050033 cr4: 00000000000006f0 (XEN) cr3: 0000000055a20000 cr2: 000007feff0216a8 (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: 0000 cs: e008 (XEN) Xen stack trace from rsp=ffff830000ff77f0: (XEN) ffff83000016223e ffff830000ff7cf8 ffff83000016228b 0000000000000001 (XEN) 0000000000000008 ffff830000ff7cf8 ffff830000ff7ad0 0000000000000001 (XEN) 0000000000000000 0000000000000000 ffff8300001665c3 3fd0000010c0f025 (XEN) 0000000000000004 ffff8300001a3c40 0000000000000008 ffff830000ff7cf8 (XEN) ffff830000141f3a ffff830000ff78e8 ffff830000000049 00000000ffffffff (XEN) 0000000800000000 000000000013920a ffff830000fdf000 ffff830000ff7f02 (XEN) ffff830000139667 0000000000000003 ffff83000012f972 ffff8300001a0341 (XEN) ffff830000fda080 4600000000000296 ffff830000ff7b28 ffff8300001a3c40 (XEN) 00000000000000c3 0000000000000001 ffff830000139667 0000000000000000 (XEN) ffff83000012f972 ffff8300001a03a0 0000000000000096 ffff8300001c0080 (XEN) 0000000000000092 ffff830000ff7a38 0000000000000046 00000000000000b0 (XEN) ffff830000138de8 ffff830000ff7f28 ffff83000012cecb 0000000000000002 (XEN) ffff830000138c0d 0000000000000001 ffff83000012ce9b ffff830000ff7f28 (XEN) 0000000000000001 fffff80001ce4bed 0000000000000001 ffff830000ff7b57 (XEN) 0000000000000001 fffff98000a25d50 0000000000000000 0000000000000000 (XEN) 0000000000000001 ffff8300001a0ca0 0000000000000000 0000000000000bed (XEN) fffff80001ce4bed 0000000000000000 ffff83000016894c 00000000000000b0 (XEN) 0000000000000024 ffff8300001c0080 ffff830000ff7a38 fffff80001ce4bee (XEN) 00000000000000d2 fffff80001ce4bee 00000000000000ff ffff830046593000 (XEN) ffff830046594070 0000000000000000 0000000001ce4067 00000000000465a5 (XEN) Xen call trace: (XEN) [<ffff830000154fa3>] svm_get_segment_register+0xf3/0x110 (XEN) [<ffff83000016223e>] hvm_get_seg_reg+0x3e/0x50 (XEN) [<ffff83000016228b>] hvm_translate_linear_addr+0x3b/0x140 (XEN) [<ffff8300001665c3>] hvm_read+0x33/0xc0 (XEN) [<ffff830000141f3a>] x86_emulate+0x3f3a/0x6fb0 (XEN) [<ffff830000139667>] pit_overflow+0x17/0x40 (XEN) [<ffff83000012f972>] do_IRQ+0x1c2/0x1e0 (XEN) [<ffff830000139667>] pit_overflow+0x17/0x40 (XEN) [<ffff83000012f972>] do_IRQ+0x1c2/0x1e0 (XEN) [<ffff830000138de8>] smp_invalidate_interrupt+0x58/0xa0 (XEN) [<ffff83000012cecb>] invalidate_interrupt+0x2b/0x30 (XEN) [<ffff830000138c0d>] smp_send_event_check_mask+0x3d/0x50 (XEN) [<ffff83000012ce9b>] event_check_interrupt+0x2b/0x30 (XEN) [<ffff83000016894c>] guest_walk_tables+0x18c/0x390 (XEN) [<ffff83000014f15f>] hpet_read+0xef/0x150 (XEN) [<ffff83000014b110>] hvm_io_assist+0xa30/0xb20 (XEN) [<ffff830000166ab1>] shadow_set_l1e+0x171/0x1a0 (XEN) [<ffff83000016894c>] guest_walk_tables+0x18c/0x390 (XEN) [<ffff83000016a88e>] sh_page_fault__shadow_4_guest_4+0xc8e/0xd90 (XEN) [<ffff83000016894c>] guest_walk_tables+0x18c/0x390 (XEN) [<ffff83000015594b>] svm_cr_access+0x1cb/0x1250 (XEN) [<ffff830000157f0a>] svm_vmexit_handler+0x99a/0x1b10 (XEN) [<ffff83000011a13b>] add_entry+0xcb/0x100 (XEN) [<ffff83000011a13b>] add_entry+0xcb/0x100 (XEN) [<ffff830000151148>] vlapic_get_ppr+0x18/0xa0 (XEN) [<ffff830000151217>] vlapic_has_interrupt+0x47/0x70 (XEN) [<ffff83000014b894>] is_isa_irq_masked+0x34/0x90 (XEN) [<ffff830000151200>] vlapic_has_interrupt+0x30/0x70 (XEN) [<ffff83000014b972>] cpu_has_pending_irq+0x32/0x60 (XEN) [<ffff83000015a3f5>] svm_stgi_label+0x8/0x13 (XEN) (XEN) (XEN) **************************************** (XEN) Panic on CPU 1: (XEN) Xen BUG at svm.c:712 (XEN) **************************************** (XEN) -- Mats _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On 16/3/07 18:30, "Petersson, Mats" <Mats.Petersson@amd.com> wrote:> Changeset 14402 got me this (not doing anything different than the other > times I''ve started the same Vista 64 bit image tho''): > > I have added a printk to see what seg is at the point of failure (if it > happens again). But perhaps it''s obvius from the trace...If you can reliably repro this then I''m really interested to get to the bottom of what''s going on. I think this may be an emulator bug or memory corruption bug we''ve very occasionally seen on VMX too... -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
> -----Original Message----- > From: Keir Fraser [mailto:keir@xensource.com] > Sent: 16 March 2007 19:03 > To: Petersson, Mats; xen-devel@lists.xensource.com > Subject: Re: [Xen-devel] Bug at svm.c:712... > > > > > On 16/3/07 18:30, "Petersson, Mats" <Mats.Petersson@amd.com> wrote: > > > Changeset 14402 got me this (not doing anything different > than the other > > times I''ve started the same Vista 64 bit image tho''): > > > > I have added a printk to see what seg is at the point of > failure (if it > > happens again). But perhaps it''s obvius from the trace... > > If you can reliably repro this then I''m really interested to > get to the > bottom of what''s going on. I think this may be an emulator > bug or memory > corruption bug we''ve very occasionally seen on VMX too...It''s only happened once so far - I''ll keep an eye on it tho''. -- Mats> > -- Keir > > > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel