usb-uhci.c problems in latest kernels?
Quoted 1 line
usb-uhci.c: interrupt, status 3, frame# 1876
This is a known problem, here is the discussion that I initiated on linux-usb-devel:
http://marc.theaimsgroup.com/?t=98609508500001&w=2&r=1
The right fix is to comment that printout out. In fact, that is what I commited for Red Hat 7.1 release.
Some people suggest to switch to uhci instead of usb-uhci, which helps precisely because it does not have a corresponding printk.
-- Pete
Quoted 9 lines · Pete Zaitcev
Quoted 1 line
usb-uhci.c: interrupt, status 3, frame# 1876This is a known problem, here is the discussion that I initiated on linux-usb-devel:
http://marc.theaimsgroup.com/?t=98609508500001&w=2&r=1
The right fix is to comment that printout out. In fact, that is what I commited for Red Hat 7.1 release.
I'm not sure of that. Sometimes keys get "stuck" in the down position with my USB keyboard (mechanical switches, so the keys themselves are not sticking) and usually when that happens I can find a line like the one quoted above in the logs. Also, occasionally my mouse goes black (one of the optical Logitech's) with a similar line and must be disconnected and reconnected to work again. Again, similar line in the logs.
Nothing fatal happens. Pressing another key fixes the keyboard and my old fashioned USB ball mouse ;) works fine.
Quoted 3 lines
Some people suggest to switch to uhci instead of usb-uhci, which helps precisely because it does not have a corresponding printk.
I've seen similar suggestions for people with AMD-based systems.
Signature · 4 lines
Joseph Carter <[email protected]> Free software developer Change the Social Contract? BWAHAHAHAHAHAHAHAHAHAHAHA. -- Branden Robinson
Quoted 12 lines
Date: Sun, 15 Apr 2001 04:38:37 -0700
From: Joseph Carter <[email protected]>
To: Pete Zaitcev <[email protected]>
Cc: [email protected], [email protected]Quoted 7 lines
Quoted 1 line
usb-uhci.c: interrupt, status 3, frame# 1876This is a known problem, here is the discussion that I initiated on linux-usb-devel:
Quoted 7 lines
Quoted 2 lines
The right fix is to comment that printout out. In fact, that is what I commited for Red Hat 7.1 release.
I'm not sure of that. Sometimes keys get "stuck" in the down position with my USB keyboard (mechanical switches, so the keys themselves are not sticking) and usually when that happens I can find a line like the one quoted above in the logs. [...]
The printout is a valuable diagnostic tool for hacking but is useless for a user (actually dangerous, as it brings computers down with /var overflow). The best option would be to have it configurable with a module parameter.
-- Pete
Quoted 9 lines · Pete Zaitcev
Quoted 4 lines
I'm not sure of that. Sometimes keys get "stuck" in the down position with my USB keyboard (mechanical switches, so the keys themselves are not sticking) and usually when that happens I can find a line like the one quoted above in the logs. [...]
The printout is a valuable diagnostic tool for hacking but is useless for a user (actually dangerous, as it brings computers down with /var overflow). The best option would be to have it configurable with a module parameter.
That sounds like a good idea actually, under kernel hacking perhaps? It seems to me that the messages do indicate some kind of non-fatal problem (that may not be true?) but I agree it is murderous to /var on a small system. Given that I now consider a small system one with a /var of under 300 megs, well.. =)
Signature · 6 lines
Joseph Carter <[email protected]> Free software developer Techical solutions are not a matter of voting. Two legislations in the US states almost decided that the value of Pi be 3.14, exactly. Popular vote does not make for a correct solution. -- Manoj Srivastava