On Thu, May 25, 2000 at 06:04:26PM +0000, Ian Blenke wrote:
> This is a "partial success" message.
>
> I've just built 2.4.0-test1 (2.3.99pre10-3) and was suprised to find that
> this previously problematic D-Link DSB-H4SMK hub now *almost* works. :)
>
> Using previous 2.2.1X+backports and previous 2.3.99-preX kernels, I've only
> managed to get usb-debug.c SETUP failure messages. With the new kernel,
> however, I now get the the following looping message:
>
> usb-uhci.c: interrupt, status 3, frame# 1472
> hub.c: nonzero status in irq -32
>
> This is the problematic device vendor id and device id:
> 0403:8370 D-Link H4SMK 7 Port Multifunction Hub (FTDI?) (hub.o)
The hub seems to have a halted/stalled interrupt endpoint, since this
message appears every 128 frames (hub polling interval). Now the question
is: Does this start with certain messages sent to the hub? I have a hub
(with an Atmel chip) that doesn't like to be asked for string descriptors.
After 'lsusb' (which seems to read string index 0), the hub is also dead...
Can you try to enable the output for control/setup messages? For usb-uhci (the
file I know best...), the place to enable it is in uhci_submit_control_urb().
Currently it is disabled with '#if 0'.
--
Georg Acher, [EMAIL PROTECTED]
http://www.in.tum.de/~acher/
"Oh no, not again !" The bowl of petunias
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
