[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] 2.6.29-rc7 pv_ops dom0 BUG / unable to handle kernel paging request
On Sat, Mar 07, 2009 at 10:09:16PM -0800, Jeremy Fitzhardinge wrote: > Pasi Kärkkäinen wrote: > >Hello! > > > >Latest git tree (updated some hours ago) boots up fine for me, xend can be > >started etc, but some time after starting kernel compilation I get the > >following BUG: > > > >http://pasik.reaktio.net/xen/pv_ops-dom0-debug/pv_ops-dom0-bootlog-19-xen331-linux-2.6.29-rc7-bug.txt > > > >(XEN) mm.c:2006:d0 Bad type (saw 28000001 != exp e0000000) for mfn 436a3 > >(pfn 3d0a3) > >(XEN) mm.c:707:d0 Error getting mfn 436a3 (pfn 3d0a3) from L1 entry > >00000000436a3063 for dom0 > >(XEN) mm.c:3640:d0 ptwr_emulate: could not get_page_from_l1e() > >BUG: unable to handle kernel paging request at c01cbd58 > >IP: [<c0405d2f>] xen_set_pte+0x8c/0x96 > > > > Well, that's bad news. It was trying to map a highmem pte page which > didn't have the Pinned bit set on its page, but Xen thought it was a > pinned pte page. Not sure how it could get into that state, but its > indicative of general memory corruption. > > What was going on at the time? Was dom0 busy? Were you running some domUs? > At that time I was compiling a kernel on dom0.. so dom0 was busy. No other domains running. -- Pasi > J > > >*pdpt = 000000003d1f0001 > >Oops: 0003 [#1] SMP > >last sysfs file: /sys/devices/pci0000:00/0000:00:1e.0/0000:06:01.0/class > >Modules linked in: ipt_MASQUERADE iptable_nat nf_nat bridge stp bnep sco > >l2cap bluetooth sunrpc ipv6 dm_multipath uinput > > ppdev floppy i2c_i801 pcspkr iTCO_wdt i2c_core iTCO_vendor_support > >pata_pdc2027x sata_promise parport_pc parport tg3 li > >bphy ata_generic pata_acpi [last unloaded: microcode] > > > >Pid: 325, comm: kswapd0 Not tainted (2.6.29-rc7-tip #10) P8SC8 > >EIP: 0061:[<c0405d2f>] EFLAGS: 00010206 CPU: 0 > >EIP is at xen_set_pte+0x8c/0x96 > >EAX: c01cbd58 EBX: 000e133a ECX: 00000000 EDX: 00000000 > >ESI: 436a3063 EDI: 0003d0a3 EBP: e2152d8c ESP: e2152d78 > > DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0069 > >Process kswapd0 (pid: 325, ti=e2152000 task=e219a610 task.ti=e2152000) > >Stack: > > 00000000 c01cbd58 3d0a3063 c01cbd58 0003d0a3 e2152db4 c0427ff5 00000000 > > 80000000 00000163 f57ff000 0000000f c19d3460 0000000f c1232000 e2152dcc > > c0404d91 00000163 80000000 436a3067 0a078000 e2152df4 c0489c17 00000000 > >Call Trace: > > [<c0427ff5>] ? kmap_atomic_prot+0x1cd/0x1ef > > [<c0404d91>] ? xen_kmap_atomic_pte+0x2f/0x36 > > [<c0489c17>] ? page_check_address+0x7f/0x131 > > [<c0489d71>] ? page_referenced_one+0x4b/0xe9 > > [<c048aa4b>] ? page_referenced+0x7d/0xee > > [<c047b3f0>] ? shrink_active_list+0x10b/0x29c > > [<c0422bfe>] ? pvclock_clocksource_read+0x48/0xa3 > > [<c0407410>] ? __xen_spin_lock+0xc4/0xd8 > > [<c047c27b>] ? shrink_zone+0x285/0x29a > > [<c047c77a>] ? kswapd+0x3b6/0x53d > > [<c047aa07>] ? isolate_pages_global+0x0/0x19e > > [<c04480cf>] ? autoremove_wake_function+0x0/0x33 > > [<c047c3c4>] ? kswapd+0x0/0x53d > > [<c0447e03>] ? kthread+0x3b/0x61 > > [<c0447dc8>] ? kthread+0x0/0x61 > > [<c04097c7>] ? kernel_thread_helper+0x7/0x10 > >Code: f3 ab c6 05 9c 33 8d c0 00 8b 1d fc 32 8d c0 e8 2d cb 01 00 8b 55 ec > >48 0f 94 c0 0f b6 c0 01 d8 a3 fc 32 8d c0 8b > >45 f0 89 50 04 <89> 30 8d 65 f4 5b 5e 5f 5d c3 55 89 e5 57 56 89 c6 53 89 > >d3 > >83 > >EIP: [<c0405d2f>] xen_set_pte+0x8c/0x96 SS:ESP 0069:e2152d78 > >CR2: 00000000c01cbd58 > >---[ end trace b993ac68a500f37e ]--- > >.. > >.. > > > >.. and a lot of other stuff after this. > > > >-- Pasi > > _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |