Alan Stern wrote:
On Thu, 22 Jul 2004, Wes Janzen wrote:
[...]
It looks like your troubles start when your USB printer is probed or detached. What happens if you simply leave the printer unplugged and boot up -- is everything okay then? And then if you plug in the printer later on, what happens?
Alan Stern
Hi,
Nothing like a quick reply, I've unfortunately had very little time to even sit down at my computer to figure this out. I have tried 2.6.8-rc2-mm2 which has the same problem. I unplugged both hubs before booting and then plugged everything in one at a time after the system was finished loading. That seemed to work, but not really since all my usb devices then appeared as ub? (a-h) instead of the appropriately named devices. So I tried 2.6.8-rc4-mm1 which I'm using now. Again I had to unplug everything to boot. I plugged everything in one hub one-by-one. Due to the location of the second hub (and the lack of time), I didn't individually plug each device in and it seems to have locked up (khubd goes D) on detecting my Logitech joystick. Now khubd is stuck in the d state (as well as lsusb from me later). At least now it's back to detecting devices appropriately so at least I can use a mouse in X. Now I'm getting these messages every few minutes in my log:
Aug 15 06:05:13 voice drivers/usb/host/ehci-sched.c: reused previous qh d6a00200 schedule
Aug 15 06:05:13 voice drivers/usb/host/ehci-sched.c: scheduled qh d6a00200 usecs 8/15 period 8.0 starting 5.0 (gap 1)
It says exactly the same thing every time, but I've not had to time to look at ehci-sched.c to find out what that message means.
Anyway, the printer doesn't seem to be at fault since it was turned off this time around.
Thanks,
-Wes-
signature.asc
Description: OpenPGP digital signature
