Hello:
many users complain (and file bugs) about a flood of
the following message:
interrupt, status 3 frame# NNN
These come about 10 times a second. Some say, they correspond
to a specific device, such as mouse; others observe those
if a ZIP drive is connected but disk is not inserted.
I saw one occurence myself, with a PS/2 keyboard adapter
(it was on Erik Troan's machine). In all cases messages
file overflow people's /var.
I have put a rate limit counter in Red Hat kernel as way
to cork the bug flow temporarily. Anyone have any ideas
what ought to be done about this?
For your reference, here is an excerpt from the manual:
Bit# Description
1 USB Error Interrupt. The Host Controller sets this bit to 1 when
completion of a USB transaction results in an error condition
(e.g., error counter underflow). If the TD on which the error
interrupt occurred also had its IOC bit set, both this bit and
Bit 0 are set.
0 USB Interrupt (USBINT). The Host Controller sets this bit to 1
when the cause of an interrupt is a completion of a USB transaction
whose Transfer Descriptor had its IOC bit set.
The Host Controller also sets this bit to 1 when a short packet is
detected (actual length field in TD is less than maximum length
field in TD), and short packet detection is enabled in that TD.
-- Pete
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
http://lists.sourceforge.net/lists/listinfo/linux-usb-devel
