linux-kernel - Re: 2.6.22 libata spindown

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

Message-ID: <4ac8254d0706011355y71f9c0b1q237617c6c0fb89c7@mail.gmail.com>
Date:	Fri, 1 Jun 2007 22:55:56 +0200
From:	"Tuncer Ayaz" <tuncer.ayaz@...il.com>
To:	"Jeff Garzik" <jeff@...zik.org>
Cc:	linux-kernel@...r.kernel.org,
	"IDE/ATA development list" <linux-ide@...r.kernel.org>
Subject: Re: 2.6.22 libata spindown

On 6/1/07, Jeff Garzik <jeff@...zik.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.
-
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/