From owner-freebsd-net@FreeBSD.ORG Mon Jan 10 21:45:54 2011 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A9A3510656AB; Mon, 10 Jan 2011 21:45:54 +0000 (UTC) (envelope-from jack.vogel@intel.com) Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by mx1.freebsd.org (Postfix) with ESMTP id 883F18FC1F; Mon, 10 Jan 2011 21:45:54 +0000 (UTC) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga102.fm.intel.com with ESMTP; 10 Jan 2011 13:17:29 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.60,303,1291622400"; d="scan'208";a="645391387" Received: from orsmsx602.amr.corp.intel.com ([10.22.226.211]) by fmsmga002.fm.intel.com with ESMTP; 10 Jan 2011 13:17:29 -0800 Received: from orsmsx508.amr.corp.intel.com ([10.22.226.46]) by orsmsx602.amr.corp.intel.com ([10.22.226.211]) with mapi; Mon, 10 Jan 2011 13:17:29 -0800 From: "Vogel, Jack" To: TAKAHASHI Yoshihiro , "jfvogel@gmail.com" Date: Mon, 10 Jan 2011 13:17:29 -0800 Thread-Topic: Supermicro Bladeserver Thread-Index: Acuu5cvMyZ5NemA1SYe02R9/WkZ0agCJaEbQ Message-ID: <1DB50624F8348F48840F2E2CF6040A9D014BC5519A@orsmsx508.amr.corp.intel.com> References: <20110108.124018.59640143160055980.nyan@FreeBSD.org> In-Reply-To: <20110108.124018.59640143160055980.nyan@FreeBSD.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "freebsd-net@freebsd.org" , "freebsd-stable@freebsd.org" Subject: RE: Supermicro Bladeserver X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jan 2011 21:45:54 -0000 We attempted to repro this problem with the 82566DM (ich8 btw) in house and= failed, it worked correctly for my testers. Oh, and just so the mailing lists have an update, the SM Blade problem was = not an issue in the driver, it was a local change in the loader.conf that c= aused the problem. Regards, Jack -----Original Message----- From: TAKAHASHI Yoshihiro [mailto:nyan@FreeBSD.org]=20 Sent: Friday, January 07, 2011 7:40 PM To: jfvogel@gmail.com Cc: freebsd-net@freebsd.org; freebsd-stable@freebsd.org; Vogel, Jack Subject: Re: Supermicro Bladeserver In article Jack Vogel writes: > I am trying to track down a problem being experienced at icir.org using > SuperMicro > bladeservers, the SERDES 82575 interfaces are having connectivity or perh= aps > autoneg problems, resulting in link transitions and watchdog resets. >=20 > The closest hardware my org at Intel has is a Fujitsu server who's blades > also have > this device, but testing on that has failed to repro the problem. >=20 > I was wondering if anyone else out there has this hardware, if so could y= ou > let me > know your experience, have you had problems or not, etc etc? My machine has the following em(4) device and it has a autoneg problem. When I was using 8-stable kernel at 2010/11/01, it has no problem. But I update to 8-stable at 2010/12/01, the kernel is only linked up as 10M. em0@pci0:0:25:0: class=3D0x020000 card=3D0x13d510cf chip=3D0x104a8086 re= v=3D0x02 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D '82566DM Gigabit Network Connection' class =3D network subclass =3D ethernet --- TAKAHASHI Yoshihiro