Alan Stern wrote:
Right, but that shouldn't mean all my devices appear as block devices then, correct? Not that it really matters since with 2.6.8-rc4-mm1 I get the expected ub? device only when I plug in mass storage devices like my pen drive.On Sun, 15 Aug 2004, Wes Janzen wrote:
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.
Sounds like you've got the ub driver installed (look under the block devices part of the kernel configuration or for the ub module).
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.
You didn't even provide a dmesg for me to go on,
I'm sorry, I've rectified that now.
I tested all 8 of my USB devices and everything works except the joystick. As soon as I plug it in, khubd blocks and presumably never succeeds. I haven't tried it direct yet, but I can if that would help.
I unplugged the joystick last night and that did not seem to help as everything but the light on my hub remained the same as of a couple hours ago. I did get a bunch of these in the log though when I went to reboot to verify the joystick was the cause of the problems:
Aug 16 02:39:26 voice ehci_hcd 0000:00:08.2: devpath 2 ep1in 3strikes Aug 16 02:39:26 voice hub 4-2:1.0: transfer --> -71 Aug 16 02:39:27 voice ehci_hcd 0000:00:08.2: devpath 2 ep1in 3strikes Aug 16 02:39:27 voice hub 4-2:1.0: transfer --> -71 Aug 16 02:39:28 voice ehci_hcd 0000:00:08.2: devpath 2 ep1in 3strikes Aug 16 02:39:28 voice hub 4-2:1.0: transfer --> -71 Aug 16 02:39:28 voice ehci_hcd 0000:00:08.2: devpath 2 ep1in 3strikes Aug 16 02:39:28 voice hub 4-2:1.0: transfer --> -71 Aug 16 02:39:29 voice ehci_hcd 0000:00:08.2: devpath 2 ep1in 3strikes Aug 16 02:39:29 voice hub 4-2:1.0: transfer --> -71 Aug 16 02:39:30 voice ehci_hcd 0000:00:08.2: devpath 2 ep1in 3strikes Aug 16 02:39:30 voice hub 4-2:1.0: transfer --> -71 Aug 16 02:39:31 voice ehci_hcd 0000:00:08.2: devpath 2 ep1in 3strikes Aug 16 02:39:31 voice hub 4-2:1.0: transfer --> -71 Aug 16 02:39:32 voice ehci_hcd 0000:00:08.2: devpath 2 ep1in 3strikes Aug 16 02:39:32 voice hub 4-2:1.0: transfer --> -71 Aug 16 02:39:32 voice ehci_hcd 0000:00:08.2: devpath 2 ep1in 3strikes Aug 16 02:39:32 voice hub 4-2:1.0: transfer --> -71 Aug 16 02:39:33 voice ehci_hcd 0000:00:08.2: devpath 2 ep1in 3strikes Aug 16 02:39:33 voice hub 4-2:1.0: transfer --> -71 Aug 16 02:39:34 voice ehci_hcd 0000:00:08.2: devpath 2 ep1in 3strikes Aug 16 02:39:34 voice hub 4-2:1.0: transfer --> -71
I've seen that before and it only seems to happen when khubd sticks.
so this is strictly guesswork... You could try applying the patch from this message:I'll give that a try, though it could be several days before I'm able to post my results.
http://marc.theaimsgroup.com/?l=linux-usb-devel&m=109241303306477&w=2
Alan Stern
Thanks,
-Wes-
bootlog-2.6.8-rc4-mm1.txt.gz
Description: GNU Zip compressed data
Description: OpenPGP digital signature
