Date: Tue, 16 Jan 2007 19:07:34 -0800 From: "Jack Vogel" <jfvogel@gmail.com> To: "Jack Vogel" <jfvogel@gmail.com>, "Mike Andrews" <mandrews@bit0.com>, freebsd-stable@freebsd.org Subject: Re: 6.2-RELEASE em0 watchdog timeouts -- sometimes (w/ partial workaround) Message-ID: <2a41acea0701161907v5bf56c6evf5eef7fdb2311eb3@mail.gmail.com> In-Reply-To: <20070117025927.GA25196@icarus.home.lan> References: <20070116123019.I46509@bit0.com> <2a41acea0701161053s67c6100cqf03284626116f04c@mail.gmail.com> <20070117025927.GA25196@icarus.home.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
On 1/16/07, Jeremy Chadwick <koitsu@freebsd.org> wrote: > On Tue, Jan 16, 2007 at 10:53:04AM -0800, Jack Vogel wrote: > > There are some management related issues with this NIC, first if you > > have not done so make a DOS bootable device, and run this app I > > am enclosing, it fixes the prom setting that is wrong on some devices. > > It will do no harm, and it may solve things. > > Jack, > > Can you expand on what this application changes in the PROM? I have > an Intel motherboard which suffers from similar to what the OP has > reported (em0 watchdog timeouts), and was curious what the utility > does before firing up the board and trying it. Others may be curious > to know, too. Hmmm, I'm rusty on this, its now been a year or more since I was first involved in the details, so I may need to amend this later :) But from memory, the issue is the value programmed into the MANC register by the PROM, I don't remember what bit it was, but one bit is mistakenly set, it causes the hardware to incorrectly intercept some packets. I was snowbound today, but I'll doublecheck on the detail tomorrow and amend if needed. Everyone note that this ONLY effects an 82573 NIC, so make sure of that before anything else. Cheers, Jack
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2a41acea0701161907v5bf56c6evf5eef7fdb2311eb3>