From owner-freebsd-current@FreeBSD.ORG  Thu May  6 05:05:43 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 DA6F316A4CE
	for <current@FreeBSD.org>; Thu,  6 May 2004 05:05:43 -0700 (PDT)
Received: from postman.ripe.net (postman.ripe.net [193.0.0.199])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 78AEB43D5F
	for <current@FreeBSD.org>; Thu,  6 May 2004 05:05:43 -0700 (PDT)
	(envelope-from marks@dell-laptop.6bone.nl)
Received: by postman.ripe.net (Postfix, from userid 8)
	id E0CEC51C5D; Thu,  6 May 2004 14:05:42 +0200 (CEST)
Received: from birch.ripe.net (birch.ripe.net [193.0.1.96])
	by postman.ripe.net (Postfix) with ESMTP
	id 9BEAB4E400; Thu,  6 May 2004 14:05:42 +0200 (CEST)
Received: from dell-laptop.6bone.nl (cow.ripe.net [193.0.1.239])
	by birch.ripe.net (8.12.10/8.11.6) with SMTP id i46C5gVt008381;
	Thu, 6 May 2004 14:05:42 +0200
Received: (nullmailer pid 1223 invoked by uid 1001);
	Thu, 06 May 2004 12:05:42 -0000
Date: Thu, 6 May 2004 14:05:42 +0200
From: Mark Santcroos <marks@ripe.net>
To: Bruce Evans <bde@zeta.org.au>
Message-ID: <20040506120541.GA1131@laptop.6bone.nl>
References: <20040505195425.GA2559@laptop.6bone.nl>
	<409948A7.1040100@DeepCore.dk> <20040506212202.O19882@gamplex.bde.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040506212202.O19882@gamplex.bde.org>
User-Agent: Mutt/1.4.2.1i
X-Handles: MS6-6BONE, MS18417-RIPE
X-RIPE-Spam-Level: 
X-RIPE-Spam-Status: N 0.000605 / 0.0 / 0.0 / disabled
X-RIPE-Signature: 3e8e3045e9b7c76b5eeac83422cf2b56
cc: current@FreeBSD.org
cc: S?ren Schmidt <sos@DeepCore.dk>
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
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 06 May 2004 12:05:44 -0000

On Thu, May 06, 2004 at 09:36:31PM +1000, Bruce Evans wrote:
> Panic dumps cannot use either device interrupts or timeouts, not to
> mention normal locks, since panics may occur in almost any context;
> in particular they may occur with all interrupts masked and important
> locks in a bad state.  Immediate mode must be used, but it doesn't
> seem to be, and a comment says that it is only used for other things:

My eye felt on the same code and comments!

But if this is indeed the problem, why isn't everyone experiencing this
issue?

Stated differently, are there problems with using ATA_IMMEDIATE_MODE?

Mark