I''ve been doing a lot of dm-userspace smash testing, and appear to have
uncovered an unrelated netfront bug. The following just showed up 3 guests
during initial boot (xendomains called on boot).
----------- [cut here ] --------- [please bite here ] ---------
Kernel BUG at drivers/xen/netfront/netfront.c:709
invalid opcode: 0000 [1] SMP
CPU 0
Modules linked in:
Pid: 8, comm: xenwatch Not tainted 2.6.16.13-xen #1
RIP: e030:[<ffffffff8024c3a6>]
<ffffffff8024c3a6>{network_alloc_rx_buffers+495}
RSP: e02b:ffff8800004e1df8 EFLAGS: 00010082
RAX: 0000000000000000 RBX: ffff88002f39dd80 RCX: 000000000002f29c
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000001040
RBP: ffff880000618500 R08: 0000000000000000 R09: 000000000002d352
R10: 0000000000000000 R11: 0000000000000000 R12: ffff880031e0d838
R13: ffff880000618628 R14: 0000000000000208 R15: ffff88000061dda0
FS: 00002acc8a46e720(0000) GS:ffffffff8046d000(0000) knlGS:0000000000000000
CS: e033 DS: 0000 ES: 0000
Process xenwatch (pid: 8, threadinfo ffff8800004e0000, task
ffff880000636100)
Stack: ffff880000618000 00008800004e1ed8 000000dc00000100 ffff8800007f1f68
00000000000000dc 0000002400636318 ffff880000636100 ffff8800006457e0
0000000000000001 ffff880000618000
Call Trace: <ffffffff8024c909>{backend_changed+456}
<ffffffff802407be>{xenwatch_thread+0}
<ffffffff8014095e>{keventd_create_kthread+0}
<ffffffff8023fdd9>{xenwatch_handle_callback+21}
<ffffffff802408eb>{xenwatch_thread+301}
<ffffffff80140d39>{autoremove_wake_function+0}
<ffffffff8014095e>{keventd_create_kthread+0}
<ffffffff802407be>{xenwatch_thread+0}
<ffffffff80140c02>{kthread+212}
<ffffffff8010b8ce>{child_rip+8}
<ffffffff8014095e>{keventd_create_kthread+0}
<ffffffff80140b2e>{kthread+0} <ffffffff8010b8c6>{child_rip+0}
Code: 0f 0b 68 13 94 30 80 c2 c5 02 4c 63 e2 48 8d bd 80 15 00 00
RIP <ffffffff8024c3a6>{network_alloc_rx_buffers+495} RSP
<ffff8800004e1df8>
Dom0 == Fedora Core 5
root@nibbler:~> xm info
host : nibbler.ltc.ibm.com
release : 2.6.16.13-xen
version : #1 SMP Thu Aug 24 16:19:01 EDT 2006
machine : x86_64
nr_cpus : 4
nr_nodes : 1
sockets_per_node : 2
cores_per_socket : 1
threads_per_core : 2
cpu_mhz : 3600
hw_caps : bfebfbff:20000800:00000000:00000180:0000659d
total_memory : 8190
free_memory : 4671
xen_major : 3
xen_minor : 0
xen_extra : -unstable
xen_caps : xen-3.0-x86_64
xen_pagesize : 4096
platform_params : virt_start=0xffff800000000000
xen_changeset : Thu Aug 24 14:16:22 2006 -0500 11223:e94865fc87a5
cc_compiler : gcc version 4.1.1 20060525 (Red Hat 4.1.1-1)
cc_compile_by : root
cc_compile_domain : (none)
cc_compile_date : Thu Aug 24 16:19:05 EDT 2006
xend_config_format : 2
-Sean
--
Sean Dague
IBM Linux Technology Center email: japh@us.ibm.com
Open Hypervisor Team alt: sldague@us.ibm.com
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
> I''ve been doing a lot of dm-userspace smash testing, and appear tohave> uncovered an unrelated netfront bug. The following just showed up 3guests> during initial boot (xendomains called on boot).Just to confirm, this was definitely during domain creation rather than restoring from a saved image? (which I think xendomains has an option to do) It might be interesting to print out requeue_idx in netfront.c just to check that it''s not thinking it needs to do ring recovery. Thanks, Ian> ----------- [cut here ] --------- [please bite here ] --------- > Kernel BUG at drivers/xen/netfront/netfront.c:709 > invalid opcode: 0000 [1] SMP > CPU 0 > Modules linked in: > Pid: 8, comm: xenwatch Not tainted 2.6.16.13-xen #1 > RIP: e030:[<ffffffff8024c3a6>] > <ffffffff8024c3a6>{network_alloc_rx_buffers+495} > RSP: e02b:ffff8800004e1df8 EFLAGS: 00010082 > RAX: 0000000000000000 RBX: ffff88002f39dd80 RCX: 000000000002f29c > RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000001040 > RBP: ffff880000618500 R08: 0000000000000000 R09: 000000000002d352 > R10: 0000000000000000 R11: 0000000000000000 R12: ffff880031e0d838 > R13: ffff880000618628 R14: 0000000000000208 R15: ffff88000061dda0 > FS: 00002acc8a46e720(0000) GS:ffffffff8046d000(0000) > knlGS:0000000000000000 > CS: e033 DS: 0000 ES: 0000 > Process xenwatch (pid: 8, threadinfo ffff8800004e0000, task > ffff880000636100) > Stack: ffff880000618000 00008800004e1ed8 000000dc00000100ffff8800007f1f68> 00000000000000dc 0000002400636318 ffff880000636100ffff8800006457e0> 0000000000000001 ffff880000618000 > Call Trace: <ffffffff8024c909>{backend_changed+456} > <ffffffff802407be>{xenwatch_thread+0} > <ffffffff8014095e>{keventd_create_kthread+0} > <ffffffff8023fdd9>{xenwatch_handle_callback+21} > <ffffffff802408eb>{xenwatch_thread+301} > <ffffffff80140d39>{autoremove_wake_function+0} > <ffffffff8014095e>{keventd_create_kthread+0} > <ffffffff802407be>{xenwatch_thread+0} > <ffffffff80140c02>{kthread+212} > <ffffffff8010b8ce>{child_rip+8} > <ffffffff8014095e>{keventd_create_kthread+0} > <ffffffff80140b2e>{kthread+0} <ffffffff8010b8c6>{child_rip+0} > > Code: 0f 0b 68 13 94 30 80 c2 c5 02 4c 63 e2 48 8d bd 80 15 00 00 > RIP <ffffffff8024c3a6>{network_alloc_rx_buffers+495} RSP<ffff8800004e1df8>> > Dom0 == Fedora Core 5 > > > root@nibbler:~> xm info > host : nibbler.ltc.ibm.com > release : 2.6.16.13-xen > version : #1 SMP Thu Aug 24 16:19:01 EDT 2006 > machine : x86_64 > nr_cpus : 4 > nr_nodes : 1 > sockets_per_node : 2 > cores_per_socket : 1 > threads_per_core : 2 > cpu_mhz : 3600 > hw_caps : bfebfbff:20000800:00000000:00000180:0000659d > total_memory : 8190 > free_memory : 4671 > xen_major : 3 > xen_minor : 0 > xen_extra : -unstable > xen_caps : xen-3.0-x86_64 > xen_pagesize : 4096 > platform_params : virt_start=0xffff800000000000 > xen_changeset : Thu Aug 24 14:16:22 2006 -050011223:e94865fc87a5> cc_compiler : gcc version 4.1.1 20060525 (Red Hat 4.1.1-1) > cc_compile_by : root > cc_compile_domain : (none) > cc_compile_date : Thu Aug 24 16:19:05 EDT 2006 > xend_config_format : 2 > > -Sean > > -- > Sean Dague > IBM Linux Technology Center email: japh@us.ibm.com > Open Hypervisor Team alt: sldague@us.ibm.com_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel