Ext3 users - Sep 2014 - Re: problems with usb stick after suspend and wake up

Hi Alan,

sorry for the journalctl output. I have now done the following:L

* boot into 3.17-rc7
* mount the usb stick (recovery completed)
* unmount, mount, unmount - just to be sure all is fine
* started usbmon capturing on bus 3
* mount the usb stick
* suspend to ram
* wake up
	now the stick is "officially" mounted (/proc/mounts)
* umount 
	error messages pop up
* try to mount
	more error messages
* capture dmesg output
* stip usbmon

The two files are available here:
	http://www.preining.info/kernel/3.mon.out.gz (size 21596)
	http://www.preining.info/kernel/3.mon.out (size 216343)
and
	http://www.preining.info/kernel/dmesg.log.gz (size 17883)
	http://www.preining.info/kernel/dmesg.log (size 67734)

Just a few more things:
* usb persistency is turned on
* I checked the stick with badblocks during creation of the fs

All the best

Norbert

------------------------------------------------------------------------
PREINING, Norbert                               http://www.preining.info
JAIST, Japan                                 TeX Live & Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0  ACF0 6CAC A448 860C DC13
------------------------------------------------------------------------

On Mon, 29 Sep 2014, Norbert Preining wrote:
> Hi Alan,
> 
> sorry for the journalctl output. I have now done the following:L
> 
> * boot into 3.17-rc7
> * mount the usb stick (recovery completed)
> * unmount, mount, unmount - just to be sure all is fine
> * started usbmon capturing on bus 3
> * mount the usb stick
> * suspend to ram
> * wake up
> 	now the stick is "officially" mounted (/proc/mounts)
> * umount 
> 	error messages pop up
> * try to mount
> 	more error messages
> * capture dmesg output
> * stip usbmon
> 
> The two files are available here:
> 	http://www.preining.info/kernel/3.mon.out.gz (size 21596)
> 	http://www.preining.info/kernel/3.mon.out (size 216343)
> and
> 	http://www.preining.info/kernel/dmesg.log.gz (size 17883)
> 	http://www.preining.info/kernel/dmesg.log (size 67734)
> 
> Just a few more things:
> * usb persistency is turned on
> * I checked the stick with badblocks during creation of the fs
The first error occurred the first time the computer tried to write 
data to the stick following the resume.  Oddly enough, an earlier write 
before the suspend worked correctly.  But the real problem occurred 
when the computer asked the stick to provide the reason for the error.  
At that point the stick refused to answer.

There were several resets, and the write was retried after each reset.  
And each time the write failed, and the stick refused to answer when 
asked the reason for the failure.

There's no obvious cause for this problem.  It really looks like 
something is wrong with the USB stick.

Alan Stern

El 29/09/14 11:15, Alan Stern escribió:
> The first error occurred the first time the computer tried to write
> data to the stick following the resume.  Oddly enough, an earlier write
> before the suspend worked correctly.  But the real problem occurred
> when the computer asked the stick to provide the reason for the error.
> At that point the stick refused to answer.
>
> There were several resets, and the write was retried after each reset.
> And each time the write failed, and the stick refused to answer when
> asked the reason for the failure.
>
> There's no obvious cause for this problem.  It really looks like
> something is wrong with the USB stick.
     Ok the culprit is the USB stick, but when retrying and seeing that 
the resets are unsuccessful, could the USB power be removed for the 
stick for half a second and restored and the write retried then?
     Have a nice day!
P.s.: sorry if I am saying nonsense...

-- 
Ivan Baldo - ibaldo@adinet.com.uy - http://ibaldo.codigolibre.net/
 From Montevideo, Uruguay, at the south of South America.
Freelance programmer and GNU/Linux system administrator, hire me!
Alternatives: ibaldo@codigolibre.net - http://go.to/ibaldo

Hi Alan,

On Mon, 29 Sep 2014, Alan Stern wrote:
> There were several resets, and the write was retried after each reset.  
> And each time the write failed, and the stick refused to answer when 
> asked the reason for the failure.
> 
> There's no obvious cause for this problem.  It really looks like 
> something is wrong with the USB stick.
Hmm, ok, thanks. I think I will return it then. 
I hope they accept my explanation about it.

Thanks for looking into it!!!

Norbert

------------------------------------------------------------------------
PREINING, Norbert                               http://www.preining.info
JAIST, Japan                                 TeX Live & Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0  ACF0 6CAC A448 860C DC13
------------------------------------------------------------------------