Hi list,
is this the correct place to report oopses? If not, ignore this.
On my testlab system all five paravirtualized linux guests oopsed after
~1d uptime, probably at the same time (log forensics show that all
oopses happened within one hour). There was probably no load at
oops-time. They did not die immediately, the opentwrt-domain survived
enough to run a final "ps" on its "xm console". I suspect my
test-pings
finally killed my guests.
Dom0 and Xen did not realize anything (dmesg, xm dmesg, xend.log,
xend-debug.log). But Dom0 seemed less responsive afterwards, at least
via ssh. I could boot all guests again without rebooting Dom0, let''s
see
how long they''ll live ...
I configured one guest with 4 NICs (did not work ;-), maybe that
triggered the oops?
The host is FC6 (xen-3.0.3-1.fc6, kernel-xen-2.6.18-1.2869.fc6), all
guests used the same kernelimage selfcompiled from Fedora''s
kernel-xen-2.6.18-1.2849 sources. Hardware is an intel core 2 duo E6600
(conroe?) on an intel G965 chipset.
/nils.
########################################################################
pc00:/# xm info
host : pc00.eonis.de
release : 2.6.18-1.2869.fc6xen
version : #1 SMP Wed Dec 20 15:28:06 EST 2006
machine : i686
nr_cpus : 2
nr_nodes : 1
sockets_per_node : 1
cores_per_socket : 2
threads_per_core : 1
cpu_mhz : 2400
hw_caps :
bfebfbff:20100000:00000000:00000140:0000e3bd:00000000:00000001
total_memory : 2023
free_memory : 806
xen_major : 3
xen_minor : 0
xen_extra : .3-0-1.2869.fc6
xen_caps : xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p
xen_pagesize : 4096
platform_params : virt_start=0xf5800000
xen_changeset : unavailable
cc_compiler : gcc version 4.1.1 20061011 (Red Hat 4.1.1-30)
cc_compile_by : brewbuilder
cc_compile_domain : build.redhat.com
cc_compile_date : Wed Dec 20 14:48:10 EST 2006
xend_config_format : 2
########################################################################
### guest 1 oops (centos) ##############################################
------------[ cut here ]------------
kernel BUG at drivers/xen/netfront/netfront.c:766!
invalid opcode: 0000 [#1]
last sysfs file: /block/sda1/dev
Modules linked in:
CPU: 0
EIP: 0061:[<c05005e1>] Not tainted VLI
EFLAGS: 00010082 (2.6.18-1.2849-xenU.2 #3)
EIP is at network_alloc_rx_buffers+0x19d/0x3f0
eax: c8b70000 ebx: c8b722c0 ecx: 0000fb70 edx: c06e0000
esi: c06e0280 edi: 00000000 ebp: c06e3080 esp: c06ebf28
ds: 007b es: 007b ss: 0069
Process xenwatch (pid: 7, ti=c06ea000 task=c00dfab0 task.ti=c06ea000)
Stack: c06e0000 00001e41 00000100 00000209 cfb70000 000000c9 cfd4c838
c06ebf64
00000037 000000c9 c05008bb 00000000 cfd1f960 00004417 00004417
c06e0280
c06e0000 cfd4c1f0 00000113 c0500ad5 c067f800 00000037 00000100
c067f800
Call Trace:
[<c05008bb>] xennet_set_tso+0x2a/0x4b
[<c0500ad5>] backend_changed+0x190/0x1cc
[<c04f905e>] otherend_changed+0x74/0x79
[<c04f78b0>] xenwatch_handle_callback+0x12/0x44
[<c04f828f>] xenwatch_thread+0xe7/0xfd
[<c0422c8d>] autoremove_wake_function+0x0/0x2d
[<c04f81a8>] xenwatch_thread+0x0/0xfd
[<c0422bd6>] kthread+0xad/0xdb
[<c0422b29>] kthread+0x0/0xdb
[<c04028a5>] kernel_thread_helper+0x5/0xb
======================Code: 14 66 0f b6 44 24 08 0f b7 f8 66 89 44 24 06 83 bc
be cc 04 00 00
00 74 1a eb 10 83 7c 24 14 00 0f 84 11 02 00 00 e9 61 01 00 00 <0f> 0b
fe 02 fa 59 5a c0 89 9c be cc 04 00 00 8d 86 d4 0c 00 00
EIP: [<c05005e1>] network_alloc_rx_buffers+0x19d/0x3f0 SS:ESP
0069:c06ebf28
########################################################################
### guest 2 oops (debian) ##############################################
------------[ cut here ]------------
kernel BUG at drivers/xen/netfront/netfront.c:766!
invalid opcode: 0000 [#1]
last sysfs file: /block/sda1/dev
Modules linked in:
CPU: 0
EIP: 0061:[<c05005e1>] Not tainted VLI
EFLAGS: 00010086 (2.6.18-1.2849-xenU.2 #3)
EIP is at network_alloc_rx_buffers+0x19d/0x3f0
eax: cede0000 ebx: cedea2c0 ecx: 0000ed1f edx: c06e0000
esi: c06e0280 edi: 00000000 ebp: c06e30e0 esp: c06ebf28
ds: 007b es: 007b ss: 0069
Process xenwatch (pid: 7, ti=c06ea000 task=c00dfab0 task.ti=c06ea000)
Stack: c06e0000 00002bc1 00000100 00000208 ced1f000 000000cc cfd4d838
c06ebf64
00000034 000000cc c05008bb 00000000 cfd80720 0000021b 0000021b
c06e0280
c06e0000 cfd4d1d8 00000188 c0500ad5 c067fa00 00000034 00000100
c067fa00
Call Trace:
[<c05008bb>] xennet_set_tso+0x2a/0x4b
[<c0500ad5>] backend_changed+0x190/0x1cc
[<c04f905e>] otherend_changed+0x74/0x79
[<c04f78b0>] xenwatch_handle_callback+0x12/0x44
[<c04f828f>] xenwatch_thread+0xe7/0xfd
[<c0422c8d>] autoremove_wake_function+0x0/0x2d
[<c04f81a8>] xenwatch_thread+0x0/0xfd
[<c0422bd6>] kthread+0xad/0xdb
[<c0422b29>] kthread+0x0/0xdb
[<c04028a5>] kernel_thread_helper+0x5/0xb
======================Code: 14 66 0f b6 44 24 08 0f b7 f8 66 89 44 24 06 83 bc
be cc 04 00 00
00 74 1a eb 10 83 7c 24 14 00 0f 84 11 02 00 00 e9 61 01 00 00 <0f> 0b
fe 02 fa 59 5a c0 89 9c be cc 04 00 00 8d 86 d4 0c 00 00
EIP: [<c05005e1>] network_alloc_rx_buffers+0x19d/0x3f0 SS:ESP
0069:c06ebf28
########################################################################
### guest 3 oops (debian) ##############################################
------------[ cut here ]------------
kernel BUG at drivers/xen/netfront/netfront.c:766!
invalid opcode: 0000 [#1]
last sysfs file: /block/sda1/dev
Modules linked in:
CPU: 0
EIP: 0061:[<c05005e1>] Not tainted VLI
EFLAGS: 00010086 (2.6.18-1.2849-xenU.2 #3)
EIP is at network_alloc_rx_buffers+0x19d/0x3f0
eax: c7790000 ebx: c77952c0 ecx: 00007112 edx: c06b0000
esi: c06b0280 edi: 00000000 ebp: c06b3340 esp: c0077f28
ds: 007b es: 007b ss: 0069
Process xenwatch (pid: 7, ti=c0076000 task=c068fab0 task.ti=c0076000)
Stack: c06b0000 00008861 00000100 00000208 c7112000 000000df c03a4838
c0077f64
00000021 000000df c05008bb 00000000 c03d7420 00000111 00000111
c06b0280
c06b0000 c03a4140 00000168 c0500ad5 c0682a00 00000021 00000100
c0682a00
Call Trace:
[<c05008bb>] xennet_set_tso+0x2a/0x4b
[<c0500ad5>] backend_changed+0x190/0x1cc
[<c04f905e>] otherend_changed+0x74/0x79
[<c04f78b0>] xenwatch_handle_callback+0x12/0x44
[<c04f828f>] xenwatch_thread+0xe7/0xfd
[<c0422c8d>] autoremove_wake_function+0x0/0x2d
[<c04f81a8>] xenwatch_thread+0x0/0xfd
[<c0422bd6>] kthread+0xad/0xdb
[<c0422b29>] kthread+0x0/0xdb
[<c04028a5>] kernel_thread_helper+0x5/0xb
======================Code: 14 66 0f b6 44 24 08 0f b7 f8 66 89 44 24 06 83 bc
be cc 04 00 00
00 74 1a eb 10 83 7c 24 14 00 0f 84 11 02 00 00 e9 61 01 00 00 <0f> 0b
fe 02 fa 59 5a c0 89 9c be cc 04 00 00 8d 86 d4 0c 00 00
EIP: [<c05005e1>] network_alloc_rx_buffers+0x19d/0x3f0 SS:ESP
0069:c0077f28
########################################################################
### guest 4 oops (openwrt/i386) ########################################
------------[ cut here ]------------
kernel BUG at drivers/xen/netfront/netfront.c:766!
invalid opcode: 0000 [#1]
last sysfs file: /block/sda1/dev
Modules linked in:
CPU: 0
EIP: 0061:[<c05005e1>] Not tainted VLI
EFLAGS: 00010082 (2.6.18-1.2849-xenU.2 #3)
EIP is at network_alloc_rx_buffers+0x19d/0x3f0
eax: c0050000 ebx: c005b600 ecx: 0000133d edx: c0690000
esi: c0690280 edi: 00000000 ebp: c0693100 esp: c0023f28
ds: 007b es: 007b ss: 0069
Process xenwatch (pid: 7, ti=c0022000 task=c0021ab0 task.ti=c0022000)
Stack: c0690000 00003321 00000100 00000208 c133d000 000000cd c0279838
c0023f64
00000033 000000cd c05008bb 00000000 c02974e0 0000027e 0000027e
c0690280
c0690000 c02791d0 00000168 c0500ad5 c06b6a00 00000033 00000100
c06b6a00
Call Trace:
[<c05008bb>] xennet_set_tso+0x2a/0x4b
[<c0500ad5>] backend_changed+0x190/0x1cc
[<c04f905e>] otherend_changed+0x74/0x79
[<c04f78b0>] xenwatch_handle_callback+0x12/0x44
[<c04f828f>] xenwatch_thread+0xe7/0xfd
[<c0422c8d>] autoremove_wake_function+0x0/0x2d
[<c04f81a8>] xenwatch_thread+0x0/0xfd
[<c0422bd6>] kthread+0xad/0xdb
[<c0422b29>] kthread+0x0/0xdb
[<c04028a5>] kernel_thread_helper+0x5/0xb
======================Code: 14 66 0f b6 44 24 08 0f b7 f8 66 89 44 24 06 83 bc
be cc 04 00 00
00 74 1a eb 10 83 7c 24 14 00 0f 84 11 02 00 00 e9 61 01 00 00 <0f> 0b
fe 02 fa 59 5a c0 89 9c be cc 04 00 00 8d 86 d4 0c 00 00
EIP: [<c05005e1>] network_alloc_rx_buffers+0x19d/0x3f0 SS:ESP
0069:c0023f28
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel