I've been trying to upgrade my kernel from 2.6.22.14-72.fc6. After some troubles I've made a couple of steps forward, but now I'm stuck. Symptom of failure in every case is essentially the same; final console messages for latest 2.6.25.20 build, for example, look like this: Write protecting the kernel text: 2836k Write protecting the kernel read-only data: 1124k Red Hat nash version 5.1.19.0.3 starting Mounting proc filesystem Mounting sysfs filesystem Creating /dev Creating initial device nodes Setting up hotplug. Creating block device nodes. Creating root device. Mounting root filesystem. mount: could not find filesystem '/dev/root' Setting up other filesystems. Setting up new root fs setuproot: moving /dev failed: No such file or directory no fstab.sys, mounting internal defaults setuproot: error mounting /proc: No such file or directory setuproot: error mounting /sys: No such file or directory Switching to new root and running init. unmounting old /dev unmounting old /proc unmounting old /sys switchroot: mount failed: No such file or directory Kernel panic - not syncing: Attempted to kill init! Building 2.6.22.19 failed to boot. Adding 'ide0=noprobe' to the boot options made it boot successfully. 2.6.23.17 had the same problem, with the same solution. 2.6.24.7 failed to boot, but 'ide0=noprobe' doesn't help. Adding 'irqpoll' (and not 'ide0=...') gets it to boot but fails to mount other partitions of the boot disk. Changing /etc/fstab to replace all occurrences of 'sda' with 'hda' gets it to boot succesfully and mount the partitions correctly. 2.6.25.20 fails to boot; 'ide0=noprobe' doesn't help, nor does 'irqpoll', nor does either version of /etc/fstab. I've also tried 'pci=routeirq' without success. 2.6.32.3 fails the same as 2.6.25.20, though I've tried fewer variations. (The idea is eventually to get up to "latest stable".) The drives reported by a successful 2.6.24.7 boot are: hda: WDC WD1600JS-08NCB1, ATA DISK drive hdd: HDS728080PLAT20, ATA DISK drive hdc: HL-DT-ST RW/DVD GCC-H20N, ATAPI CD/DVD-ROM drive (in that order). Full dmesg from the latest two successful boots are at: <http://crypt.org/kernel/dmesg-2.6.23.17> <http://crypt.org/kernel/dmesg-2.6.24.7> I've tried to cut the configs down as far as possible, to minimize the changes from one version to the next (and it's always possible I've cut out too much). Successful configs and latest failed attempt for 2.6.25 are at: <http://crypt.org/kernel/config-2.6.23.17> <http://crypt.org/kernel/config-2.6.24.7> <http://crypt.org/kernel/config-2.6.25.20> The two variants of /etc/fstab are: <http://crypt.org/kernel/fstab-sda> <http://crypt.org/kernel/fstab-hda> My PCI device list is: PCI ID Works? Vendor Device Driver Kernel 80862970 Yes Intel Corporation 82946GZ/PL/GL Memory Controller Hub intel-agp v2.6.25- 80862971 Intel Corporation 82946GZ/PL/GL PCI Express Root Port 80862972 Yes Intel Corporation 82946GZ/GL Integrated Graphics Controller i915 v2.6.32- 808627d0 Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 808627d2 Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 808627c8 Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 808627c9 Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 808627ca Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 808627cb Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 808627cc Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller 8086244e Yes Intel Corporation 82801 PCI Bridge i810_rng,hw_random 808627b8 Yes Intel Corporation 82801GB/GR (ICH7 Family) LPC Interface Bridge intel-rng,iTCO_wdt v2.6.25- 808627c0 Yes Intel Corporation 82801GB/GR/GH (ICH7 Family) SATA IDE Controller ata_piix v2.6.25- 808627da Yes Intel Corporation 82801G (ICH7 Family) SMBus Controller i2c-i801 v2.6.25- 14e4169a Yes Broadcom Corporation NetLink BCM5786 Gigabit Ethernet PCI Express tg3 v2.6.25- 13f60111 Yes C-Media Electronics Inc CM8738 snd-cmipci v2.6.25- I have tried to use BOOT_PRINTK_DELAY to see better what is going on with the failing boots, but setting 'lpj=2800000 boot_delay=10' gives me very slow startup (around 3-5 seconds per console line, and very bursty unless I also hack kernel/printk.c to move the boot_delay_msec() call to around the first call to _call_console_drivers() in call_console_drivers(). Then just before the interesting part it suddenly speeds up again, even if I hack out the "system_state != SYSTEM_BOOTING" check in boot_delay_msec(). I welcome any suggestions for how to get further, including how to get something useful out of boot_delay. Hugo van der Sanden -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
