From: James H. Markowitz on
On Thu, 11 Feb 2010 15:24:58 -0500, David W. Hodgins wrote:

> On Thu, 11 Feb 2010 14:22:20 -0500, Todd <todd(a)invalid.com> wrote:
>
>> On 02/09/2010 06:03 PM, James H. Markowitz wrote:
>>> I have a number of USB hard drives connected to a Linux PC. They
>>> all work fine, but they have an annoyance in common: When they have
>>> been accessed for a while (minutes; I am not sure how many) the next
>>> time I try to access them several seconds elapse before they respond.
>>> It's as though they stopped spinning when not accessed for a while.
>
>> https://bugzilla.redhat.com/show_bug.cgi?id=469290 You are not alone.
>> The only way I found to get around it was to reboot. Changing
>> "elevators" did not work either.
>
> See if
> echo "-1" >/sys/module/usbcore/parameters/autosuspend helps fix this.

Unfortunately, /sys/module/usbcore/parameters/autosuspend doesn't
exist in my Slackware 12.1 box, running a 2.6.24.5 kernel.


From: David W. Hodgins on
On Thu, 11 Feb 2010 21:40:25 -0500, James H. Markowitz <noone(a)nowhere.net> wrote:

> Unfortunately, /sys/module/usbcore/parameters/autosuspend doesn't
> exist in my Slackware 12.1 box, running a 2.6.24.5 kernel.

See if the fourth answer in
http://www.linuxquestions.org/questions/linux-hardware-18/how-can-one-get-usb-external-disk-drive-to-sleep-667762/
helps.

Regards, Dave Hodgins

--
Change nomail.afraid.org to ody.ca to reply by email.
(nomail.afraid.org has been set up specifically for
use in usenet. Feel free to use it yourself.)
From: James H. Markowitz on
On Thu, 11 Feb 2010 22:01:44 -0500, David W. Hodgins wrote:

> On Thu, 11 Feb 2010 21:40:25 -0500, James H. Markowitz
> <noone(a)nowhere.net> wrote:
>
>> Unfortunately, /sys/module/usbcore/parameters/autosuspend doesn't
>> exist in my Slackware 12.1 box, running a 2.6.24.5 kernel.
>
> See if the fourth answer in
> http://www.linuxquestions.org/questions/linux-hardware-18/how-can-one-
get-usb-external-disk-drive-to-sleep-667762/
> helps.

Thanks. Still no joy, unfortunately: autosuspend is nowhere to
bee seen in my /sys/bus/usb/devices subdirectories, and trying to echo
anything into it makes no difference.


From: J G Miller on
On Fri, 12 Feb 2010 16:30:31 +0000, James H. Markowitz wrote:

> Still no joy

And what happens when you try using the hdparm utility as suggested
in another posting?
From: Harold Johanssen on
On Fri, 12 Feb 2010 19:30:53 +0100, J G Miller wrote:

> On Fri, 12 Feb 2010 16:30:31 +0000, James H. Markowitz wrote:
>
>> Still no joy
>
> And what happens when you try using the hdparm utility as suggested in
> another posting?

I thought that hdparm was meant for IDE drives, not USB ones.
Anyway, I tried the following:

# hdparm -C /dev/sde

and this is what I got.

/dev/sde:
G_IO: bad/missing ATA_16 sense data:: 70 00 05 00 00 00 00 0a 00
0 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
G_IO: bad/missing ATA_16 sense data:: 70 00 05 00 00 00 00 0a 00
0 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
drive state is: unknown

I am a bit reluctant to tinker with my USB drive using hdparm any further
until I understand it better.