From owner-freebsd-current@FreeBSD.ORG Fri Jun 8 19:25:39 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2D1D616A41F for ; Fri, 8 Jun 2007 19:25:39 +0000 (UTC) (envelope-from SRS0=80c147f75a2eca3d95877361f038523cef757dc0=360=es.net=oberman@es.net) Received: from postal1.es.net (postal2.es.net [198.128.3.206]) by mx1.freebsd.org (Postfix) with ESMTP id 0D43313C44C for ; Fri, 8 Jun 2007 19:25:39 +0000 (UTC) (envelope-from SRS0=80c147f75a2eca3d95877361f038523cef757dc0=360=es.net=oberman@es.net) Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by postal2.es.net (Postal Node 2) with ESMTP (SSL) id NZH40238; Fri, 08 Jun 2007 12:25:38 -0700 Received: from ptavv.es.net (ptavv.es.net [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 956C745042; Fri, 8 Jun 2007 12:25:38 -0700 (PDT) To: "Poul-Henning Kamp" In-Reply-To: Your message of "Fri, 08 Jun 2007 18:18:04 -0000." <16413.1181326684@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_1181330738_16095P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Fri, 08 Jun 2007 12:25:38 -0700 From: "Kevin Oberman" Message-Id: <20070608192538.956C745042@ptavv.es.net> Cc: freebsd-current@freebsd.org Subject: Re: bge auto-negotiation fails with recent current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jun 2007 19:25:39 -0000 --==_Exmh_1181330738_16095P Content-Type: text/plain; charset=us-ascii Content-Disposition: inline > From: "Poul-Henning Kamp" > Date: Fri, 08 Jun 2007 18:18:04 +0000 > Sender: phk@critter.freebsd.dk > > > I have the exact same behaviour with if_re in my "zepto 6615WD" > laptop. > > Dmesg: > re0: port 0x3000-0x30ff mem 0xcc000000-0xcc000fff irq 16 at device 0.0 on pci2 > miibus0: on re0 > rgephy0: PHY 1 on miibus0 > rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto > re0: Ethernet address: 00:a0:d1:c1:f9:ad > re0: [FILTER] This implies it might be tied to some common code in the PHY/MII code. Has anyone else seen anything like this other than brgphy and rgephy? -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 --==_Exmh_1181330738_16095P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) Comment: Exmh version 2.5 06/03/2002 iD8DBQFGaa0ykn3rs5h7N1ERAkQzAKCYd9maJgxitMn3f49V8nWzyHq4RwCeLcGF LOaTtQUvV03dxKWlPeNgMh4= =u7SO -----END PGP SIGNATURE----- --==_Exmh_1181330738_16095P--