Date: Sat, 9 Feb 2013 11:07:51 +1030 From: "Daniel O'Connor" <doconnor@gsoft.com.au> To: Jack Vogel <jfvogel@gmail.com> Cc: FreeBSD stable <freebsd-stable@freebsd.org>, "Pieper, Jeffrey E" <jeffrey.e.pieper@intel.com>, FreeBSD Net <freebsd-net@freebsd.org>, "Hearn, James R" <james.r.hearn@intel.com>, "Vogel, Jack" <jack.vogel@intel.com>, "Ronciak, John" <john.ronciak@intel.com>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: Intel 82574 issue reported on Slashdot Message-ID: <A18965A6-8D17-4919-9947-FE43D250354F@gsoft.com.au> In-Reply-To: <CAFOYbc=kYHRBet_M_3-U_6JkBqos4tF1oMamYKXswsvRyG3cuw@mail.gmail.com> References: <CAFOYbc=kYHRBet_M_3-U_6JkBqos4tF1oMamYKXswsvRyG3cuw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 09/02/2013, at 4:46, Jack Vogel <jfvogel@gmail.com> wrote: > recommends contacting your motherboard manufacturer if you have = continued > concerns or questions whether your products are impacted. > Here is the link: >=20 > = http://communities.intel.com/community/wired/blog/2013/02/07/intel-82574l-= gigabit-ethernet-controller-statement >=20 > Any questions or concerns may be sent to me. In all honesty.. The blog post (and your email) are basically = information free, they don't name names and provide no script or = downloadable code that will allow end users to check if they are = affected. "Contact your motherboard manufacturer" is much more time consuming than = "Run sysctl... | grep foo | awk ..." to see if your system is affected. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A18965A6-8D17-4919-9947-FE43D250354F>