From owner-freebsd-net@FreeBSD.ORG Fri Feb 8 18:16:58 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 16390941; Fri, 8 Feb 2013 18:16:58 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from mail-ve0-f176.google.com (mail-ve0-f176.google.com [209.85.128.176]) by mx1.freebsd.org (Postfix) with ESMTP id A93716E0; Fri, 8 Feb 2013 18:16:57 +0000 (UTC) Received: by mail-ve0-f176.google.com with SMTP id cz10so3548090veb.21 for ; Fri, 08 Feb 2013 10:16:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to:cc :content-type; bh=/HWKFgz9ZwkiIxlnuu1o7XRIvTSkuVs3bQva9h97swI=; b=cRpzOlHfJOoNMeQHaRLycuqq/MdFZph7Ag1sMD0Q9pkjTIFqoKiCPUFf9t+3jZYdm7 SNolqxT2lGw4tCy85YjurATp8B97qX3gG6FVnXDk/W/xEhwrOorPKeXsf4uw5mJOgyos dli1NHcEw5PhjSfcL23+zACjmLHTBwjnZfn8pnWpZ0Fs0x2VsctWJAEoPBBEceziV7Nc tCskHB5KoakPq6fb+vp5iU6mAUpZvpnpfz3h61cHySnzAdYghotJvZDsOJW7TW8JU7Ue UljccQZE8A8Ac7RV3aXLpPmGOqFa7FoQ2UE1bovSROmap+07DYOL3LqUEgN/8/SfKxGw NU/w== MIME-Version: 1.0 X-Received: by 10.52.29.109 with SMTP id j13mr6919204vdh.111.1360347409285; Fri, 08 Feb 2013 10:16:49 -0800 (PST) Received: by 10.220.191.132 with HTTP; Fri, 8 Feb 2013 10:16:49 -0800 (PST) Date: Fri, 8 Feb 2013 10:16:49 -0800 Message-ID: Subject: Intel 82574 issue reported on Slashdot From: Jack Vogel To: FreeBSD Net , FreeBSD Current , FreeBSD stable Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "Pieper, Jeffrey E" , "Hearn, James R" , "Ronciak, John" , "Vogel, Jack" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Feb 2013 18:16:58 -0000 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=AE 82574L Gigabit Ethernet Controller to become unresponsive until corrected by a full platform power cycle. Intel was made aware of this issue in September 2012 by the blogs author. Intel worked with the author as well as the original motherboard manufacturer to investigate and determine root cause. Intel root caused the issue to the specific vendor=92s mother board design where an incorrect EEPROM image was programmed during manufacturing. We communicated the findings and recommended corrections to the motherboard manufacturer. It is Intel=92s belief that this is an implementation issue isolated to a specific manufacturer, not a design problem with the Intel 82574L Gigabit Ethernet controller. Intel has not observed this issue with any implementations which follow Intel=92s published design guidelines. Intel 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-g= igabit-ethernet-controller-statement Any questions or concerns may be sent to me. Cheers, Jack