I'm pulling this out of bug #140065, because it appears to be a separate issue. We're seeing this in FC2 on an Asus P4S533-MX system *without* SATA. And, separately, on a Dell Optiplex 270 (discovered since the earlier report). We get VFS: Mounted root (ext2 filesystem). VFS: Cannot open root device "LABEL=/" 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) followed by an infinite number of atkbd.c: Spurious ACK on isa0060/seri0. Some program, like XFree86, might be trying access hardware directly. The machine isn't SMP, but oddly, if we boot the SMP kernel, we get the panic message but _not_ the atkbd.c errors. Also very disturbing: this happens with the newest kernel-2.6.9-1.6_FC2, but kernel-2.6.9-1.3_FC2 works _fine_. Using "root=/dev/hda2" instead of "root=LABEL=/" solves the problem here -- not only does the system boot, but there's no "atkbd.c: Spurious ACK" messages. Messages on fedora-list seem to indicate that this has hit people on FC3 with kernel-2.6.9-1.681_FC3 too, but I haven't confirmed that myself.
did your initrd build ok after installing the kernel ?
The two systems where I've gotten reports of this aren't under my direct control, so I haven't checked completely. The initrd images did appear to be 800+k, instead of the clearly broken 12k img I got with the 1.2_FC3 kernel that one time. However, one of the systems (the Asus motherboard) was reinstalled from scratch and upgraded a second time in basically the same way, but has no problems, which does strongly point to something with the initrd (because, what else could it be...). I'll check the details of the other system hopefully tomorrow. Anything in particular I should be looking for to be wrong? Thanks!
The initrd _appears_ to be fine... I can attach it if that would be helpful....
Fedora Core 2 has now reached end of life, and no further updates will be provided by Red Hat. The Fedora legacy project will be producing further kernel updates for security problems only. If this bug has not been fixed in the latest Fedora Core 2 update kernel, please try to reproduce it under Fedora Core 3, and reopen if necessary, changing the product version accordingly. Thank you.