[Xen-bugs] [Bug 589] New: [xen-hvm] dom0 crash during xm-test networking tests

[bugzilla-daemon@xxxxxxxxxxxxxxxxxxx]

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=589

           Summary: [xen-hvm] dom0 crash during xm-test networking tests
           Product: Xen
           Version: unstable
          Platform: x86-64
        OS/Version: Linux
            Status: NEW
          Severity: critical
          Priority: P1
         Component: Hypervisor
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: ricardoz@xxxxxxxxxx
                CC: dsteklof@xxxxxxxxxx,khoa@xxxxxxxxxx,niv@xxxxxxxxxx,pl@us
                    .ibm.com


HW:
x460

OS:
Sles9 sp2 32bit

changeset:

cs9443

Test Tool:
xm-test

Description:

  Dom0 crashes during xm-test networking tests. The crash does not happen in
specific network test. I have seen it crash on 12_network_domU_tcp and
07_network..... tests.

Here is the output of serial console:

(XEN) (GUEST: 93) int13_harddisk: function 15, unmapped device for ELDL=81
(XEN) (GUEST: 93) *** int 15h function AX=E980, BX=E6F5 not yet supported!
(XEN) (GUEST: 93) int13_harddisk: function 02, unmapped device for ELDL=81
(XEN) (GUEST: 93) int13_harddisk: function 41, unmapped device for ELDL=81
(XEN) HVM_PIT: guest freq in cycles=3002337
Unable to handle kernel paging request at 000000000040025c RIP:
<ffffffff80141800>{run_workqueue+128}
PGD d750067 PUD b04b067 PMD d2ff067 PTE 0
Oops: 0002 [1] SMP
CPU 0
Modules linked in: xt_physdev iptable_filter ip_tables x_tables tun loop bridge
usbserial parport_pc lp parport sg st sr_mod joydev thermal processor fan button
battery ac ipv6 ehci_hcd ohci_hcd tg3 dm_mod
Pid: 26, comm: events/0 Not tainted 2.6.16-xen #1
RIP: e030:[<ffffffff80141800>] <ffffffff80141800>{run_workqueue+128}
RSP: e02b:ffff88000054de38  EFLAGS: 00010097
RAX: 0000000000400254 RBX: ffff880005b52328 RCX: 0000000000000000
RDX: ffff88001ee11f58 RSI: 0000000000000000 RDI: ffff88001ee11f40
RBP: ffff880005b52330 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000001 R12: ffff88001ee11f40
R13: 0000000000000004 R14: 0000000000000000 R15: 0000000000000020
FS:  00002b0436a936e0(0000) GS:ffffffff804c1000(0000) knlGS:0000000000000000
CS:  e033 DS: 0000 ES: 0000
Process events/0 (pid: 26, threadinfo ffff88000054c000, task ffff88001ee17710)
Stack: ffffffff8010722a ffff88001ee11f80 ffff88001ee11f58 ffff88001ee11f58
       ffff88001ee11f68 ffff88001ee11f40 ffff88000054dec8 0000000000000000
       0000000000000000 ffffffff80141a32
Call Trace: <ffffffff8010722a>{hypercall_page+554}
<ffffffff80141a32>{worker_thread+306}
       <ffffffff80127b70>{default_wake_function+0}
<ffffffff80127b70>{default_wake_function+0}
       <ffffffff80141900>{worker_thread+0} <ffffffff80145cf9>{kthread+217}
       <ffffffff8010bc96>{child_rip+8} <ffffffff80145c20>{kthread+0}
       <ffffffff8010bc8e>{child_rip+0}

Code: 48 89 50 08 48 89 02 48 89 6d 08 48 89 6d 00 e8 5c 21 22 00
RIP <ffffffff80141800>{run_workqueue+128} RSP <ffff88000054de38>
CR2: 000000000040025c

Message from syslogd@vmxdom2 at Sun Mar 26 21:39:37 2006 ...
vmxdom2 kernel: Oops: 0002 [1] SMP

Attached are all the files related to xen.

-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- 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