Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 140065 - "atkbd.c: Spurious ACK on isa0060/seri0..." infinitely repeated on boot
"atkbd.c: Spurious ACK on isa0060/seri0..." infinitely repeated on boot
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
All Linux
medium Severity high
: ---
: ---
Assigned To: Dave Jones
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2004-11-19 11:12 EST by Daniel Walsh
Modified: 2015-01-04 17:12 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-12-03 14:11:03 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Daniel Walsh 2004-11-19 11:12:00 EST
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):

How reproducible:

Steps to Reproduce:
1.  Boot the machine
Actual results:

Infinite loop, never finishes.
Expected results:

Additional info:
Comment 1 Rob Hughes 2004-11-21 13:55:01 EST
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.
Comment 2 Matthew Miller 2004-11-23 11:53:33 EST
We're seeing this in FC2 on an Asus P4S533-MX system *without* SATA. 

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

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_.
Comment 3 Matthew Miller 2004-11-23 13:41:02 EST
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?
Comment 4 Rob Hughes 2004-11-23 14:10:47 EST
I have "root=/dev/sda3" in my grub.conf. I'll try hde3 and see if 
that makes a difference.
Comment 5 Reinier Balt 2004-11-24 14:45:29 EST
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.
Comment 6 Rob Hughes 2004-11-25 09:35:34 EST
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.
Comment 7 Rob Hughes 2004-11-29 18:52:27 EST
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.
Comment 8 Daniel Walsh 2004-12-03 14:11:03 EST
kernel-2.6.9-1.681_FC3 is working for me now.
Comment 9 Matthew Miller 2004-12-03 14:20:21 EST
Daniel -- shall I open a separate bug for the "root=LABEL=/" problem?
To my knowledge, the latest kernel doesn't resolve that.
Comment 10 Daniel Walsh 2004-12-03 14:29:55 EST
Might be a good idea, since your bug is probably getting lost in the

Comment 11 Matthew Miller 2004-12-03 15:01:18 EST
Okay. Issue in comment #2 filed as bug #141791.

Note You need to log in before you can comment on or make changes to this bug.