mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Tuncer Ayaz" <tuncer.ayaz@gmail.com>
To: "Jeff Garzik" <jeff@garzik.org>
Cc: linux-kernel@vger.kernel.org,
	"IDE/ATA development list" <linux-ide@vger.kernel.org>
Subject: Re: 2.6.22 libata spindown
Date: Fri, 1 Jun 2007 22:55:56 +0200	[thread overview]
Message-ID: <4ac8254d0706011355y71f9c0b1q237617c6c0fb89c7@mail.gmail.com> (raw)
In-Reply-To: <4660841D.5050003@garzik.org>

On 6/1/07, Jeff Garzik <jeff@garzik.org> wrote:
> Tuncer Ayaz wrote:
> > I'm still seeing the libata warning that disks were not spun down
> > properly on the following two setups and am wondering whether I need
> > a new shutdown binary or the changeset mentioned below is not meant
> > to fix what I'm triggering by halt'ing.
> >
> > If it's not a bug I will try to update my shutdown utility and if
> > that does not work I promise not to bother lkml about a problem
> > caused by my userland. If it is a bug I hope it will be of interest
> > for 2.6.22 bug tracking.
> >
> > Setup 1:
> > SATA 1 Disks
> > AMD64 3200+
> > nVidia nForce 3 250 (Ultra?)
> > Debian i386 Unstable
> >
> > Setup 2:
> > SATA 2 disks
> > Core 2 Duo E6600
> > Intel 975X
> > Debian x86_64 Unstable
> >
> > Just to be clear what warning I'm talking about:
> > DISK MIGHT NOT BE SPUN DOWN PROPERLY. UPDATE SHUTDOWN UTILITY
> > For more info, visit http://linux-ata.org/shutdown.html
>
>
> IIRC, Debian was the one OS that really did need a shutdown utility
> update, as the message says :)

Thanks for the confirmation.

  reply	other threads:[~2007-06-01 20:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-01 20:14 Tuncer Ayaz
2007-06-01 20:39 ` Jeff Garzik
2007-06-01 20:55   ` Tuncer Ayaz [this message]
2007-06-02  3:23   ` Henrique de Moraes Holschuh

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=4ac8254d0706011355y71f9c0b1q237617c6c0fb89c7@mail.gmail.com \
    --to=tuncer.ayaz@gmail.com \
    --cc=jeff@garzik.org \
    --cc=linux-ide@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®