From owner-freebsd-net@FreeBSD.ORG Tue Apr 1 20:29:37 2014 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 804F4B6C; Tue, 1 Apr 2014 20:29:37 +0000 (UTC) Received: from mho-02-ewr.mailhop.org (mho-02-ewr.mailhop.org [204.13.248.72]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3E63287B; Tue, 1 Apr 2014 20:29:37 +0000 (UTC) Received: from c-24-8-230-52.hsd1.co.comcast.net ([24.8.230.52] helo=damnhippie.dyndns.org) by mho-02-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1WV5JK-000Bid-3K; Tue, 01 Apr 2014 20:29:30 +0000 Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id s31KTR6o084889; Tue, 1 Apr 2014 14:29:27 -0600 (MDT) (envelope-from ian@FreeBSD.org) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 24.8.230.52 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1+1Rzk96lbXP759T3jbeyTp Subject: Re: miibus0: mii_mediachg: can't handle non-zero PHY instance 31 From: Ian Lepore To: Chris H In-Reply-To: References: <2598eeb4c68e23df0789e5e3e8f46d76.authenticated@ultimatedns.net> <20140331050002.GC1359@michelle.cdnetworks.com> <20140401065842.GA1364@michelle.cdnetworks.com> Content-Type: text/plain; charset="us-ascii" Date: Tue, 01 Apr 2014 14:29:27 -0600 Message-ID: <1396384167.81853.210.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: pyunyh@gmail.com, freebsd-net , freebsd-stable X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Apr 2014 20:29:37 -0000 On Tue, 2014-04-01 at 13:19 -0700, Chris H wrote: > [...] > miibus0: on nfe0 > rlphy0: PHY 0 on miibus0 > rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow > rlphy1: PHY 1 on miibus0 > rlphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow > rlphy2: PHY 2 on miibus0 > rlphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow > rlphy3: PHY 3 on miibus0 > rlphy3: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow > rlphy4: PHY 4 on miibus0 > rlphy4: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow > rlphy5: PHY 5 on miibus0 > rlphy5: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow > rlphy6: PHY 6 on miibus0 > rlphy6: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow > rlphy7: PHY 7 on miibus0 > rlphy7: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow > rlphy8: PHY 8 on miibus0 > rlphy8: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow > rlphy9: PHY 9 on miibus0 > rlphy9: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow > rlphy10: PHY 10 on miibus0 > rlphy10: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow > rlphy11: PHY 11 on miibus0 > rlphy11: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow > rlphy12: PHY 12 on miibus0 > rlphy12: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow > rlphy13: PHY 13 on miibus0 > rlphy13: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow > rlphy14: PHY 14 on miibus0 > rlphy14: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow > rlphy15: PHY 15 on miibus0 > rlphy15: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow > rlphy16: PHY 16 on miibus0 > rlphy16: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow > rlphy17: PHY 17 on miibus0 > rlphy17: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow > rlphy18: PHY 18 on miibus0 > rlphy18: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow > rlphy19: PHY 19 on miibus0 > rlphy19: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow > rlphy20: PHY 20 on miibus0 > rlphy20: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow > rlphy21: PHY 21 on miibus0 > rlphy21: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow > rlphy22: PHY 22 on miibus0 > rlphy22: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow > rlphy23: PHY 23 on miibus0 > rlphy23: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow > rlphy24: PHY 24 on miibus0 > rlphy24: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow > rlphy25: PHY 25 on miibus0 > rlphy25: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow > rlphy26: PHY 26 on miibus0 > rlphy26: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow > rlphy27: PHY 27 on miibus0 > rlphy27: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow > rlphy28: PHY 28 on miibus0 > rlphy28: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow > rlphy29: PHY 29 on miibus0 > rlphy29: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow > rlphy30: PHY 30 on miibus0 > rlphy30: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow > rlphy31: PHY 31 on miibus0 > rlphy31: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow [...] > miibus0: mii_mediachg: can't handle non-zero PHY instance 31 > miibus0: mii_mediachg: can't handle non-zero PHY instance 30 > miibus0: mii_mediachg: can't handle non-zero PHY instance 29 > miibus0: mii_mediachg: can't handle non-zero PHY instance 28 > miibus0: mii_mediachg: can't handle non-zero PHY instance 27 > miibus0: mii_mediachg: can't handle non-zero PHY instance 26 > miibus0: mii_mediachg: can't handle non-zero PHY instance 25 > miibus0: mii_mediachg: can't handle non-zero PHY instance 24 > miibus0: mii_mediachg: can't handle non-zero PHY instance 23 > miibus0: mii_mediachg: can't handle non-zero PHY instance 22 > miibus0: mii_mediachg: can't handle non-zero PHY instance 21 > miibus0: mii_mediachg: can't handle non-zero PHY instance 20 > miibus0: mii_mediachg: can't handle non-zero PHY instance 19 > miibus0: mii_mediachg: can't handle non-zero PHY instance 18 > miibus0: mii_mediachg: can't handle non-zero PHY instance 17 > miibus0: mii_mediachg: can't handle non-zero PHY instance 16 > miibus0: mii_mediachg: can't handle non-zero PHY instance 15 > miibus0: mii_mediachg: can't handle non-zero PHY instance 14 > miibus0: mii_mediachg: can't handle non-zero PHY instance 13 > miibus0: mii_mediachg: can't handle non-zero PHY instance 12 > miibus0: mii_mediachg: can't handle non-zero PHY instance 11 > miibus0: mii_mediachg: can't handle non-zero PHY instance 10 > miibus0: mii_mediachg: can't handle non-zero PHY instance 9 > miibus0: mii_mediachg: can't handle non-zero PHY instance 8 > miibus0: mii_mediachg: can't handle non-zero PHY instance 7 > miibus0: mii_mediachg: can't handle non-zero PHY instance 6 > miibus0: mii_mediachg: can't handle non-zero PHY instance 5 > miibus0: mii_mediachg: can't handle non-zero PHY instance 4 > miibus0: mii_mediachg: can't handle non-zero PHY instance 3 > miibus0: mii_mediachg: can't handle non-zero PHY instance 2 > miibus0: mii_mediachg: can't handle non-zero PHY instance 1 > > As you can see, it looks much the same. I have no idea what > I should do to better inform the driver/kernel how to better > handle it. Or is it the driver, itself? > > Thank you again, for your thoughtful response. > > --Chris > I think the way to fix a phy that responds at all addresses is to set a hint in loader.conf masking out the ones that aren't real, like so: hint.miibus.0.phymask="1" You might be able to set ="0x00000001" to make it more clear it's a bitmask, but I'm not sure of that. -- Ian