From owner-freebsd-stable@FreeBSD.ORG Sat Feb 9 10:15:41 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id BB5D12D3; Sat, 9 Feb 2013 10:15:41 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id 420451D2; Sat, 9 Feb 2013 10:15:40 +0000 (UTC) Received: from ur.dons.net.au (ppp118-210-73-50.lns20.adl2.internode.on.net [118.210.73.50]) (authenticated bits=0) by cain.gsoft.com.au (8.14.4/8.14.3) with ESMTP id r19AFQce071839 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 9 Feb 2013 20:45:32 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Subject: Re: Intel 82574 issue reported on Slashdot Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Content-Type: text/plain; charset=us-ascii From: "Daniel O'Connor" In-Reply-To: <20130209101219.GA2133@holstein.holy.cow> Date: Sat, 9 Feb 2013 20:45:26 +1030 Content-Transfer-Encoding: quoted-printable Message-Id: <1D962264-6DF6-4192-8190-34E22AADE843@gsoft.com.au> References: <20130209101219.GA2133@holstein.holy.cow> To: Parv X-Mailer: Apple Mail (2.1499) X-Spam-Score: 0.163 () BAYES_00,RDNS_DYNAMIC X-Scanned-By: MIMEDefang 2.67 on 203.31.81.10 Cc: FreeBSD stable , FreeBSD Current , "Pieper, Jeffrey E" , FreeBSD Net , "Hearn, James R" , "Vogel, Jack" , "Ronciak, John" , Jack Vogel X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Feb 2013 10:15:41 -0000 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. >=20 > Gift^WStraight from horse's mouth ... >=20 > 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