WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-bugs

[Xen-bugs] [Bug 558] New: dom0 crash during new xm-test 13_create_multin

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 558] New: dom0 crash during new xm-test 13_create_multinic_pos.test case
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Tue, 07 Mar 2006 07:13:59 +0000
Delivery-date: Tue, 07 Mar 2006 07:14:52 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=558

           Summary: dom0 crash during new xm-test
                    13_create_multinic_pos.test case
           Product: Xen
           Version: unstable
          Platform: Unspecified
        OS/Version: Linux-2.6
            Status: NEW
          Severity: critical
          Priority: P1
         Component: Hypervisor
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: ricardoz@xxxxxxxxxx
                CC: khoa@xxxxxxxxxx,niv@xxxxxxxxxx,pl@xxxxxxxxxx


Hardware Platform:
xSeries x460

OS:
SLES9 SP2 32bit and 64bit.

Test Tool:
xm-test

Description:

Jim Dykman wrote additional network test cases for xm-test. Qemu-dm crashes dom0
in 2 out of 4 runs of his 13_create_multinic_pos.test case. Attached is the
patch to be able to reproduce the problem.

This problem happens with 32bit and 64bit dom0s.

xm-test output:

Started domain 13_create_multinic_pos-1141488989
[dom0] Waiting 20 seconds for domU boot...
Console executing: ['/usr/sbin/xm', 'xm', 'console',
'13_create_multinic_pos-1141488989']
[13_create_multinic_pos-1141488989] Sending `input'
[13_create_multinic_pos-1141488989] Sending `ls'
[13_create_multinic_pos-1141488989] Sending `echo $?'
[dom0] Running `xm destroy 13_create_multinic_pos-1141488989'
Traceback (most recent call last):
  File "./13_create_multinic_pos.test", line 24, in ?
    domain.destroy()
  File
"/home/stekloff/work/HG/xen-unstable.hg/tools/xm-test/lib/XmTestLib/XenDomain.py",
line 218, in destroy
    ret, output = traceCommand(prog + cmd + self.config.getOpt("name"))
  File
"/home/stekloff/work/HG/xen-unstable.hg/tools/xm-test/lib/XmTestLib/Test.py",
line 98, in traceCommand
    status, output = commands.getstatusoutput(command)
  File "/usr/lib64/python2.3/commands.py", line 54, in getstatusoutput
    text = pipe.read()
KeyboardInterrupt
FAIL: 13_create_multinic_pos.test


dmesg output:

xenbr0: port 8(vif627.8) entering disabled state
device vif627.8 left promiscuous mode
xenbr0: port 8(vif627.8) entering disabled state
Eeek! page_mapcount(page) went negative! (-1)
  page->flags = 14
  page->count = 1
  page->mapping = 0000000000000000
----------- [cut here ] --------- [please bite here ] ---------
Kernel BUG at mm/rmap.c:555
invalid opcode: 0000 [1]
CPU 0
Modules linked in: video thermal processor fan button battery ac qla2300 qla2xxx
scsi_transport_fc
Pid: 519, comm: qemu-dm Not tainted 2.6.16-rc5-xen0 #2
RIP: e030:[<ffffffff8015d507>] <ffffffff8015d507>{page_remove_rmap+135}
RSP: e02b:ffff880014067bc8  EFLAGS: 00010286
RAX: 00000000ffffffff RBX: ffff8800014b5df8 RCX: 0000000000000000
RDX: 00000000ffffff01 RSI: 000000000001926c RDI: ffffffff8052f260
RBP: ffff880014067bd8 R08: 0000000000000000 R09: 0000000000000023
R10: 000000000000001f R11: 000000000000001e R12: ffff88000d6ff568
R13: 0000000000000000 R14: ffff8800014b5df8 R15: ffff88000a5acab0
FS:  00002ae1efafbde0(0000) GS:ffffffff80654000(0000) knlGS:0000000000000000
CS:  e033 DS: 0000 ES: 0000
Process qemu-dm (pid: 519, threadinfo ffff880014066000, task ffff8800175f5180)
Stack: ffff880014067bd8 00002aaaaacad000 ffff880014067cd8 ffffffff80154684
       0000000000000000 00002aaaaaeabfff 00002aaaaaeabfff 00002aaaaaeabfff
       00000000a91a2067 ffffffff00000000
Call Trace: <ffffffff80154684>{unmap_vmas+1764} <ffffffff8015abc2>{exit_mmap+98}
      <ffffffff801244b3>{mmput+35} <ffffffff80128e1c>{exit_mm+204}
       <ffffffff80129637>{do_exit+519} <ffffffff80130c22>{recalc_sigpending+18}
       <ffffffff801312b9>{__dequeue_signal+441}
<ffffffff80129d2d>{do_group_exit+205}
       <ffffffff801330e9>{get_signal_to_deliver+1433}
<ffffffff8010a22d>{do_signal+125}
       <ffffffff801755b7>{pipe_readv+663} <ffffffff8017564e>{pipe_read+30}
       <ffffffff8010af34>{sysret_signal+39} 
<ffffffff8010a9bf>{do_notify_resume+47}
       <ffffffff8010b1d5>{ptregscall_common+61}

Code: 0f 0b 68 3c f6 4a 80 c2 2b 02 48 c7 c6 ff ff ff ff bf 20 00
RIP <ffffffff8015d507>{page_remove_rmap+135} RSP <ffff880014067bc8>
 <1>Fixing recursive fault but reboot is needed!
Bad page state in process 'net.agent'
page:ffff8800014b5df8 flags:0x0000000000000014 mapping:0000000000000000
mapcount:-1 count:0
Trying to fix it up, but a reboot is needed
Backtrace:

Call Trace: <ffffffff8014a854>{free_hot_cold_page+228}
       <ffffffff8014a38d>{bad_page+93} 
<ffffffff8014a80d>{free_hot_cold_page+157}
       <ffffffff8014ac9b>{free_hot_page+11} <ffffffff8014b4a9>{__free_pages+41}
       <ffffffff8011812c>{pte_free+476} <ffffffff80152c1d>{free_pgd_range+1133}
       <ffffffff8015320b>{free_pgtables+139} <ffffffff8015abde>{exit_mmap+126}
       <ffffffff801244b3>{mmput+35} <ffffffff80128e1c>{exit_mm+204}
       <ffffffff80129637>{do_exit+519} <ffffffff80169494>{vfs_read+196}
       <ffffffff80129d2d>{do_group_exit+205} 
<ffffffff80129d42>{sys_exit_group+18}
       <ffffffff8010ae4d>{system_call+117} <ffffffff8010add8>{system_call+0}

-- 
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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-bugs] [Bug 558] New: dom0 crash during new xm-test 13_create_multinic_pos.test case, bugzilla-daemon <=