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/
Home Products Support Community News


[Xen-bugs] [Bug 1364] New: domU crashed with kernel panic when using md

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 1364] New: domU crashed with kernel panic when using md device
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Thu, 2 Oct 2008 05:34:28 -0700
Delivery-date: Thu, 02 Oct 2008 05:34:34 -0700
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/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx

           Summary: domU crashed with kernel panic when using md device
           Product: Xen
           Version: unspecified
          Platform: x86-64
        OS/Version: Linux-2.6
            Status: NEW
          Severity: critical
          Priority: P2
         Component: Hypervisor
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: shota@xxxxxxxxxx

Using Xen-3.3.0 with centos 5.2 x86_64, domU crashed while installing CentOS5.2
x86_64 domU.
During kickstart install, kernel panic ocurred and crashed.

below is a part of kickstart file
# Partition clearing information
clearpart --all --initlabel
part /boot --fstype ext3 --size=256 --ondisk=xvda
part raid.10 --size=100 --grow --ondisk=xvda
part raid.9 --size=100 --grow --ondisk=xvdb
raid pv.11 --fstype "physical volume (LVM)" --level=RAID1 --device=md0 raid.9
volgroup raidVG pv.11
logvol swap --fstype swap --name=swapLV --vgname=raidVG --size=1024
logvol / --fstype ext3 --name=rootLV --vgname=raidVG --size=4000 --grow

below is log.

 ----------- [cut here ] --------- [please bite here ] ---------
Kernel BUG at drivers/xen/blkfront/blkfront.c:567                     |         
invalid opcode: 0000 [1] SMP -----------------------------------------+         
last sysfs file: /block/ram0/dev                                                
CPU 0                                                                           
Modules linked in: dm_emc dm_round_robin dm_multipath dm_snapshot dm_mirror
dm_zero dm_mod lock_nolock gfs2 ext3 jbd msdos raid456 xor raid1 raid0 xenblk
xennet iscsi_ibft iscsi_tcp libiscsi scsi_transport_iscsi sr_mod sd_mod
scsi_mod ide_cd cdrom ipv6 xfrm_nalgo crypto_api squashfs pcspkr loop nfs
nfs_acl fscache lockd sunrpc vfat fat cramfs
Pid: 1661, comm: ldconfig Not tainted 2.6.18-92.el5xen #1
RIP: e030:[<ffffffff8825072b>]  [<ffffffff8825072b>]
RSP: e02b:ffff88000cb71bc8  EFLAGS: 00010046
RAX: 000000000000000b RBX: 0000000000000008 RCX: 0000000000000000
RDX: 000000000000000c RSI: 0000000000000000 RDI: 00000000000019c8
RBP: ffff88000f7515f0 R08: ffff880001a71e38 R09: 000007000000015d
R10: 0000070000000473 R11: ffffffff882505aa R12: ffff88000f770000
R13: ffff880001dcf370 R14: ffff880001a71e38 R15: ffff880003475b40
FS:  00002ad8a67a7cc0(0063) GS:ffffffff805ae000(0000) knlGS:0000000000000000
CS:  e033 DS: 0000 ES: 0000
Process ldconfig (pid: 1661, threadinfo ffff88000cb70000, task
Stack:  ffff88000f775968  ffff88000f770000  000000000f775a48  0000000000000339 
 0000000000000006  0000000880233446  0000000b00003000  ffffffff80501550 
 ffffffff00000001  ffff88000f775968 
Call Trace:
 [<ffffffff8025cd20>] generic_unplug_device+0x18/0x2b
 [<ffffffff8826929b>] :raid1:unplug_slaves+0x5d/0x98
 [<ffffffff80229229>] sync_page+0x0/0x42
 [<ffffffff882692f2>] :raid1:raid1_unplug+0x10/0x1d
 [<ffffffff88386b4b>] :dm_mod:dm_table_unplug_all+0x33/0x40
 [<ffffffff88384d71>] :dm_mod:dm_unplug_all+0x1d/0x28
 [<ffffffff8025eadf>] blk_backing_dev_unplug+0x54/0x5a
 [<ffffffff80229262>] sync_page+0x39/0x42
 [<ffffffff802636a7>] __wait_on_bit_lock+0x36/0x66
 [<ffffffff8024156f>] __lock_page+0x5e/0x64
 [<ffffffff8029b96f>] wake_bit_function+0x0/0x23
 [<ffffffff80213c11>] filemap_nopage+0x22a/0x322
 [<ffffffff80208dad>] __handle_mm_fault+0x440/0x11bd
 [<ffffffff802648a1>] _spin_lock_irqsave+0x9/0x14
 [<ffffffff80267374>] do_page_fault+0xf7b/0x12e0
 [<ffffffff8021cb3e>] vma_link+0xd0/0xfd
 [<ffffffff8020e1bb>] do_mmap_pgoff+0x637/0x7a2
 [<ffffffff80260823>] error_exit+0x0/0x6e

Code: 0f 0b 68 03 15 25 88 c2 37 02 49 8b 4d 00 48 2b 0d 18 63 43 
RIP  [<ffffffff8825072b>] :xenblk:do_blkif_request+0x181/0x384
 RSP <ffff88000cb71bc8>
 <0>Kernel panic - not syncing: Fatal exception

in xend.log,
[2008-10-02 17:11:34 3635] WARNING (XendDomainInfo:1617) Domain has crashed:
name=host2 id=2.

Configure bugmail: 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Xen-bugs mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-bugs] [Bug 1364] New: domU crashed with kernel panic when using md device, bugzilla-daemon <=