Hi folks,
Yestoday, I run a testcase, 6 VMs restart every 10 minitues from 11:00 am to 16:30 pm until Dom0 crashed. Assertion 'list_empty(&vreq->next)' failed will lead to tapdisk2 process segfault, then Dom0 crashed!
Jun 27 16:31:05 r02k05014 kernel: device tap775.0 entered promiscuous mode Jun 27 16:31:05 r02k05014 kernel: eth0: port 13(tap775.0) entering forwarding state Jun 27 16:31:15 r02k05014 tapdisk2[4341]: Assertion 'list_empty(&vreq->next)' failed, line 1822, file tapdisk-vbd.c
Jun 27 16:31:15 r02k05014 kernel: tapdisk2[4341]: segfault at 0 ip 000000000040a24f sp 00007fff0d8acb70 error 6 in tapdisk2[400000+39000] Jun 28 18:58:09 r02k05014 syslogd 1.4.1: restart.
Any one who can give me some tips?
What will lead to Assertion 'list_empty(&vreq->next)' failed ?
xm info: release : 2.6.31.13
version : #3 SMP Fri Apr 30 15:10:24 CST 2010 machine : x86_64 nr_cpus : 16 nr_nodes : 2 cores_per_socket : 4
threads_per_core : 2 cpu_mhz : 2266 hw_caps : bfebfbff:28100800:00000000:00001b40:009ce3bd:00000000:00000001:00000000 virt_caps : hvm
total_memory : 24544 free_memory : 19693 node_to_cpu : node0:0,2,4,6,8,10,12,14 node1:1,3,5,7,9,11,13,15 node_to_memory : node0:7633
node1:12059 node_to_dma32_mem : node0:2996 node1:0 max_node_id : 1 xen_major : 4 xen_minor : 0
xen_extra : .0 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096
platform_params : virt_start=0xffff800000000000 xen_changeset : unavailable xen_commandline : console=com1,vga com1=115200,8n1 msi=1 dom0_mem=6144M dom0_max_vcpus=4 dom0_vcpus_pin iommu=off x2apic=off hap=0
cc_compiler : gcc version 4.1.2 20080704 (Red Hat 4.1.2-46) cc_compile_by : root cc_compile_date : Wed May 12 19:09:47 CST 2010 xend_config_format : 4
tsk
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|