On Fri, 2013-02-08 at 10:16 -0800, Jack Vogel wrote:
> For those that may have run across the story on Slashdot about this NIC,
> here is our statement:
>
> Recently there were a few stories published, based on a blog post by an
> end-user, suggesting specific network packets may cause the Intel®
On 09/02/2013, at 20:42, Parv wrote:
>> "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
I've
in message ,
wrote Daniel O'Connor thusly...
>
>
> On 09/02/2013, at 4:46, Jack Vogel 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/com
On 09/02/2013, at 4:46, Jack Vogel 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-co
For those that may have run across the story on Slashdot about this NIC,
here is our statement:
Recently there were a few stories published, based on a blog post by an
end-user, suggesting specific network packets may cause the Intel® 82574L
Gigabit Ethernet Controller to become unresponsive until
