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®
in message a18965a6-8d17-4919-9947-fe43d2503...@gsoft.com.au,
wrote Daniel O'Connor thusly...
On 09/02/2013, at 4:46, Jack Vogel jfvo...@gmail.com wrote:
recommends contacting your motherboard manufacturer if you have
continued concerns or questions whether your products are
impacted.
On 09/02/2013, at 20:42, Parv p...@pair.com 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
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
On 09/02/2013, at 4:46, Jack Vogel jfvo...@gmail.com wrote:
recommends contacting your motherboard manufacturer if you have continued
concerns or questions whether your products are impacted.
Here is the link:
