Date: Wed, 18 Jan 2012 20:01:42 -0500 From: Michael Butler <imb@protected-networks.net> To: pyunyh@gmail.com Cc: current@freebsd.org Subject: Re: Intermittent re0 phy failure Message-ID: <4F176B76.5010809@protected-networks.net> In-Reply-To: <20120119005457.GE7469@michelle.cdnetworks.com> References: <4F174C4F.2010302@protected-networks.net> <20120119005457.GE7469@michelle.cdnetworks.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 01/18/12 19:54, YongHyeon PYUN wrote:
> On Wed, Jan 18, 2012 at 05:48:47PM -0500, Michael Butler wrote:
>> At random intervals, when re0 is without any significant load; idle for
>> lengthy periods, I see ..
>>
>> kernel: re0: PHY read failed
>> last message repeated 4 times
>> kernel: re0: link state changed to DOWN
>>
>> Unplugging the cable and re-inserting is sufficient to restore
>> functionality.
>>
>> kernel is @ SVN r230276
>>
>> Any ideas how to track this down?
>
> Knowing which kind of controller you have would be more helpful.
> Show me both re(4)/rgephy(4) related message from dmesg and
> 'devinfo -rv | grep rgephy' output.
>
As requested:
dmesg:
re0: <RealTek 8168/8111 B/C/CP/D/DP/E/F PCIe Gigabit Ethernet> port
0x2000-0x20ff mem 0xf0700000-0xf0700fff,0xf0200000-0xf0203fff irq 17 at
device 0.0 on pci3
re0: MSI count : 1
re0: MSI-X count : 4
re0: attempting to allocate 1 MSI-X vectors (4 supported)
msi: routing MSI-X IRQ 257 to local APIC 0 vector 51
re0: using IRQ 257 for MSI-X
re0: Using 1 MSI-X message
re0: ASPM disabled
re0: Chip rev. 0x28000000
re0: MAC rev. 0x00000000
miibus0: <MII bus> on re0
rgephy0: <RTL8169S/8110S/8211 1000BASE-T media interface> PHY 1 on miibus0
rgephy0: OUI 0x00e04c, model 0x0011, rev. 2
rgephy0: none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX,
100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master,
1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow,
1000baseT-FDX-flow-master, auto, auto-flow
devinfo -rv | grep rgephy
rgephy0 pnpinfo oui=0xe04c model=0x11 rev=0x2 at phyno=1
imb
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F176B76.5010809>