miibus0: mii_mediachg: can't handle non-zero PHY instance 31

[Yonghyeon PYUN]

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'?