On Thu, 9 Aug 2007, Martin Fahr wrote: > Dear Alan, > > thank you for your answer. > Unfortunately I am somewhat confused now. You mentioned an "error -71", > while I see a "-110", and no "-71".
My mistake; I must have misread your message. Sometimes we see what we expect to see instead of what's really there... The -110 error means that the computer was waiting for the stick to acknowledge receiving a request and to send back a reply, but the stick didn't do so and after about five seconds the request timed out. > But nevertheless, putting all things together, your explanation of > "something happens in the stick" fits best. I already mentioned the > badly damaged file systems, which apparently doesn't happen, when the > stick or power to the stick is removed intentionally. Thus it's probably > in the stick. > > Cable is probably not the reason, because an longer cable didn't change > anything. > > Later on I noticed that the mentioned problem arises significantly less > often when I use the power supply from an additional USB port. But > unfortunately it still happens, but now after a day or two and not every > two hours. I will try to add a big capacitor to the power lanes, just in > case that helps. Good luck. > Just one question yet, as I m not an expert to USB handling in linux. I > already sent the following two lines from dmesg. It's the first thing > that comes out, when the system dies. What do they mean? > |ehci_hcd 0000:03:00.2 port 2 high speed > |ehci_hcd 0000:03:00.2 GetStatus port 2 status 001005 POWER sig=se0 PE > CONNECT Those lines are part of a port reset, which is what the usb-storage driver does to try to recover from an error. (All they mean is that following the reset, the computer detected your stick as a high-speed device plugged into port 2.) Some sort of error must have occurred just before those lines; unfortunately there's no configuration option to make usb-storage print errors in the log without also printing lots of other useless information. The -110 errors that follow are also part of the reset. The fact that they occurred means the device did not succeed in resetting itself fully. > And BTW, this new patch in 2.6.23-rcx to make USB devices persistant > over suspend works great. Just in case noone else uses it. Thanks. Alan Stern ------------------------------------------------------------------------- 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/ _______________________________________________ Linux-usb-users@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
