linux-kernel - Re: hdparm standby timeout not working for WD raptors?

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] [day] [month] [year] [list]

Message-ID: <71b295590710141702r48be29f3s9308ab7dd8f7363c@mail.gmail.com>
Date:	Sun, 14 Oct 2007 19:02:12 -0500
From:	"Mark Weber" <crash@...ysoft.com>
To:	"Mark Lord" <lkml@....ca>
Cc:	"Bart Samwel" <bart@...wel.tk>, linux-kernel@...r.kernel.org
Subject: Re: hdparm standby timeout not working for WD raptors?

On 10/14/07, Mark Lord <lkml@....ca> wrote:
> 1. How are you forcing the drives into standby?

hdparm -y



> 2. Have you reproduced this with a stock kernel.org kernel yet?

No; maybe later this week.



> One possibility is that these drives may be the kind that
> generate a "spurious" interrupt when they spin-down via the timer,
> and perhaps libata is "processing" that interrupt and sending
> additional command(s) that then wake the drive up again immediately.
>
> To rule this out, you could try using drivers/ide for a moment or two,
> and see if the same problem persists with those drives.
>
> You could also try dumping /proc/interrupts in conjunction with "hdparm -S1",
> and we can compare that with a "known good" system.
>
> Something like this:
>
> hdparm -B255 /dev/sda
> hdparm -S1 /dev/sda
> cat /proc/interrupts
> sleep 6
> cat /proc/interrupts




Here's the log for the second suggestion:



narf ~ # hdparm -B255 /dev/sda

/dev/sda:
 setting Advanced Power Management level to disabled
 HDIO_DRIVE_CMD failed: Input/output error

narf ~ # hdparm -S1 /dev/sda

/dev/sda:
 setting standby to 1 (5 seconds)
narf ~ # cat /proc/interrupts
           CPU0
  0:       2268   IO-APIC-edge      timer
  1:          2   IO-APIC-edge      i8042
  8:          5   IO-APIC-edge      rtc
  9:          0   IO-APIC-fasteoi   acpi
 12:          4   IO-APIC-edge      i8042
 14:     206827   IO-APIC-edge      ide0
 16:     350813   IO-APIC-fasteoi   sata_promise, uhci_hcd:usb5
 17:   39596029   IO-APIC-fasteoi   eth0
 18:          0   IO-APIC-fasteoi   uhci_hcd:usb4
 19:     728947   IO-APIC-fasteoi   libata, uhci_hcd:usb3
 20:          0   IO-APIC-fasteoi   ehci_hcd:usb1, uhci_hcd:usb2
NMI:          0
LOC:    2736793
ERR:          0
MIS:          0
narf ~ # sleep 6
narf ~ # cat /proc/interrupts
           CPU0
  0:       2268   IO-APIC-edge      timer
  1:          2   IO-APIC-edge      i8042
  8:          5   IO-APIC-edge      rtc
  9:          0   IO-APIC-fasteoi   acpi
 12:          4   IO-APIC-edge      i8042
 14:     206828   IO-APIC-edge      ide0
 16:     350813   IO-APIC-fasteoi   sata_promise, uhci_hcd:usb5
 17:   39596069   IO-APIC-fasteoi   eth0
 18:          0   IO-APIC-fasteoi   uhci_hcd:usb4
 19:     728947   IO-APIC-fasteoi   libata, uhci_hcd:usb3
 20:          0   IO-APIC-fasteoi   ehci_hcd:usb1, uhci_hcd:usb2
NMI:          0
LOC:    2736881
ERR:          0
MIS:          0
-
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/