Description of problem:
I am getting the following error repeated infinitely on boot
Spurious ACK on isa0060/serio0. Some Program, like XFree86, might be
trying to access hardware directly
The machine works fine with original FC3 kernel.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot the machine
Infinite loop, never finishes.
Happening to me as well on all three FC3 (installed, 678, 681) kernels
I've tried. Unplugging all USB devices doesn't seem to make any
difference. I'm using a NForce2 chipset board from ASUS.
We're seeing this in FC2 on an Asus P4S533-MX system *without* SATA.
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
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_.
Hmmm. "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. Is this also the case on the FC3 systems, or
is this totally unrelated?
I have "root=/dev/sda3" in my grub.conf. I'll try hde3 and see if
that makes a difference.
I have the same problem. Dell Inspiron 3800 (no SMP, celeron 500, no SATA).
2.6.9-1.3 works fine, but 2.6.9-1.6 panics with the spurious ACK error.
When booting with root=/dev/hda1 the problem goes away.
I've tried this with root=/dev/sda3 and root=/dev/hde3. Neither worked for me.
This may, however, be related to bug 140367, which seems to be causing my drive
to fail to initilize.
Over the weekend, I booted the rescue cd, removed all kernel packages,
then rebooted again to the cd, chose install and had it install the
kernel and write a new grub config/MBR. Since then, the problem has
gone away and it boots fine, even with the 681 kernel.
kernel-2.6.9-1.681_FC3 is working for me now.
Daniel -- shall I open a separate bug for the "root=LABEL=/" problem?
To my knowledge, the latest kernel doesn't resolve that.
Might be a good idea, since your bug is probably getting lost in the
Okay. Issue in comment #2 filed as bug #141791.