Date: Mon, 9 Jun 2008 18:35:37 -0700 From: "Paul Saab" <ps@mu.org> To: freebsd-net@freebsd.org Subject: Re: Anyone seen this error on em ? Message-ID: <5c0ff6a70806091835p2c206fe2p203b37433b87e073@mail.gmail.com> In-Reply-To: <2a41acea0806091811t2d085d64ra9e9e24029e91d73@mail.gmail.com> References: <m2zlpuxmo0.wl%gnn@neville-neil.com> <484DC272.6020002@acm.poly.edu> <484DD008.6090009@modulus.org> <2a41acea0806091811t2d085d64ra9e9e24029e91d73@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
http://yogurt.org/FreeBSD/em.diff On Mon, Jun 9, 2008 at 6:11 PM, Jack Vogel <jfvogel@gmail.com> wrote: > There is more than one problem that results in the same error in the > core driver, the more common one is actually fixed, as Andrew notes, > in the shared code in the latest driver. However, this is a more obscure > bug that occurs on some hardware, and it seems to require that you have > a management BMC, this is what Paul Saab is seeing, there is not a final > fix for this issue yet. > > Note that both these problems only occur with the esb2lan type NIC. > > Jack > > > On Mon, Jun 9, 2008 at 5:51 PM, Andrew Snow <andrew@modulus.org> wrote: > >> Just a "me, too." Also on a Supermicro board, and it happens on some > >> boots, but not all. > > > > > > I used to have this problem, but it went away after upgrading FreeBSD > > version (7-stable) > > > > - Andrew > > _______________________________________________ > > freebsd-net@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-net > > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5c0ff6a70806091835p2c206fe2p203b37433b87e073>