Ferenc-Jan wrote:

You're not making sense to me.  If it fails in the same way,
it oopses; if it doesn't oops, you've got a different failure.


My apologies, I quoted too little of my previous posts.

The "Subject:" ought to suffice.



In setting up bluetooth networking something fails and connectivity is lost. On the P133 laptop (ohci), the bluetooth software complains about timeouts & unreachable bluetooth hardware. Re-inserting the usb bluetooth dongle wakes it up, and bluetooth networking can again be set up. The bluetooth team thinks this points to an usb driver problem.

Actually, I'd suspect the bluetooth devices aren't quite being talked to in the way they'd like. I honestly can't remember the last time there was an OHCI bug with those kinds of symptoms ... but in terms of buggy protocol layered on top of USB (between a usb device driver and the firmware or silicon inside that device), certainly I've seen them most months.


With 2.4.21 the re-inserting business usually resulted in an oops. This oops I posted earlier. I have not yet been able to get 2.6.0t to oops in this way.

In short, the 2.6.0-test kernels have no evident OHCI issue here. I'll assume that the "ohci-hcd" backport also behaves.

- Dave




------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Reply via email to