From owner-freebsd-bugs@FreeBSD.ORG  Fri Apr  2 12:43:04 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 19AB416A4CE; Fri,  2 Apr 2004 12:43:04 -0800 (PST)
Received: from elvis.mu.org (elvis.mu.org [192.203.228.196])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 0E84E43D46; Fri,  2 Apr 2004 12:43:04 -0800 (PST)
	(envelope-from ps@mu.org)
Received: by elvis.mu.org (Postfix, from userid 1000)
	id 056655C808; Fri,  2 Apr 2004 12:43:04 -0800 (PST)
Date: Fri, 2 Apr 2004 12:43:03 -0800
From: Paul Saab <ps@mu.org>
To: Poul-Henning Kamp <phk@phk.freebsd.dk>
Message-ID: <20040402204303.GA97274@elvis.mu.org>
References: <A1964EDB64C8094DA12D2271C04B812601532143@tabby.3ware.com>
	<36769.1080936529@critter.freebsd.dk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <36769.1080936529@critter.freebsd.dk>
User-Agent: Mutt/1.4.2.1i
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:43:04 -0000

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.