public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Lord <lkml@rtr.ca>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Chuck Ebbert <cebbert@redhat.com>,
	Niels <zorglub_olsen@hotmail.com>,
	linux-kernel@vger.kernel.org,
	linux-scsi <linux-scsi@vger.kernel.org>,
	USB development list <linux-usb-devel@lists.sourceforge.net>
Subject: Re: [linux-usb-devel] Problems with USB disk [solved]
Date: Thu, 13 Sep 2007 10:35:46 -0400	[thread overview]
Message-ID: <46E94AC2.3030607@rtr.ca> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0709131008360.3619-100000@iolanthe.rowland.org>

Alan Stern wrote:
> On Wed, 12 Sep 2007, Mark Lord wrote:
> 
>> Chuck Ebbert wrote:
..
>>> Oh, nice. The usb-storage (SCSI) disk spins itself down and we can't handle that.
>>> Should we be disabling auto-spindown when we connect the device, or be able to
>>> handle this by sending the start command when needed?
>> There's more to this.
>>
>> My Sandisk Cruzer Micro 1GB USB sticks suffer from this regression.
> 
> I seriously doubt that.  Are you claiming that your USB stick spins 
> itself down during a suspend?  And then requires to be spun back up 
> before it will resume proper operation?

No, the machine is not being suspended at all.

What happens is, there's a nice little LED on the Cruzer stick,
that is "lit" when the stick itself is not in a "power suspend" state
(or whatever you USB folks call it).

On 2.6.22, that little LED stays "on" normally, and flickers off/on
when data is being transfered.

The new "USB autosuspend" logic in 2.6.23 now causes that little LED
to turn off after a few seconds of inactivity.

Once that happens, the USB stick is not accessible until after a longish
timeout (~30s I think), followed by a USB reset.  Then it is usable again
until the next inactivity timeout and autosuspend (a few seconds).

Etc.


  reply	other threads:[~2007-09-13 14:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-07 20:26 Problems with USB disk Niels
2007-08-07 21:18 ` Greg KH
2007-08-08 10:48   ` Niels
2007-08-08 10:57     ` Ismail Dönmez
2007-08-10 12:43       ` Niels
2007-08-12  9:54         ` Niels
2007-08-13 14:50           ` Problems with USB disk [solved] Niels
2007-08-14 15:08             ` Chuck Ebbert
2007-09-12 22:10               ` Mark Lord
2007-09-12 23:42                 ` Greg KH
2007-09-13 14:12                 ` [linux-usb-devel] " Alan Stern
2007-09-13 14:35                   ` Mark Lord [this message]
2007-09-13 15:09                     ` Alan Stern
2007-09-13 15:21                       ` Mark Lord
2007-08-10  4:54   ` Problems with USB disk Bill Davidsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46E94AC2.3030607@rtr.ca \
    --to=lkml@rtr.ca \
    --cc=cebbert@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=stern@rowland.harvard.edu \
    --cc=zorglub_olsen@hotmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox