there is a bug in twe driver or disk subsystem for sure

[Poul-Henning Kamp]

In message <20040402204303.GA97274 at elvis.mu.org>, Paul Saab writes:
>Poul-Henning Kamp (phk at 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 at 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.