Hi,
can anyone provide any pointers as to how to avoid this issue?
A CentOS 5.3 domU on snv_111 dom0 is crashing on bott unless I remove
/lib/modules/2.6.18-128.1.6.el5/kernel/drivers/xenpv_hvm
dom0:
haggis:~$ uname -a
SunOS haggis 5.11 snv_111 i86pc i386 i86xpv
Name: SUNWxvm
Summary: Hypervisor Header Files
Category: System/Virtualization
State: Installed
Publisher: dev
Version: 3.1
Build Release: 5.11
Branch: 0.111
Packaging Date: Tue Mar 31 09:19:53 2009
Size: 0.00 B
FMRI: pkg:/[email protected],5.11-0.111:20090331T091953Z
r...@haggis:~# prtdiag -v
System Configuration: Hewlett-Packard HP Compaq 8510w
BIOS Configuration: Hewlett-Packard 68MVD Ver. F.13 06/24/2008
==== Processor Sockets ====================================
Version Location Tag
-------------------------------- --------------------------
Intel(R) Core(TM)2 Duo CPU T7700 @ 2.40GHz U10
domU:
[r...@localhost ~]# uname -a
Linux localhost.localdomain 2.6.18-128.1.6.el5 #1 SMP Wed Apr 1 09:10:25 EDT
2009 x86_64 x86_64 x86_64 GNU/Linux
domUs last words:
type=1404 audit(1240132330.658:2): enforcing=1 old_enforcing=0 auid=4294967295
ses=4294967295
type=1403 audit(1240132332.558:3): policy loaded auid=4294967295 ses=4294967295
INIT: version 2.86 booting
Welcome to CentOS release 5.3 (Final)
Press 'I' to enter interactive startup.
Setting clock (utc): Sun Apr 19 11:12:22 CEST 2009 [ OK ]
Starting udev: Unable to handle kernel NULL pointer dereference at
0000000000000000 RIP:
[<ffffffff80064b3e>] _spin_lock+0x1/0xa
PGD d77e067 PUD c536067 PMD 0
Oops: 0002 [1] SMP
last sysfs file: /class/net/lo/type
CPU 0
Modules linked in: xen_vbd xen_vnif xen_balloon ide_cd 8139too parport_pc
xen_platform_pci cdrom 8139cp parport serio_raw i2c_piix4 mii pcspkr i2c_core
dm_raid45 dm_message dm_region_hash dm_log dm_mod dm_mem_cache ata_piix libata
sd_mod scsi_mod ext3 jbd uhci_hcd ohci_hcd ehci_hcd
Pid: 895, comm: modprobe Not tainted 2.6.18-128.1.6.el5 #1
RIP: 0010:[<ffffffff80064b3e>] [<ffffffff80064b3e>] _spin_lock+0x1/0xa
RSP: 0018:ffff81000d507ec0 EFLAGS: 00010292
RAX: 0000000000000001 RBX: ffff81000fa58470 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff8014954e RDI: 0000000000000000
RBP: ffff81000fa58448 R08: 000000001c3a7138 R09: ffffffff8014954e
R10: ffffffff803d9520 R11: ffffffff881cfcf4 R12: 0000000000000000
R13: ffffffff881de848 R14: 000000001c3a7138 R15: 000000001c3b08e0
FS: 00002b652c15b6e0(0000) GS:ffffffff803ac000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 0000000000000000 CR3: 000000000d0be000 CR4: 00000000000006e0
Process modprobe (pid: 895, threadinfo ffff81000d506000, task ffff81000d4cd0c0)
Stack: ffffffff8026f625 ffffffff80320730 ffff81000fa58448 ffff81000d05a500
ffffffff801b5267 ffffffff8014954e ffff81000fa58448 ffff81000d05a7c0
ffff81000d05a500 000000001c3b08e0 ffffffff801b540b ffff81000fa58448
Call Trace:
[<ffffffff8026f625>] klist_del+0x15/0x2a
[<ffffffff801b5267>] device_del+0x22/0x1a9
[<ffffffff8014954e>] kobject_release+0x0/0x9
[<ffffffff801b540b>] device_unregister+0x9/0x12
[<ffffffff881cf051>] :xen_platform_pci:xvd_dev_shutdown+0x55/0x84
[<ffffffff8824a014>] :xen_vbd:xlblk_init+0x14/0x18
[<ffffffff800a3ee4>] sys_init_module+0xaf/0x1e8
[<ffffffff8005d116>] system_call+0x7e/0x83
Code: ff 0f 0f 88 6c 01 00 00 c3 90 81 2f 00 00 00 01 74 05 e8 c3
RIP [<ffffffff80064b3e>] _spin_lock+0x1/0xa
RSP <ffff81000d507ec0>
CR2: 0000000000000000
<0>Kernel panic - not syncing: Fatal exception
_______________________________________________
xen-discuss mailing list
[email protected]
