linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: jbradford@dial.pipex.com
To: davidsen@tmr.com (Bill Davidsen)
Cc: padraig.brady@corvil.com, linux-kernel@vger.kernel.org
Subject: Re: hdparm -Y hangup
Date: Wed, 25 Sep 2002 08:49:48 +0100 (BST)	[thread overview]
Message-ID: <200209250749.g8P7nmiT000178@darkstar.example.net> (raw)
In-Reply-To: <Pine.LNX.3.96.1020924170534.19732B-100000@gatekeeper.tmr.com> from "Bill Davidsen" at Sep 24, 2002 05:06:57 PM

> > > Hrm, OK thanks for the info. Perhaps it should be removed
> > > from hdparm or a (DANGEROUS) put beside the description
> > > until it's fixed.
> > 
> > The person to contact would be Mark Lord, the hdparm maintainer, (see the
> > hdparm manual page for his E-Mail address).
> 
> Rather than have Mark Lord set the option DANGEROUS (it shouldn't be)
> perhaps it could be made to work more than once... Odd problem, is
> something not getting set or cleared when the drive is spun up the first
> time?

With my Maxtor disk connected to a PIIX3 IDE interface and stock kernel 2.4.19, I get this behavior:

# hdparm -Y /dev/hda

Disk sleeps

# find

No disk activity - it doesn't wake up.  It doesn't work once for me, it always hangs on the first attempt.

So, I try dmesg on another console - no new output.

# hdparm -w /dev/hda

Performs a device reset, and the disk spins up.

# dmesg

hda: ide_set_handler: handler not null; c0181050
hda: dma_intr: status=0xd0 { Busy }
hda: DMA disabled
hda: ide_set_handler: handler not null; old=c0181050, new=c017b160
bug: kernel timer added twice at c017afe1.
hda: ide_set_handler: handler not null; old=c017b160, new=c017b160
ide0: reset: success

Obviously, if you're going to try to repeat this, sync the disk beforehand, because I assume that a device reset will loose data in the disk's write cache.

John.

  reply	other threads:[~2002-09-25  7:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-20 14:24 hdparm -Y hangup Padraig Brady
2002-09-21 18:13 ` jbradford
2002-09-23  8:32   ` Padraig Brady
2002-09-23  9:44     ` jbradford
2002-09-24 21:06       ` Bill Davidsen
2002-09-25  7:49         ` jbradford [this message]
2002-09-23 23:08 Peter
2002-09-25 14:58 ` Mark Lord
2002-09-25 15:06   ` Padraig Brady
2002-09-25 16:11     ` jbradford

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=200209250749.g8P7nmiT000178@darkstar.example.net \
    --to=jbradford@dial.pipex.com \
    --cc=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=padraig.brady@corvil.com \
    /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;
as well as URLs for NNTP newsgroup(s).