Date: Fri, 02 Apr 2004 22:49:40 +0200 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: Paul Saab <ps@mu.org> Cc: freebsd-current@freebsd.org Subject: Re: there is a bug in twe driver or disk subsystem for sure Message-ID: <37791.1080938980@critter.freebsd.dk> In-Reply-To: Your message of "Fri, 02 Apr 2004 12:43:03 -0800." <20040402204303.GA97274@elvis.mu.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?37791.1080938980>