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.Received on Fri Apr 02 2004 - 10:49:45 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:49 UTC