Date: Tue, 1 Apr 2014 17:53:51 -0700 (PDT) From: "Chris H" <bsd-lists@bsdforge.com> To: pyunyh@gmail.com Cc: freebsd-net <freebsd-net@freebsd.org>, freebsd-stable <freebsd-stable@freebsd.org>, Ian Lepore <ian@freebsd.org> Subject: Re: miibus0: mii_mediachg: can't handle non-zero PHY instance 31 Message-ID: <3f97f5646629043fed5e34a77c9c2f3d.authenticated@ultimatedns.net> In-Reply-To: <20140402003912.GA2938@michelle.cdnetworks.com> References: <2598eeb4c68e23df0789e5e3e8f46d76.authenticated@ultimatedns.net> <20140331050002.GC1359@michelle.cdnetworks.com> <c0a800d2a15f205788ed9ce606c00637.authenticated@ultimatedns.net> <20140401065842.GA1364@michelle.cdnetworks.com> <c73ef96319846b3da07db5785f48fb6a.authenticated@ultimatedns.net> <1396384167.81853.210.camel@revolution.hippie.lan> <41917a9e67d0f4519df4b55f3aa6ebe3.authenticated@ultimatedns.net> <20140402003912.GA2938@michelle.cdnetworks.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Tue, Apr 01, 2014 at 01:40:58PM -0700, Chris H wrote: >> > On Tue, 2014-04-01 at 13:19 -0700, Chris H wrote: >> >> [...] >> >> miibus0: <MII bus> on nfe0 >> >> rlphy0: <RTL8201L 10/100 media interface> PHY 0 on miibus0 >> >> rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow >> >> rlphy1: <RTL8201L 10/100 media interface> PHY 1 on miibus0 >> > [...]---big-snip--8<--- >> >> 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. >> >> Thank you very much for the hint. I'll give it a shot. >> Any idea why this is happening? I have 4 other MB's using the Nvidia >> chipset, and the nfe(4) driver. But they don't respond this way. >> > > If some nfe(4) variants badly behave in probing stage, this should > be handled by driver. We already have too many hints and tunables > and I don't think most users know that. In addition, adding > additional NIC may change miibus instance number. > > Could you show me the output of 'kenv | grep smbios'? Yes, of course. Here it is: smbios.bios.reldate="11/22/2010" smbios.bios.vendor="American Megatrends Inc." smbios.bios.version="V2.7" smbios.chassis.maker="MSI" smbios.chassis.serial="To Be Filled By O.E.M." smbios.chassis.tag="To Be Filled By O.E.M." smbios.chassis.version="2.0" smbios.memory.enabled="2097152" smbios.planar.maker="MSI" smbios.planar.product="K9N6PGM2-V2 (MS-7309)" smbios.planar.serial="To be filled by O.E.M." smbios.planar.version="2.0" smbios.socket.enabled="1" smbios.socket.populated="1" smbios.system.maker="MSI" smbios.system.product="MS-7309" smbios.system.serial="To Be Filled By O.E.M." smbios.system.uuid="00000000-0000-0000-0000-406186cd4497" smbios.system.version="2.0" smbios.version="2.6" Hope this helps, and thank you for all your time, and trouble. --Chris >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3f97f5646629043fed5e34a77c9c2f3d.authenticated>