lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <71b295590710141330g7a4779e5q2d6b8f50387ee971@mail.gmail.com>
Date:	Sun, 14 Oct 2007 15:30:57 -0500
From:	"Mark Weber" <crash@...ysoft.com>
To:	"Bart Samwel" <bart@...wel.tk>
Cc:	"Mark Lord" <lkml@....ca>, linux-kernel@...r.kernel.org
Subject: Re: hdparm standby timeout not working for WD raptors?

On 10/14/07, Bart Samwel <bart@...wel.tk> wrote:
>
> Some things to check:
>
> * Run "hdparm -I" on your drive. In the "Capabilities" section there is
> a line "Standby timer values", for some drives this mentions a device
> specific minimum. I know some drives that ignore any setting below 60
> seconds.
>
> * I also know of quite a number of drives where hdparm -B settings
> override the -S settings, even if you set the -S settings after the
> hdparm -B settings. You could try combinations with various values of
> hdparm -B, especially 1 and 255.

Thanks for the suggestions.

The -I command prints out a bunch of stuff including:
Standby timer values: spec'd by Standard, with device specific minimum

I tried setting -B to 1 and and then set -S to 5 minutes.
Also, -B 255 and then set -S to 5 minutes.
No luck with either. These drives want to keep running.

One thing of possible interest: The -B command printed
the following message:

/dev/sda:
 setting Advanced Power Management level to 0x01 (1)
 HDIO_DRIVE_CMD failed: Input/output error

I would guess that the first line came out just before
hdparm tried to do the set, and the second line indicates
that the set failed.

Perhaps -S is failing too, just without the diagnostic?

All of the above using 2.6.22-gentoo-r5
I have not yet tried 2.6.23 as suggested by Mark Lord.

---

"And he puzzled three hours, `till his puzzler was sore."
from "How the Grinch Stole Christmas"
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ