On Jan 9, 2011, at 4:19 PM, Edward Ned Harvey <opensolarisisdeadlongliveopensola...@nedharvey.com> wrote:
>> From: Pasi Kärkkäinen [mailto:pa...@iki.fi] >> >> Other OS's have had problems with the Broadcom NICs aswell.. > > Yes. The difference is, when I go to support.dell.com and punch in my > service tag, I can download updated firmware and drivers for RHEL that (at > least supposedly) solve the problem. I haven't tested it, but the dell > support guy told me it has worked for RHEL users. There is nothing > available to download for solaris. The drivers are written by Broadcom and are, AFAIK, closed source. By going through Dell, you are going through a middle-man. For example, http://www.broadcom.com/support/ethernet_nic/netxtremeii10.php where you see the release of the Solaris drivers was at the same time as Windows. > > Also, the bcom is not the only problem on that server. After I added-on an > intel network card and disabled the bcom, the weekly crashes stopped, but > now it's ... I don't know ... once every 3 weeks with a slightly different > mode of failure. This is yet again, rare enough that the system could very > well pass a certification test, but not rare enough for me to feel > comfortable putting into production as a primary mission critical server. > > I really think there are only two ways in the world to engineer a good solid > server: > (a) Smoke your own crack. Systems engineering teams use the same systems > that are sold to customers. This is rarely practical, not to mention that product development is often not in the systems engineering organization. > or > (b) Sell millions of 'em. So despite whether or not the engineering team > uses them, you're still going to have sufficient mass to dedicate engineers > to the purpose of post-sales bug solving. yes, indeed :-) -- richard > _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
