RE: [Xen-users] Xen 3.1 kernel panics on RHEL4u5

Judging by the device ids listed (2920 and 2926), it seems like the following patch would solve my problem:

http://lists.xensource.com/archives/html/xen-changelog/2007-09/msg00310.html

I tried applying it from /linux-2.6.18-xen with 'patch p0 < patch_filename', but it errored out and said a file could not be found. Am I running the command correctly?

Thanks,

-Ryan

From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Ryan Persaud
Sent: Thursday, January 10, 2008 2:21 PM
To: Apparao, Padmashree K
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-users] Xen 3.1 kernel panics on RHEL4u5

I enabled all the SATA related options "y" in the .config and rebuilt the Xen kernel. I still got kernel panics. After examining the source of the ata_piix driver that comes with 2.6.18 (version 2.00), I noticed that my SATA controllers are not supported. What is the best way to include a more recent version (I need at least 2.00ac7) of that driver in my kernel? The documentation in the Xen manual for manually rebuilding the kernel is a bit sparse. Does anyone have a pointer to a more detailed description.

Thanks,

-Ryan

From: Apparao, Padmashree K [mailto:padmashree.k.apparao@xxxxxxxxx]
Sent: Wednesday, January 09, 2008 8:18 PM
To: Ryan Persaud
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-users] Xen 3.1 kernel panics on RHEL4u5

If the boot drive is a SATA then you must build it into the kernel, not as a module

Such as CONFIG_SCSI_SATA=y

Make all the SATA related as “y” in the .config and rebuild your xen kernel. If they are built as modules they will not be loaded until the kernel is booted (and of course the kernel cannot boot w/o SATA)

-Padma

From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Ryan Persaud
Sent: Wednesday, January 09, 2008 5:04 PM
To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Xen 3.1 kernel panics on RHEL4u5

Hello,

I am trying to install Xen 3.1 (with Linux kernel 2.6.18) from source on a machine running RHEL4u5 (2.6.9-55.ELsmp), but I am getting kernel panics. I've listed the KPs below. The first listing is with an initrd image specified, and the second one is without an initrd image. For the second listing, I am only including the portion that differs from the first.


With initrd image:
(XEN) Command line: /xen-3.1.gz dom0_mem=262144 com1=115200,8n1 console=com1
(XEN) 0000000000000000 - 000000000009f000 (usable)
(XEN) 000000000009f000 - 00000000000a0000 (reserved)
(XEN) 00000000000e0000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 000000007d5a0000 (usable)
(XEN) 000000007d5a0000 - 000000007d5ae000 (ACPI data)
(XEN) 000000007d5ae000 - 000000007d5f0000 (ACPI NVS)
(XEN) 000000007d5f0000 - 000000007d600000 (reserved)
(XEN) 00000000fed90000 - 00000000fed94000 (reserved)
(XEN) 00000000fee00000 - 00000000fee01000 (reserved)
(XEN) 00000000ffa78000 - 00000000ffa79000 (reserved)
(XEN) 00000000ffb00000 - 0000000100000000 (reserved)
(XEN) System RAM: 2005MB (2053372kB)
(XEN)   >>> ERROR: Invalid checksum
(XEN) Xen heap: 13MB (14244kB)
(XEN) Domain heap initialised: DMA width 32 bits
(XEN) Processor #0 6:15 APIC version 20
(XEN) Processor #1 6:15 APIC version 20
(XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
(XEN) Enabling APIC mode: Flat. Using 1 I/O APICs
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 2992.562 MHz processor.
(XEN) HVM: VMX enabled
(XEN) VMX: MSR intercept bitmap enabled
(XEN) CPU0: Intel(R) Core(TM)2 Duo CPU     E6850 @ 3.00GHz stepping 0b
(XEN) Mapping cpu 0 to node 255
(XEN) Booting processor 1/1 eip 90000
(XEN) Mapping cpu 1 to node 255
(XEN) CPU1: Intel(R) Core(TM)2 Duo CPU     E6850 @ 3.00GHz stepping 0b
(XEN) Total of 2 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN) -> Using new ACK method
(XEN) Platform timer is 1.193MHz PIT
(XEN) Brought up 2 CPUs
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Xen kernel: 64-bit, lsb, compat32
(XEN) Dom0 kernel: 64-bit, lsb, paddr 0xffffffff80200000 -> 0xffffffff805aee6c
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Dom0 alloc.:   000000007a000000->000000007b000000 (61440 pages to be all)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: ffffffff80200000->ffffffff805aee6c
(XEN) Init. ramdisk: ffffffff805af000->ffffffff80d7f000
(XEN) Phys-Mach map: ffffffff80d7f000->ffffffff80dff000
(XEN) Start info:    ffffffff80dff000->ffffffff80dff49c
(XEN) Page tables:   ffffffff80e00000->ffffffff80e0b000
(XEN) Boot stack:    ffffffff80e0b000->ffffffff80e0c000
(XEN) TOTAL:         ffffffff80000000->ffffffff81000000
(XEN) ENTRY ADDRESS: ffffffff80200000
(XEN) Dom0 has maximum 2 VCPUs
(XEN) Initrd len 0x7d0000, start at 0xffffffff805af000
(XEN) Scrubbing Free RAM: .................done.
(XEN) Xen trace buffers: disabled
(XEN) Std. Loglevel: Errors and warnings
(XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xe.
kernel direct mapping tables up to 10800000 @ e0b000-e91000
Bootdata ok (command line is root=/dev/sda3 ro console=ttyS0,115200 )
Linux version 2.6.18-xen (root@xxxxxxxxxxxxxxxxxxxxx) (gcc version 3.4.6 2006048
BIOS-provided physical RAM map:
Xen: 0000000000000000 - 0000000010800000 (usable)
DMI present.
>>> ERROR: Invalid checksum
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
ACPI: LAPIC (acpi_id[0x03] lapic_id[0x82] disabled)
ACPI: LAPIC (acpi_id[0x04] lapic_id[0x83] disabled)
ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Setting APIC routing to xen
Using ACPI (MADT) for SMP configuration information
Allocating PCI resources starting at 80000000 (gap: 7d600000:81790000)
Built 1 zonelists. Total pages: 67584
Kernel command line: root=/dev/sda3 ro console=ttyS0,115200
Initializing CPU#0
PID hash table entries: 2048 (order: 11, 16384 bytes)
Xen reported: 2992.562 MHz processor.
Console: colour VGA+ 80x25
Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
Software IO TLB enabled:
Aperture:     2 megabytes
Kernel range: ffff8800014fc000 - ffff8800016fc000
Address size: 25 bits
PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Memory: 242204k/270336k available (2014k kernel code, 19588k reserved, 870k dat)
Calibrating delay using timer specific routine.. 5986.35 BogoMIPS (lpj=29931761)
Security Framework v1.0.0 initialized
Capability LSM initialized
Mount-cache hash table entries: 256
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 4096K
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
SMP alternatives: switching to UP code
ACPI: Core revision 20060707
SMP alternatives: switching to SMP code
Brought up 2 CPUs
Initializing CPU#1
migration_cost=7
checking if image is initramfs...it isn't (bad gzip magic numbers); looks like d
Freeing initrd memory: 8000k freed
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: Using configuration type 1
ACPI: Interpreter enabled
ACPI: Using IOAPIC for interrupt routing
Error attaching device data
Error attaching device data
Error attaching device data
Error attaching device data
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Transparent bridge - 0000:00:1e.0
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 *10 12 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 10 12 14 *15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 7 10 12 14 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 *10 12 14 15)
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 12 *14 15)
ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 *7 10 12 14 15)
ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 *5 6 7 10 12 14 15)
ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 *5 6 7 10 12 14 15)
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
(XEN) ioapic_guest_write: apic=0, pin=4, old_irq=4, new_irq=4
(XEN) ioapic_guest_write: old_entry=000009f1, new_entry=000109f1
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
pnp: PnP ACPI: found 23 devices
xen_mem: Initialising balloon driver.
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
pnp: 00:09: ioport range 0xa20-0xa3f has been reserved
pnp: 00:09: ioport range 0xa00-0xa0f has been reserved
pnp: 00:09: ioport range 0xa10-0xa1f has been reserved
pnp: 00:09: ioport range 0xa40-0xa5f has been reserved
PCI: Ignore bogus resource 6 [0:0] of 0000:00:02.0
PCI: Bridge: 0000:00:1e.0
IO window: disabled.
MEM window: disabled.
PREFETCH window: disabled.
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 3, 32768 bytes)
TCP established hash table entries: 16384 (order: 6, 262144 bytes)
TCP bind hash table entries: 8192 (order: 5, 131072 bytes)
TCP: Hash tables configured (established 16384 bind 8192)
TCP reno registered
IA-32 Microcode Update Driver: v1.14a-xen <tigran@xxxxxxxxxxx>
audit: initializing netlink socket (disabled)
audit(1199920435.180:1): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
Real Time Clock Driver v1.12ac
Non-volatile memory driver v1.2
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
loop: loaded (max 8 devices)
Xen virtual console successfully installed as ttyS0
Event-channel device installed.
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
PNP: No PS/2 controller found. Probing ports directly.
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
mice: PS/2 mouse device common for all mice
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
NET: Registered protocol family 1
NET: Registered protocol family 17
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
RAMDISK: ext2 filesystem found at block 0
RAMDISK: Loading 8000KiB [1 disk] into ram disk... done.
VFS: Mounted root (ext2 filesystem).
Red Hat nash version 4.2.1.10 starting
Mounted /proc filesystem
Mounting sysfs
Loading ide-disk.ko module
Loading jbd.ko module
Loading ext3.ko module
Loading scsi_mod.ko module
SCSI subsystem initialized
Loading aacraid.ko module
Adaptec aacraid driver (1.1-5[2409]-mh2)
Loading sd_mod.ko module
Creating block devices
linuxrc[475]: segfault at 0000000000000000 rip 0000000000403698 rsp 00007fff0294
VFS: Cannot open root device "sda3" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
(XEN) Domain 0 crashed: rebooting machine in 5 seconds.

Without initrd image:

RAMDISK: ext2 filesystem found at block 0
RAMDISK: Loading 8000KiB [1 disk] into ram disk... done.
VFS: Mounted root (ext2 filesystem).
Red Hat nash version 4.2.1.10 starting
Mounted /proc filesystem
Mounting sysfs
Loading ide-disk.ko module
Loading jbd.ko module
Loading ext3.ko module
Loading scsi_mod.ko module
SCSI subsystem initialized
Loading aacraid.ko module
Adaptec aacraid driver (1.1-5[2409]-mh2)
Loading sd_mod.ko module
Creating block devices
linuxrc[475]: segfault at 0000000000000000 rip 0000000000403698 rsp 00007fff0294
VFS: Cannot open root device "sda3" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
(XEN) Domain 0 crashed: rebooting machine in 5 seconds.

Other relevant details:

[root@localhost rpersaud]# lsmod
Module                  Size Used by
nls_utf8                3649 1
vfat                   16833 1
fat                    50144 1 vfat
usb_storage            71561 1
parport_pc             29569 0
lp                     15345 0
parport                44493 2 parport_pc,lp
autofs4                27080 0
i2c_dev                13889 0
i2c_core               28865 1 i2c_dev
sunrpc                176313 1
ds                     21705 0
yenta_socket           23105 0
pcmcia_core            69969 2 ds,yenta_socket
dm_mirror              32201 0
dm_mod                 74153 1 dm_mirror
button                  9313 0
battery                11465 0
ac                      6985 0
md5                     5953 1
ipv6                  285089 10
joydev                 12224 0
uhci_hcd               35305 0
ehci_hcd               33989 0
hw_random               7393 0
snd_azx                20953 3
snd_hda_codec         164929 1 snd_azx
snd_pcm_oss            59897 0
snd_mixer_oss          21697 2 snd_pcm_oss
snd_pcm               110409 3 snd_azx,snd_hda_codec,snd_pcm_oss
snd_timer              29001 1 snd_pcm
snd                    63497 10 snd_azx,snd_hda_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer
soundcore              12641 2 snd
snd_page_alloc         13264 2 snd_azx,snd_pcm
e1000                 226316 0
floppy                 66065 0
sr_mod                 20965 1
ext3                  139089 2
jbd                    69745 1 ext3
ata_piix               18885 2
libata                125097 1 ata_piix
sd_mod                 19649 6
scsi_mod              145297 4 usb_storage,sr_mod,libata,sd_mod

[root@localhost rpersaud]# lspci
00:00.0 Host bridge: Intel Corporation DRAM Controller (rev 02)
00:02.0 VGA compatible controller: Intel Corporation Integrated Graphics Controller (rev 02)
00:03.0 Communication controller: Intel Corporation MEI Controller (rev 02)
00:03.2 IDE interface: Intel Corporation PT IDER Controller (rev 02)
00:03.3 Serial controller: Intel Corporation Serial KT Controller (rev 02)
00:19.0 Ethernet controller: Intel Corporation: Unknown device 10bd (rev 02)
00:1a.0 USB Controller: Intel Corporation USB UHCI Controller #4 (rev 02)
00:1a.1 USB Controller: Intel Corporation USB UHCI Controller #5 (rev 02)
00:1a.2 USB Controller: Intel Corporation USB UHCI Controller #6 (rev 02)
00:1a.7 USB Controller: Intel Corporation USB2 EHCI Controller #2 (rev 02)
00:1b.0 Audio device: Intel Corporation HD Audio Controller (rev 02)
00:1d.0 USB Controller: Intel Corporation USB UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation USB UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation USB UHCI Controller #3 (rev 02)
00:1d.7 USB Controller: Intel Corporation USB2 EHCI Controller #1 (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 92)
00:1f.0 ISA bridge: Intel Corporation LPC Interface Controller (rev 02)
00:1f.2 IDE interface: Intel Corporation 4 port SATA IDE Controller (rev 02)
00:1f.3 SMBus: Intel Corporation SMBus Controller (rev 02)
00:1f.5 IDE interface: Intel Corporation 2 port SATA IDE Controller (rev 02)

Some of the threads I've seen indicate that missing SATA support might be the culprit, but the SATA portions of my kernel configuration files seem to be identical in the relevant areas:

RHEL Kernel configuration:

# CONFIG_BLK_DEV_IDE_SATA is not set
# CONFIG_BLK_DEV_HD_IDE is not set
...
CONFIG_ATA=m
CONFIG_SATA_AHCI=m
CONFIG_SATA_SVW=m
CONFIG_ATA_PIIX=m
CONFIG_SATA_MV=m
CONFIG_SATA_NV=m
CONFIG_PDC_ADMA=m
CONFIG_SATA_QSTOR=m
CONFIG_SATA_PROMISE=m
CONFIG_SATA_SX4=m
CONFIG_SATA_SIL=m
CONFIG_SATA_SIL24=m
CONFIG_SATA_SIS=m
CONFIG_SATA_ULI=m
CONFIG_SATA_VIA=m
CONFIG_SATA_VITESSE=m
CONFIG_SATA_INTEL_COMBINED=y

Xen Linux configuration from xen-3.1.0-src/build-linux-2.6.18-xen_x86_64:

# CONFIG_BLK_DEV_IDE_SATA is not set
# CONFIG_BLK_DEV_HD_IDE is not set
...
CONFIG_SCSI_SATA=m
CONFIG_SCSI_SATA_AHCI=m
CONFIG_SCSI_SATA_SVW=m
CONFIG_SCSI_ATA_PIIX=m
CONFIG_SCSI_SATA_MV=m
CONFIG_SCSI_SATA_NV=m
CONFIG_SCSI_PDC_ADMA=m
CONFIG_SCSI_HPTIOP=m
CONFIG_SCSI_SATA_QSTOR=m
CONFIG_SCSI_SATA_PROMISE=m
CONFIG_SCSI_SATA_SX4=m
CONFIG_SCSI_SATA_SIL=m
CONFIG_SCSI_SATA_SIL24=m
CONFIG_SCSI_SATA_SIS=m
CONFIG_SCSI_SATA_ULI=m
CONFIG_SCSI_SATA_VIA=m
CONFIG_SCSI_SATA_VITESSE=m
CONFIG_SCSI_SATA_INTEL_COMBINED=y

My grub.conf (with initrd specified):

default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Red Hat Enterprise Linux ES (2.6.9-55.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.6.9-55.ELsmp ro root=/dev/sda3 rhgb quiet
initrd /initrd-2.6.9-55.ELsmp.img
title Red Hat Enterprise Linux ES-up (2.6.9-55.EL)
root (hd0,0)
kernel /vmlinuz-2.6.9-55.EL ro root=/dev/sda3 rhgb quiet
initrd /initrd-2.6.9-55.EL.img
title Xen 3.0 / XenLinux 2.6
root (hd0,0)
kernel /xen-3.1.gz dom0_mem=262144 com1=115200,8n1 console=com1
module /vmlinuz-2.6.18-xen root=/dev/sda3 ro console=ttyS0,115200
module /initrd-2.6.18-xen.img

Does anyone have any idea of what might be causing the kernel panics?

Thanks,

-Ryan

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

WARNING - OLD ARCHIVES

xen-users

RE: [Xen-users] Xen 3.1 kernel panics on RHEL4u5