public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Lord <lkml@rtr.ca>
To: crash@treysoft.com
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:40:52 -0400	[thread overview]
Message-ID: <4712A904.9010304@rtr.ca> (raw)
In-Reply-To: <71b295590710141505x54ca0a8fwebfd75ab4fdf2e71@mail.gmail.com>

1. How are you forcing the drives into standby?

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

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

Cheers

  reply	other threads:[~2007-10-14 23:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-06 17:11 hdparm standby timeout not working for WD raptors? 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 [this message]
2007-10-15  0:02                   ` Mark Weber

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=4712A904.9010304@rtr.ca \
    --to=lkml@rtr.ca \
    --cc=bart@samwel.tk \
    --cc=crash@treysoft.com \
    --cc=linux-kernel@vger.kernel.org \
    /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