On Sun, 13 Mar 2005, Guilhem Lavaux wrote:
> Hi,
>
> Here is the syslog corresponding to your request. I've added a few
> comments to show you the moment the events happen.
You're seeing two different errors here. And there are a few things
in the log I don't understand; it's possible that your syslogd has
dropped some of the log entries.
> Mar 13 17:28:39 taniquetil kernel: hub 4-0:1.0: enabling power on all ports
> Mar 13 17:28:39 taniquetil kernel: uhci_hcd 0000:00:1d.0: Unlink after
> no-IRQ? Controller is probably using the wrong IRQ.
> Mar 13 17:28:39 taniquetil kernel: usb 1-2: khubd timed out on ep0in
Although something like this is expected, it shouldn't have happened that
way. I don't see why that "Unlink after no-IRQ" message appeared. Can
you try applying this diagnostic patch and post the log messages it gives?
(I don't think your problems are caused by bad IRQ assignments; they seem
to be okay.)
--- a/drivers/usb/core/hcd.c Fri Mar 4 09:52:25 2005
+++ b/drivers/usb/core/hcd.c Mon Mar 14 12:06:21 2005
@@ -1262,6 +1262,7 @@
"Controller is probably using the wrong IRQ."
"\n");
hcd->saw_irq = 1;
+ WARN_ON(1);
}
urb->status = status;
> Mar 13 17:28:39 taniquetil kernel: usb-storage: waiting for device to settle
> before scanning
> Mar 13 17:28:39 taniquetil kernel: Vendor: IC35L120 Model: AVV207-0
> Rev: V24O
> Mar 13 17:28:39 taniquetil kernel: Type: Direct-Access
> ANSI SCSI revision: 00
> Mar 13 17:28:39 taniquetil kernel: usb-storage: device scan complete
Another thing I don't understand is why there isn't a five-second delay
here before usb-storage scans your device. Did you do anything to shorten
that delay?
> >>However if I try to plug an USB 1 device on another bus then I get the
> >>first message until I reload again the driver.
> At that moment I plug another USB storage key (USB1 key) on another
> port and I get this. However if I unload and reload the driver I get
> access to the key.
At first you said the USB-1.0 key was plugged on another bus, but here you
say it's plugged into another port. In fact that port is on the _same_
bus as the Freebox device.
> Mar 13 17:30:37 taniquetil kernel: usb 1-1: new full speed USB device using
> uhci_hcd and address 3
> Mar 13 17:30:37 taniquetil kernel: usb 1-1: ep0 maxpacket = 8
> Mar 13 17:30:37 taniquetil kernel: uhci_hcd 0000:00:1d.0:
> uhci_result_control: failed with status 440000
> Mar 13 17:30:37 taniquetil kernel: [d9ba5300] link (19ba51e2) element
> (1f102880)
> Mar 13 17:30:37 taniquetil kernel: Element != First TD
> Mar 13 17:30:37 taniquetil kernel: 0: [df102840] link (1f102880) e3
> Length=7 MaxLen=7 DT0 EndPt=0 Dev=3, PID=2d(SETUP) (buf=1f5e7c40)
> Mar 13 17:30:37 taniquetil kernel: 1: [df102880] link (1f1028c0) e0 SPD
> Stalled CRC/Timeo Length=7ff MaxLen=7 DT1 EndPt=0 Dev=3, PID=69(IN)
> (buf=1f5e7640)
This doesn't look like the same kind of error as above. If you unplug the
key, rmmod uhci-hcd, modprobe it again, and then reinsert the key will it
work? Or does the key only work if it is plugged in at the time you
modprobe uhci-hcd?
Here's something else you can do that might help. Make sure you have a
debugfs filesystem mounted somewhere (typically /sys/kernel/debug), and
get a copy of .../uhci/0000:00:1d.0 right before you rmmod uhci-hcd the
first time and then again after first plugging in the USB key.
Alan Stern
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
