From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003
Description of problem:
I get the message "usb-uhci.c: c interrupt, status 3" followed by various frame
numbers on all tty terminals. These messages started showing up after I updates
the kernel to the latest offered by RH on the RedHat Network.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Toggle to a tty (cntl-alt-f2, etc)
3.message appears, logged in or not.
Actual Results: I see the "usb-uhci.c: c interrupt, status 3" message.
Expected Results: Should not see the message.
I have a USB Logitech mouse and a microsoft wireless keyboard. Both seem to be
funtioning properly. The message is irritating and indicates that something is
not configured correctly. I did not see it prior to the kernel upgrade
Does this persist with 2.4.20-13.8?
At my system I saw this but only _after a warm reset_ from windows98SE.
I have 2.4.20-13.9 with and an Logitech USB Cordless MouseMan Optical.
it was necessary to press poweroff, to reset the machine wasn't enough.
It happened one time only
I am using 2.4.20-13.9 #1 Mon May 12 11:03:52 EDT 2003 i686 athlon i386
GNU/Linux now. I do not see this bug with this kernel.
I have an RH 7.2 that I just fully updated to current. It has a SanDisk SDDR-31
compact flash reader on it. This used to work with the previous kernel
(2.4.18-27.7). With the latest kernel that up2date installs for RH 7.2,
(2.4.20-13.7), I get:
Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0
SCSI device sda: 96385 512-byte hdwr sectors (49 MB)
sda: Write Protect is off
usb-uhci.c: interrupt, status 3, frame# 1383
I see that the poster had success with the -13.9 kernel. Is this kernel going
to be made available in the RH 7.2 channel?
the -13.7 and -13.9 kernels are nearly identical (the 13.7 one doesn't have the
nptl threading patch and is compiled with the 7.x gcc compiler)
Rick, please file a new bug. I don't want you to be mixed with keyboard/mouse
The message accompains thousands of unrelated scenarios, so SuSE simply
comment it out in order to prevent bugs like this. We ship it count-limited,
perhaps the count patch was lost.
In summary, it's a totally useless message, which never helps to debug anything
and only serves to confuse users. So, disregarding idiotic printout, most
users in this bug see no problem, but Rik expiriences a regression with SDDR-31.
The SDDR-31 is a supported device, well understood. His problem needs
its own bug.
Brad, please make sure that 2.4.20-18 does not regress for you,
and we'll close this.
I installed 2.4.20-18 today. After running it for about 1 hour, I have not seen
any usb-uhci.c messages at all. Looks good.