Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932237AbXFAU4g (ORCPT ); Fri, 1 Jun 2007 16:56:36 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1764890AbXFAUz7 (ORCPT ); Fri, 1 Jun 2007 16:55:59 -0400 Received: from wx-out-0506.google.com ([66.249.82.237]:40892 "EHLO wx-out-0506.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1764598AbXFAUz5 (ORCPT ); Fri, 1 Jun 2007 16:55:57 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Q3FKloZyJZivo3L3EvQxOrgnwvDLEUl47optqEM23BFrPOw8H/ypD3B9pBPft2EonzfVCZft/qs7hZ6vg5ad6Poz6/gBcHMVhO8kAauGM2kHeIa/ccMuNiyknBQ+soCt/MGNrp1oc5qzr9YRITTC0bdPqo4ZTuChXCNChBVjEUo= Message-ID: <4ac8254d0706011355y71f9c0b1q237617c6c0fb89c7@mail.gmail.com> Date: Fri, 1 Jun 2007 22:55:56 +0200 From: "Tuncer Ayaz" To: "Jeff Garzik" Subject: Re: 2.6.22 libata spindown Cc: linux-kernel@vger.kernel.org, "IDE/ATA development list" In-Reply-To: <4660841D.5050003@garzik.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4ac8254d0706011314g5468f02m3cf5a5281bd30018@mail.gmail.com> <4660841D.5050003@garzik.org> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1340 Lines: 38 On 6/1/07, Jeff Garzik 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/