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 already read this.

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

I'd really rather a test which reads the EEPROM and tells me if it's a problem 
rather than hang the interface on a machine :)

In any case that isn't the point - this may be a "vendor issue" but it reflects 
poorly on Intel that they didn't take proper ownership of the issue. It would 
be far, far better for their image to say "some systems may have the fault, go 
to http://.... to find a way to test for your operating system".

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

freebsd-current@freebsd.org mailing list
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Reply via email to