From owner-freebsd-stable@FreeBSD.ORG Sat Feb 9 00:38:25 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 050EFF81; Sat, 9 Feb 2013 00:38:25 +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 7F730CC8; Sat, 9 Feb 2013 00:38:23 +0000 (UTC) Received: from [10.138.22.220] ([1.124.113.155]) (authenticated bits=0) by cain.gsoft.com.au (8.14.4/8.14.3) with ESMTP id r190bqro039647 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 9 Feb 2013 11:07:59 +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=windows-1252 From: "Daniel O'Connor" In-Reply-To: Date: Sat, 9 Feb 2013 11:07:51 +1030 Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Jack Vogel X-Mailer: Apple Mail (2.1499) X-Spam-Score: -0.023 () BAYES_00,HELO_MISC_IP,RDNS_NONE X-Scanned-By: MIMEDefang 2.67 on 203.31.81.10 Cc: FreeBSD stable , "Pieper, Jeffrey E" , FreeBSD Net , "Hearn, James R" , "Vogel, Jack" , "Ronciak, John" , FreeBSD Current 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 00:38:25 -0000 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: >=20 > = http://communities.intel.com/community/wired/blog/2013/02/07/intel-82574l-= gigabit-ethernet-controller-statement >=20 > 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. -- 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