From: "Mark Weber" <crash@treysoft.com>
To: "Mark Lord" <lkml@rtr.ca>
Cc: "Bart Samwel" <bart@samwel.tk>, linux-kernel@vger.kernel.org
Subject: Re: hdparm standby timeout not working for WD raptors?
Date: Sun, 14 Oct 2007 19:02:12 -0500 [thread overview]
Message-ID: <71b295590710141702r48be29f3s9308ab7dd8f7363c@mail.gmail.com> (raw)
In-Reply-To: <4712A904.9010304@rtr.ca>
On 10/14/07, Mark Lord <lkml@rtr.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
prev parent reply other threads:[~2007-10-15 0:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-06 17:11 Mark Weber
2007-10-11 19:37 ` Mark Lord
2007-10-12 5:07 ` Mark Weber
2007-10-12 13:30 ` Mark Lord
2007-10-12 22:19 ` Mark Weber
2007-10-13 12:46 ` Mark Lord
2007-10-14 12:36 ` Bart Samwel
2007-10-14 20:30 ` Mark Weber
2007-10-14 21:05 ` Bart Samwel
2007-10-14 22:05 ` Mark Weber
2007-10-14 23:40 ` Mark Lord
2007-10-15 0:02 ` Mark Weber [this message]
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=71b295590710141702r48be29f3s9308ab7dd8f7363c@mail.gmail.com \
--to=crash@treysoft.com \
--cc=bart@samwel.tk \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
/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
all inboxes | Powered by JetHome®