[Xen-bugs] [Bug 96] DomU crashing on x86

[bugzilla-daemon@xxxxxxxxxxxxxxxxxxx]

http://bugzilla.xensource.com/cgi-bin/bugzilla/show_bug.cgi?id=96





------- Additional Comments From dbarrera@xxxxxxxxxx  2005-07-11 18:15 -------
David Wolinsky posted the following info out to the xen-devel mailing list. I
believe we are seeing the same problem. I am actually seeing this problem on
several machines, not just one as I had reported earlier

kernel BUG at mm/page_alloc.c:649!
invalid operand: 0000 [#1]
PREEMPT 
Modules linked in:
CPU:    0
EIP:    0061:[<c013c5c2>]    Not tainted VLI
EFLAGS: 00010202   (2.6.11.12-xen0) 
EIP is at buffered_rmqueue+0x26c/0x2c4
eax: 00000001   ebx: c17e2000   ecx: 00000000   edx: 000290eb
esi: c1521d74   edi: 00000000   ebp: c031aa1c   esp: c17e3ccc
ds: 007b   es: 007b   ss: 0069
Process kjournald (pid: 783, threadinfo=c17e2000 task=c16ff0a0)
Stack: c031aa00 c1521d74 00000000 00000001 c1521d74 c031aa00 00000000
00000050 
       00000000 c013c838 c031aa00 00000000 00000050 00000000 00000000
00000000 
       00000000 00000000 c16ff0a0 00000010 c031ad6c 00001594 00000000
00000000 
Call Trace:
 [<c013c838>] __alloc_pages+0x176/0x3de
 [<c01379b7>] find_or_create_page+0x65/0xb0
 [<c015a1f7>] grow_dev_page+0x34/0x166
 [<c015a3ba>] __getblk_slow+0x91/0x135
 [<c015a79c>] __getblk+0x3d/0x3f
 [<c01a758c>] journal_get_descriptor_buffer+0x43/0x92
 [<c01a3fa0>] journal_commit_transaction+0xa69/0x1319
 [<c0130a84>] autoremove_wake_function+0x0/0x4b
 [<c0130a84>] autoremove_wake_function+0x0/0x4b
 [<c02d6736>] schedule+0x346/0x5f5
 [<c0117469>] __wake_up+0x4f/0xaa
 [<c01a6a63>] kjournald+0xd9/0x27d
 [<c0130a84>] autoremove_wake_function+0x0/0x4b
 [<c0130a84>] autoremove_wake_function+0x0/0x4b
 [<c01094e6>] ret_from_fork+0x6/0x14
 [<c01a6980>] commit_timeout+0x0/0x9
 [<c01a698a>] kjournald+0x0/0x27d
 [<c0107795>] kernel_thread_helper+0x5/0xb
Code: ff ff 8d 46 2c 89 44 24 0c 8b 45 0c c7 44 24 04 00 00 00 00 89 14
24 89 44 24 08 e8 23 fb ff ff 03 46 1c 89 46 1c e9 f4 fd ff ff <0f> 0b
89 02 a9 7c 2e c0 e9 7c fe ff ff e8 11 a4 19 00 eb 8b e8 
 <1>Unable to handle kernel paging request at virtual address 00200200
 printing eip:
c0140bec
*pde = ma 00000000 pa 55555000
Oops: 0002 [#2]
PREEMPT 
Modules linked in:
CPU:    0
EIP:    0061:[<c0140bec>]    Not tainted VLI
EFLAGS: 00010297   (2.6.11.12-xen0) 
EIP is at free_block+0xb7/0xda
eax: c1521d8c   ebx: c103f1b8   ecx: 000df114   edx: 00200200
esi: c1521d80   edi: 00000001   ebp: 0000000c   esp: c036de0c
ds: 007b   es: 007b   ss: 0069
Process swapper (pid: 0, threadinfo=c036c000 task=c0314b20)
Stack: 00000069 00000000 c1521d9c c041ae10 df142000 00000000 c16b6860
c0140c5c 
       c1521d80 c041ae10 0000000c 0000000c c041ae00 df142000 00000000
c043c980 
       c014100e c1521d80 c041ae00 df37f480 df37f480 df37f480 c02815ed
df142000 
Call Trace:
 [<c0140c5c>] cache_flusharray+0x4d/0xcc
 [<c014100e>] kfree+0x9d/0xa8
 [<c02815ed>] kfree_skbmem+0x10/0x26
 [<c028168a>] __kfree_skb+0x87/0x11c
 [<c02cdec9>] packet_rcv_spkt+0x179/0x27e
 [<c0107537>] __dev_alloc_skb+0x23/0x39
 [<c02877f3>] netif_receive_skb+0x20e/0x235
 [<c021438d>] tg3_rx+0x24c/0x3d0
 [<c0214607>] tg3_poll+0xf6/0x259
 [<c0287aca>] net_rx_action+0x118/0x1b7
 [<c012004c>] __do_softirq+0x6c/0xf5
 [<c0120139>] do_softirq+0x64/0x77
 [<c0120205>] irq_exit+0x36/0x38
 [<c010d2e2>] do_IRQ+0x22/0x28
 [<c0105f1d>] evtchn_do_upcall+0x60/0x86
 [<c01097cc>] hypervisor_callback+0x2c/0x34
 [<c01075b0>] xen_idle+0x32/0x6b
 [<c0107619>] cpu_idle+0x30/0x3e
 [<c036e765>] start_kernel+0x1a0/0x1f7
 [<c036e307>] unknown_bootoption+0x0/0x1bc
Code: 43 14 66 89 44 4b 18 66 89 4b 14 8b 43 10 83 e8 01 85 c0 89 43 10
74 81 8d 46 0c 83 c7 01 8b 50 04 39 ef 89 58 04 89 03 89 53 04 <89> 1a
7c 8f 83 c4 0c 5b 5e 5f 5d c3 2b 46 3c 89 46 24 89 5c 24 
 <0>Kernel panic - not syncing: Fatal exception in interrupt
 (XEN) Domain 0 shutdown: rebooting machine.
(XEN) Reboot disabled on cmdline: require manual reset 



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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