Messages in this thread | | | Date | Fri, 1 Jun 2007 22:55:56 +0200 | From | "Tuncer Ayaz" <> | Subject | Re: 2.6.22 libata spindown |
| |
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. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |