From owner-freebsd-current@FreeBSD.ORG Wed May 5 13:20:16 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 46AC916A57A for ; Wed, 5 May 2004 13:20:16 -0700 (PDT) Received: from spider.deepcore.dk (cpe.atm2-0-53484.0x50a6c9a6.abnxx9.customer.tele.dk [80.166.201.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 594CB43D46 for ; Wed, 5 May 2004 13:20:15 -0700 (PDT) (envelope-from sos@DeepCore.dk) Received: from DeepCore.dk (sos.deepcore.dk [194.192.25.130]) by spider.deepcore.dk (8.12.11/8.12.10) with ESMTP id i45KK8d0050934; Wed, 5 May 2004 22:20:13 +0200 (CEST) (envelope-from sos@DeepCore.dk) Message-ID: <40994C78.9080707@DeepCore.dk> Date: Wed, 05 May 2004 22:20:08 +0200 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= User-Agent: Mozilla Thunderbird 0.5 (X11/20040329) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mark Santcroos References: <20040505195425.GA2559@laptop.6bone.nl> <409948A7.1040100@DeepCore.dk> <20040505201128.GA768@laptop.6bone.nl> In-Reply-To: <20040505201128.GA768@laptop.6bone.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-mail-scanned: by DeepCore Virus & Spam killer v1.4 cc: current@freebsd.org Subject: Re: ATA_FLUSHCACHE failing X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 May 2004 20:20:16 -0000 Mark Santcroos wrote: > On Wed, May 05, 2004 at 10:03:51PM +0200, S?ren Schmidt wrote: > >>Nope, but I have seen a few disks that claims to support flush and then >>do wierd things when asked to... > > I guess so yes. > > So this is a disk issue instead of a chip issue? I'd think so, however until we have more data we can't be sure... >>We should find out why it does not return, my guess is that >>it doesn't interrupt and the timeout doesn't fire because we are on the >>way down... > > Any hints where to start looking? > > I'll keep investigating myself too. Hmm, first you could enable the ATA request debug code in ata-all.h, then set the ATA_R_DEBUG flag when the flush command is issued. That should give an idea where it goes south... -- -Søren