Re: Intel 82574 issue reported on Slashdot

in message <A18965A6-8D17-4919-9947-FE43D250354F@gsoft.com.au>,
wrote Daniel O'Connor thusly...
>
>
> 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:
> >
> > http://communities.intel.com/community/wired/blog/2013/02/07/intel-82574l-gigabit-ethernet-controller-statement
> >
> > 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.

Gift^WStraight from horse's mouth ...

  http://blog.krisk.org/2013/02/packets-of-death.html

  http://www.kriskinc.com/intel-pod

  - parv

-- 

_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"