On Thu, 11 Dec 2003, Rogério Brito wrote: > Well, the fact that it sometimes works and sometimes doesn't can be > indicative that there's a race condition somewhere, right?
Not necessarily. It could easily be a hardware issue. > I don't remember if I mentioned this, but this device is actually > recognized as (at least) two devices: one as a USB Mass Storage Device > and another as a USB Security Device (this is what both the manual of > the Drive and Windows says). > > That is, ignoring the embedded hub that seems to be present in my drive. > > The USB Security Device seems to be (reading the manual) a second, > password-protected interface for the USB Drive. > > Couldn't it be that there's a race condition in the order that the > devices are detected and this password-protected version of the drive is > the first to be detected/accessed and then it just locks everything > else? No. The problem occurs before the other devices are detected. > Would there be any way to test the hypothesis above? Does it even make > sense? It makes sense, but it's wrong. The logs you have already posted prove that. > BTW, I don't know if it helps, but I put a screenshot of what the > Windows Device Manager tells me about the devices of my motherboard. It > is at <http://www.ime.usp.br/~rbrito/usb-new/usb-screenshot.png> and I > hope that it sheds some light on the situation. Alan Stern ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
