Re: [linux-usb-devel] OHCI problems with 2.6.10-rc3

2004-12-17 Thread David Brownell
On Friday 17 December 2004 3:25 pm, Robert Wruck wrote: > > At which point an "alt-sysrq-t" traceback should be informative, > > if this patch doesn't help the latest rc3-BK code. > > Thanks! Keeping the root hub from suspending seems to solve the > problem.. Good -- it's already in 2.6.10-rc3-b

Re: [linux-usb-devel] OHCI problems with 2.6.10-rc3

2004-12-17 Thread Robert Wruck
> At which point an "alt-sysrq-t" traceback should be informative, > if this patch doesn't help the latest rc3-BK code. Thanks! Keeping the root hub from suspending seems to solve the problem.. -robert --- SF email is sponsored by - The IT P

Re: [linux-usb-devel] OHCI problems with 2.6.10-rc3

2004-12-16 Thread David Brownell
On Sunday 12 December 2004 4:26 pm, Robert Wruck wrote: > Hi, > > I'm encountering a strange behaviour with an AMD-756 USB controller, or > more exactly: > :00:07.4 USB Controller: Advanced Micro Devices [AMD] AMD-756 > [Viper] USB (rev 06) > > There's one USB device connected at boot time

[linux-usb-devel] OHCI problems with 2.6.10-rc3

2004-12-13 Thread Robert Wruck
Hi, I'm encountering a strange behaviour with an AMD-756 USB controller, or more exactly: :00:07.4 USB Controller: Advanced Micro Devices [AMD] AMD-756 [Viper] USB (rev 06) There's one USB device connected at boot time (a low speed APC UPS). When I boot up the system and issue a 'cat /proc/b