On Wed, 21 Dec 2005, Brown, Len wrote: > >> >Can you send the dmesg log for the situation where you boot with the > >> >keyboard and mouse plugged into the computer and the computer > >> >attached to the docking station? > >> > >> Attached as dmesg.init3 > >> corresponding devices.init3 attached as well. > >> > >> However, while gathering the dmesg I realized that the > >> keyboard started working some time after I logged in > >> (via network and serial console, not using console kbd) > >> > >> After I realized the keyboard was working I looked in that > >> file again and the keyboard had appeard (devices.init3.diff) > > > >Can you resend this logs from message, perhaps inline? Your > >(or Intel's) Symantec Mail Security program deleted the attachments.
Hmm... There aren't any timestamps in the log, so it's hard to tell just how long the various events go on for. Basically the log shows correct and expected behavior. The only questionable aspect occurs when the system tries to initialize the docking station's internal hub. You get lots of errors like these: > usb 3-5: khubd timed out on ep0in len=0/64 > ehci_hcd 0000:00:02.2: port 5 high speed > ehci_hcd 0000:00:02.2: GetStatus port 5 status 001005 POWER sig=se0 PE CONNECT > usb 3-5: device descriptor read/64, error -110 > ehci_hcd 0000:00:02.2: port 5 high speed > ehci_hcd 0000:00:02.2: GetStatus port 5 status 001005 POWER sig=se0 PE CONNECT > usb 3-5: new high speed USB device using ehci_hcd and address 5 > usb 3-5: khubd timed out on ep0in len=0/64 > usb 3-5: khubd timed out on ep0in len=0/64 > usb 3-5: khubd timed out on ep0in len=0/64 The hub driver does a lot of retries and timeouts while attempting to get the docking station to work; apparently all those timeouts take longer in aggregate than you would like. Perhaps the code should avoid doing quite so many retries. At any rate, since the hub driver is single-threaded, it doesn't get around to registering your mouse and keyboard (the wireless receiver _does_ go to the keyboard, right?) until after it has given up on the docking station. I still don't have a clue about why the docking station's hub refuses to cooperate. The log shows only that it is not sending back data when it should be. If it worked correctly then none of those timeouts and retries would have occurred. Alan Stern ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
