Re: Intermittent re0 phy failure
On Mon, Jan 30, 2012 at 05:32:06PM -0500, Michael Butler wrote: On 01/18/12 20:52, YongHyeon PYUN wrote: On Wed, Jan 18, 2012 at 08:01:42PM -0500, Michael Butler wrote: 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. [ .. snip .. ] Thanks a lot. Would you try attached patch? Since applying this (for 8168D) and the patch at SVN r230336 (which affected another system of mine), neither system has gone deaf, Thanks for testing. Committed to HEAD(r231622). Thanks! imb ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Intermittent re0 phy failure
On 01/18/12 20:52, YongHyeon PYUN wrote: On Wed, Jan 18, 2012 at 08:01:42PM -0500, Michael Butler wrote: 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. [ .. snip .. ] Thanks a lot. Would you try attached patch? Since applying this (for 8168D) and the patch at SVN r230336 (which affected another system of mine), neither system has gone deaf, Thanks! imb ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Intermittent re0 phy failure
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? imb ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Intermittent re0 phy failure
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 0xf070-0xf0700fff,0xf020-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. 0x2800 re0: MAC rev. 0x 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 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Intermittent re0 phy failure
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. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Intermittent re0 phy failure
On Wed, Jan 18, 2012 at 08:01:42PM -0500, Michael Butler wrote: 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 0xf070-0xf0700fff,0xf020-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. 0x2800 re0: MAC rev. 0x 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 Thanks a lot. Would you try attached patch? Index: sys/dev/re/if_re.c === --- sys/dev/re/if_re.c (revision 230315) +++ sys/dev/re/if_re.c (working copy) @@ -1433,11 +1433,16 @@ sc-rl_flags |= RL_FLAG_MACSLEEP; /* FALLTHROUGH */ case RL_HWREV_8168CP: - case RL_HWREV_8168D: sc-rl_flags |= RL_FLAG_PHYWAKE | RL_FLAG_PAR | RL_FLAG_DESCV2 | RL_FLAG_MACSTAT | RL_FLAG_CMDSTOP | RL_FLAG_AUTOPAD | RL_FLAG_JUMBOV2 | RL_FLAG_WOL_MANLINK; break; + case RL_HWREV_8168D: + sc-rl_flags |= RL_FLAG_PHYWAKE | RL_FLAG_PHYWAKE_PM | + RL_FLAG_PAR | RL_FLAG_DESCV2 | RL_FLAG_MACSTAT | + RL_FLAG_CMDSTOP | RL_FLAG_AUTOPAD | RL_FLAG_JUMBOV2 | + RL_FLAG_WOL_MANLINK; + break; case RL_HWREV_8168DP: sc-rl_flags |= RL_FLAG_PHYWAKE | RL_FLAG_PAR | RL_FLAG_DESCV2 | RL_FLAG_MACSTAT | RL_FLAG_AUTOPAD | ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Intermittent re0 phy failure
On 01/18/12 20:52, YongHyeon PYUN wrote: Thanks a lot. Would you try attached patch? Compiled, installed and running - I'll see if I can reproduce the failure. Thanks very much for your quick response :-) imb ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
