From: Mark Lord <lkml@rtr.ca>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Niels <zorglub_olsen@hotmail.com>,
USB development list <linux-usb-devel@lists.sourceforge.net>,
linux-kernel@vger.kernel.org, Chuck Ebbert <cebbert@redhat.com>,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: Problems with USB disk [solved]
Date: Thu, 13 Sep 2007 11:21:07 -0400 [thread overview]
Message-ID: <46E95563.5020704@rtr.ca> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0709131105250.3619-100000@iolanthe.rowland.org>
Alan Stern wrote:
> On Thu, 13 Sep 2007, Mark Lord wrote:
..
>> 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).
>
> We call it "suspended". (Wasn't there an episode of Classic Trek where
> Mr. Spock explained to somebody, "I call them `ears'."?)
>
>> 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).
>
> So this _isn't_ the regression described above -- to wit, that the
> drive gets spun down and then won't work without first being spun back
> up. You wrote:
>
>>>> My Sandisk Cruzer Micro 1GB USB sticks suffer from this regression.
>
> But it doesn't. It suffers from a different regression.
Perhaps, but that doesn't necessarily follow from the above.
>From this observer's point of view (and being an expert on disk technologies),
the same "spin up" issue for rotating media could be the culprit here too.
A reset to a disk drive usually (not always) causes it to spin up.
Regardless, Greg has acknowledged the regression and is planning to revert things.
Cheers
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
WARNING: multiple messages have this Message-ID (diff)
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 11:21:07 -0400 [thread overview]
Message-ID: <46E95563.5020704@rtr.ca> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0709131105250.3619-100000@iolanthe.rowland.org>
Alan Stern wrote:
> On Thu, 13 Sep 2007, Mark Lord wrote:
..
>> 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).
>
> We call it "suspended". (Wasn't there an episode of Classic Trek where
> Mr. Spock explained to somebody, "I call them `ears'."?)
>
>> 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).
>
> So this _isn't_ the regression described above -- to wit, that the
> drive gets spun down and then won't work without first being spun back
> up. You wrote:
>
>>>> My Sandisk Cruzer Micro 1GB USB sticks suffer from this regression.
>
> But it doesn't. It suffers from a different regression.
Perhaps, but that doesn't necessarily follow from the above.
>From this observer's point of view (and being an expert on disk technologies),
the same "spin up" issue for rotating media could be the culprit here too.
A reset to a disk drive usually (not always) causes it to spin up.
Regardless, Greg has acknowledged the regression and is planning to revert things.
Cheers
next prev parent reply other threads:[~2007-09-13 15:21 UTC|newest]
Thread overview: 19+ 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-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:12 ` Alan Stern
2007-09-13 14:35 ` Mark Lord
2007-09-13 15:09 ` Alan Stern
2007-09-13 15:09 ` Alan Stern
2007-09-13 15:21 ` Mark Lord [this message]
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=46E95563.5020704@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.