Alan Stern wrote:
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 ever
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
On Sunday 15 August 2004 4:13 am, Wes Janzen wrote:
>
> 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 usec
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, wh
On Thursday 22 July 2004 16:15, Wes Janzen wrote:
> I've been having trouble with USB since 2.6.8-rc1; khubd ends up
> blocking on something which makes USB hotplugging stop working (and only
> half my devices even get initialized). I did get 2.6.8-rc1 to work once
> though it seemed to help in
On Thu, 22 Jul 2004, Wes Janzen wrote:
> I've been having trouble with USB since 2.6.8-rc1; khubd ends up
> blocking on something which makes USB hotplugging stop working (and only
> half my devices even get initialized). I did get 2.6.8-rc1 to work once
> though it seemed to help inserting mo
