Package: xen-3.0
Severity: important
While booting the DomU, it sometimes crashes, especially if the
vif-device is not up yet. I managed to get the console output (xm
console test), which I'll attach to this bug report. It seems it is some
kernel bug, but I'm not sure.
If you need more information, please tell me how to get it, and I will
try to post it.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-1-xen-686
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)
------------[ cut here ]------------
kernel BUG at drivers/xen/netfront/netfront.c:717!
invalid opcode: 0000 [#1]
SMP
Modules linked in: ext3 jbd mbcache processor
CPU: 0
EIP: 0061:[<c0211489>] Not tainted VLI
EFLAGS: 00010082 (2.6.18-1-xen-686 #1)
EIP is at network_alloc_rx_buffers+0x198/0x3bb
eax: 00000000 ebx: c3db6d80 ecx: 00002c86 edx: c0de0000
esi: c0de02c0 edi: c0de3150 ebp: c39e8838 esp: c0397f2c
ds: 007b es: 007b ss: 0069
Process xenwatch (pid: 7, ti=c0396000 task=c0393ab0 task.ti=c0396000)
Stack: c0de0000 00000000 00000100 00000209 c2c86000 000000cd c0397f64 00000033
000000cd c0211733 00000000 0000aba9 0000aba9 0000aba9 c0de02c0 c0de0000
c39e81d0 0000015b c0211943 c3919000 00000033 00000100 c3919000 c39dc3ff
Call Trace:
[<c0211733>] xennet_set_tso+0x2a/0x4b
[<c0211943>] backend_changed+0x186/0x1d2
[<c020a2d3>] otherend_changed+0x4f/0x54
[<c0208a92>] xenwatch_handle_callback+0x12/0x44
[<c02094d7>] xenwatch_thread+0x105/0x11b
[<c0129e5d>] autoremove_wake_function+0x0/0x2d
[<c02093d2>] xenwatch_thread+0x0/0x11b
[<c0129d8f>] kthread+0xc2/0xef
[<c0129ccd>] kthread+0x0/0xef
[<c010293d>] kernel_thread_helper+0x5/0xb
Code: 8b 14 24 89 53 14 0f b6 44 24 08 89 44 24 04 83 bc 86 d8 04 00 00 00 74
1a
eb 10 83 7c 24 14 00 0f 84 e1 01 00 00 e9 31 01 00 00 <0f>
0b cd 02 81 9b 2a c0
8b 54 24 04 8d 86 e0 0c 00 00 89 9c 96
EIP: [<c0211489>] network_alloc_rx_buffers+0x198/0x3bb SS:ESP 0069:c0397f2c
