From owner-freebsd-bugs@FreeBSD.ORG  Fri Apr  2 12:49:45 2004
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 5CF4F16A4CE; Fri,  2 Apr 2004 12:49:45 -0800 (PST)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id BE43543D3F; Fri,  2 Apr 2004 12:49:44 -0800 (PST)
	(envelope-from phk@phk.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.12.11/8.12.11) with ESMTP id i32Knexi037792;
	Fri, 2 Apr 2004 22:49:40 +0200 (CEST)
	(envelope-from phk@phk.freebsd.dk)
To: Paul Saab <ps@mu.org>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Fri, 02 Apr 2004 12:43:03 -0800."
             <20040402204303.GA97274@elvis.mu.org> 
Date: Fri, 02 Apr 2004 22:49:40 +0200
Message-ID: <37791.1080938980@critter.freebsd.dk>
cc: Vinod Kashyap <vkashyap@3WARE.com>
cc: freebsd-bugs@freebsd.org
cc: 'Artem Koutchine' <matrix@itlegion.ru>
cc: freebsd-current@freebsd.org
Subject: Re: there is a bug in twe driver or disk subsystem for sure 
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Apr 2004 20:49:45 -0000

In message <20040402204303.GA97274@elvis.mu.org>, Paul Saab writes:
>Poul-Henning Kamp (phk@phk.freebsd.dk) wrote:
>> You're wrong vinod, the bug _is_ most likely in the 3ware driver.
>
>No, the guy is claiming the 3ware driver is buggy because of the
>error reported on reboot, which is standard now for any filesystem
>which is mounted and you try to unload the driver (such as on reboot).
>Granted this error should probably be silented for this case, but without
>a full stacktrace, we have no idea where the bug is coming from.
>
>I have a similar config at the office and have been unable to reproduce
>this problem, but i also haven't tried very hard.

You have DIAGNOSTICS in the kernel ?

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.