From owner-freebsd-net@FreeBSD.ORG Mon Jan 18 20:59:50 2010 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 E51B0106566B; Mon, 18 Jan 2010 20:59:50 +0000 (UTC) (envelope-from davidch@broadcom.com) Received: from MMS3.broadcom.com (mms3.broadcom.com [216.31.210.19]) by mx1.freebsd.org (Postfix) with ESMTP id 80D688FC08; Mon, 18 Jan 2010 20:59:50 +0000 (UTC) Received: from [10.9.200.133] by MMS3.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Mon, 18 Jan 2010 12:59:38 -0800 X-Server-Uuid: B55A25B1-5D7D-41F8-BC53-C57E7AD3C201 Received: from IRVEXCHCCR01.corp.ad.broadcom.com ([10.252.49.30]) by IRVEXCHHUB02.corp.ad.broadcom.com ([10.9.200.133]) with mapi; Mon, 18 Jan 2010 13:01:01 -0800 From: "David Christensen" To: "pyunyh@gmail.com" , "Charles Owens" Date: Mon, 18 Jan 2010 12:59:36 -0800 Thread-Topic: "PHY read timeout" with bce2 & 3 on FreeBSD 8.0 Thread-Index: AcqYdifB3jRI1WCXS46MfB+yGPXJ3AACdbww Message-ID: <5D267A3F22FD854F8F48B3D2B52381933A537E201E@IRVEXCHCCR01.corp.ad.broadcom.com> References: <4B548107.5050603@greatbaysoftware.com> <20100118194039.GA1336@michelle.cdnetworks.com> In-Reply-To: <20100118194039.GA1336@michelle.cdnetworks.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 X-WSS-ID: 674A14303J880272690-01-01 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Cc: "freebsd-net@freebsd.org" , "davidch@FreeBSD.org" Subject: RE: "PHY read timeout" with bce2 & 3 on FreeBSD 8.0 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, 18 Jan 2010 20:59:51 -0000 > > I'm working with a system (IBM System x3550 M2) that has=20 > four onboard > > bce(4) NICs. Using FreeBSD 8.0, the first two seem to=20 > function fine,=20 > > but the second two do not, yielding messages like this when=20 > a cable is > > inserted: > >=20 > > Jan 12 10:37:19 dmz55 kernel: <2<>N2M>NINM IM INISMI AI S AIIS SAA=20 > > 22cc2,,c , E2EIcIES,SIAS AA E I00 Jan 12 10:37:19 dmz55 kernel: > > Jan 12 10:37:19 dmz55 kernel: S0 > > Jan 12 10:37:19 dmz55 kernel: > > Jan 12 10:37:19 dmz55 kernel: <<22>>A > > Jan 12 10:37:19 dmz55 kernel: > > Jan 12 10:37:19 dmz55 kernel: 0 > > Jan 12 10:37:28 dmz55 kernel: bce2:=20 > /usr/src/sys/dev/bce/if_bce.c(1533): > > Error: PHY read timeout! > > phy =3D 1, reg =3D 0x0001 > >=20 > >=20 > > What's are the best next steps to take in figuring this=20 > out? Thanks in > > advance for any assistance. Kernel boot log appending below. > >=20 >=20 > Are you using ASF/IMPI/UMP on bce2 or bce3? > If so would you try attached patch? Publicly available datasheet > lacks details on management firmware handling so I'm not sure what > is really happening here. > davidch may shed light on this(CCed). The first lines include a lot of N's, M's, and I's, which make me think an NMI may be occurring. Does the garbled text and the PHY timeout error disappear if you disable bce2/bce3? Can you try adding "options PRINTF_BUFR_SIZE=3D256" to your kernel config file to try and de-garble the output? Dave=