freebsd stable - Mar 2014 - miibus0: mii_mediachg: can't handle non-zero PHY instance 31

Greetings,
 I'm not sure whether this best belonged on net@, or stable@
so I'm using both. :)
I'm testing both releng_9, and MB, and I encountered a new
message I don't usually see using the nfe(4) driver:

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

Truncated for brevity (31 lines in total; 1-31). I don't know
how interpret this. An issue with my version of the driver, or
the hardware itself? This occurred with both GENERIC, as well
as my custom kernel.

# uname -a
FreeBSD demon0 9.2-STABLE FreeBSD 9.2-STABLE #0 r263756: Wed Mar 26 11:28:10 PDT
2014
root at demon0:/usr/obj/usr/src/sys/DEMON0  amd64

Thank you for all your time, and consideration.

--Chris

On Sun, Mar 30, 2014 at 01:12:20PM -0700, chrish at UltimateDNS.NET
wrote:
> Greetings,
>  I'm not sure whether this best belonged on net@, or stable@
> so I'm using both. :)
> I'm testing both releng_9, and MB, and I encountered a new
> message I don't usually see using the nfe(4) driver:
> 
> miibus0: mii_mediachg: can't handle non-zero PHY instance 1
> ...
> miibus0: mii_mediachg: can't handle non-zero PHY instance 31
> 
> Truncated for brevity (31 lines in total; 1-31). I don't know
> how interpret this. An issue with my version of the driver, or
> the hardware itself? This occurred with both GENERIC, as well
> as my custom kernel.
Would you show me the dmesg output?
> 
> # uname -a
> FreeBSD demon0 9.2-STABLE FreeBSD 9.2-STABLE #0 r263756: Wed Mar 26
11:28:10 PDT 2014
> root at demon0:/usr/obj/usr/src/sys/DEMON0  amd64
> 
> Thank you for all your time, and consideration.
> 
> --Chris