From owner-freebsd-current@FreeBSD.ORG Wed May 5 13:03:59 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 2A57816A4CE for ; Wed, 5 May 2004 13:03:59 -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 3019143D1F for ; Wed, 5 May 2004 13:03:58 -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 i45K3pcV050694; Wed, 5 May 2004 22:03:56 +0200 (CEST) (envelope-from sos@DeepCore.dk) Message-ID: <409948A7.1040100@DeepCore.dk> Date: Wed, 05 May 2004 22:03:51 +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> In-Reply-To: <20040505195425.GA2559@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:03:59 -0000 Mark Santcroos wrote: > Hi, > > I finally took the time to find out why I can't get a coredump on panic: > > ata_controlcmd(&ch->device[MASTER], ATA_FLUSHCACHE, 0, 0, 0); > > never returns in ata_shutdown() on my system (dmesg attached). > > Commenting it out gives me back my coredumps! ;) > > Have you seen this before? Nope, but I have seen a few disks that claims to support flush and then do wierd things when asked to... > If not, should we maybe create some blacklist of chips that report that > they can flush but in reality can't ... That would be blacklist of disks then, hmm, I'm not a fan of blacklists actually, they tend to always be as incorrect and incomplete as not having any. 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... -- -Søren