Date: Mon, 6 Nov 2006 22:42:18 -0800 From: "Jack Vogel" <jfvogel@gmail.com> To: "Adrian Chadd" <adrian@freebsd.org> Cc: freebsd-stable@freebsd.org Subject: Re: em driver testing Message-ID: <2a41acea0611062242h42b1bde6w711e9a5039ed1a90@mail.gmail.com> In-Reply-To: <d763ac660611062047n67058489jeca8d4c79e8c7490@mail.gmail.com> References: <68011C68-0962-4946-88E1-F36EE7C707DA@redstarling.com> <20061106221219.GA66676@hugo10.ka.punkt.de> <041201c701f9$37b2aed0$9603a8c0@claylaptop> <2a41acea0611061614n478efe77y82c0ebc2e1b01e19@mail.gmail.com> <d763ac660611062047n67058489jeca8d4c79e8c7490@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11/6/06, Adrian Chadd <adrian@freebsd.org> wrote: > Just out of curiousity - why wasn't the offending MPSAFE related > changes to em just reverted after discovering the em instability? The > driver -was- stable a couple of months ago, no? Actually it was not. Some reports have cited problems back to 6.0 or before. The watchdog design was fundamentally flawed from an SMP point of view and needed to be changed. We also didnt want to go backwards if possible. My Intel driver had support for new hardware that was good to pick up. There's lots of new stuff coming too, so stay tuned :) Jack
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2a41acea0611062242h42b1bde6w711e9a5039ed1a90>