From owner-freebsd-current  Tue Oct 30 16:38: 8 2001
Delivered-To: freebsd-current@freebsd.org
Received: from magic.adaptec.com (magic.adaptec.com [208.236.45.80])
	by hub.freebsd.org (Postfix) with ESMTP
	id BD7DA37B40A; Tue, 30 Oct 2001 16:37:54 -0800 (PST)
Received: from redfish.adaptec.com (redfish.adaptec.com [162.62.50.11])
	by magic.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id QAA26092;
	Tue, 30 Oct 2001 16:36:46 -0800 (PST)
Received: from btc.btc.adaptec.com (btc.btc.adaptec.com [162.62.64.10])
	by redfish.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id QAA05942;
	Tue, 30 Oct 2001 16:22:29 -0800 (PST)
Received: from hollin.btc.adaptec.com (hollin [162.62.149.56])
	by btc.btc.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id RAA20437;
	Tue, 30 Oct 2001 17:36:43 -0700 (MST)
Received: (from scottl@localhost)
	by hollin.btc.adaptec.com (8.11.6/8.11.4) id f9V0Vnh09046;
	Tue, 30 Oct 2001 17:31:49 -0700 (MST)
	(envelope-from scottl)
Date: Tue, 30 Oct 2001 17:31:49 -0700
From: Scott Long <scott_long@btc.adaptec.com>
To: Nick Hibma <n_hibma@freebsd.org>
Cc: freebsd-current@freebsd.org
Subject: Re: WARNING: Driver mistake: destroy_dev on 154/0
Message-ID: <20011030173149.D8573@hollin.btc.adaptec.com>
References: <XFMail.011030133559.jhb@FreeBSD.org> <20011031000621.V697-100000@heather.plazza.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20011031000621.V697-100000@heather.plazza.uk>
User-Agent: Mutt/1.3.23i
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG

On Wed, Oct 31, 2001 at 12:10:14AM +0000, Nick Hibma wrote:
> 
> Yes. I have no idea why phk has not done this.
> 
> As this is a purposeful panicing of systems that worked fine before, I
> presume that someone is keeping track of the problems that are occurring
> and going to do something about it? Or is this a bad case of 'someone
> else's problem'?

This was debated ad nausium over the weekend, with the end resulting being
a Pay-Per-View deathmatch between phk and grog (to be held at the next
Geek Wrestlemania so I hear).  In this case, the change actually exposed
a long-ignored bug in an *extremely* bogus piece of code in the asr
driver.  I've applied a Band-Aid to the driver until the author comes
up with a suitable fix.

Scott

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message