Re: software unplug

Pete Zaitcev wrote:
> The symptoms you described point to a sequencer lock-up in the device.
> Your best bet is to change the brand of the dongle to a more reliable
> one. 
Any suggestion about which brands could be more reliable than others?

> If you work for a bigger OEM, you may be able to shop around and 
> have vendors interested.
Not exactly my case...

Felipe Balbi wrote:
> This is not the right way to do it. 
Maybe, but I'd like a quick & dirty solution at the moment. Besides that I'm
more than happy to recompile the kernel, provide you with the debug output
and so on.

> Provide us more detailed 
> information such as dmesg output. 
That's hard to retrieve. The problem is not reproducible, it happens once
every several days, it never happened in test system but it's happening in
a few production systems (not all). I suspect it happens only on those
production systems where bluetooth traffic is higher, a situation hard to
simulate for our resources during lab tests; however that's only a not so
reliable guess.

> Another good information would be your kernel version.
2.6.21.1-2 from Debian Lenny i386 (but the rest of the system is Etch).

Lucio.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel