From owner-freebsd-current@FreeBSD.ORG Fri Apr 2 12:53: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 1ED7616A4CF; Fri, 2 Apr 2004 12:53:59 -0800 (PST) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 13B2C43D4C; Fri, 2 Apr 2004 12:53:59 -0800 (PST) (envelope-from ps@mu.org) Received: by elvis.mu.org (Postfix, from userid 1000) id 0BF8E5C808; Fri, 2 Apr 2004 12:53:59 -0800 (PST) Date: Fri, 2 Apr 2004 12:53:59 -0800 From: Paul Saab To: Poul-Henning Kamp Message-ID: <20040402205359.GA98348@elvis.mu.org> References: <20040402204303.GA97274@elvis.mu.org> <37791.1080938980@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <37791.1080938980@critter.freebsd.dk> User-Agent: Mutt/1.4.2.1i cc: Vinod Kashyap cc: freebsd-bugs@freebsd.org cc: 'Artem Koutchine' cc: freebsd-current@freebsd.org Subject: Re: there is a bug in twe driver or disk subsystem for sure 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: Fri, 02 Apr 2004 20:53:59 -0000 Poul-Henning Kamp (phk@phk.freebsd.dk) wrote: > 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 ? Yes