Aw: Re: Re: Realtek 8168/8111 if_re not working in current r295091

From: <s.o.k_at_web.de>
Date: Fri, 5 Feb 2016 22:56:45 +0100
Hi, this is the line from verbose boot:

re0: <RealTek 8168/8111 B/C/CP/D/DP/E/F/G PCIe Gigabit Ethernet> port 0xe000-0xe0ff mem
re0: Chip rev. 0x2c800000
re0: MAC rev. 0x00100000
rgephy0: <RTL8169S/8110S/8211 1000BASE-T media interface> PHY 1 on miibus0
rgephy0: OUI 0x00e04c, model 0x0011, rev. 5

so it is an even older rev: 5.

I will try reverting to r290946 and r290566 respectivly over the weekend and post my results accordingly.

Regards, Stefan

PS: I ran accidentally on r290151, as I started syncing and building Current (coming from 10-2 Stable) on Nov 1st; I was distracted over the holiday season and only started updating again a fortnight ago, when I stumbled into the problem with the re driver.

> Unfortunately, it doesn't make a whole lot of sense to me; 0x2c800000
> translates to RL_HWREV_8168E_VL, which is an older chip that should
> never have required the handling of RTL8168G and later revisions (or
> may not actually work when applying it). So r290566 should only make
> a positive difference, if it changes anyting for that revision all.
> Did the interface work before r290151, or actually before r281337?
> Does reverting r290946 and r290566 locally make it work again?
> Another candidate causing that breakage would be r291676 if the PHY
> is an RTL8211F one. If you boot verbosely, you'll have a line in the
> dmesg(8) output with "OUI 0x00e04c" in it. If the "rev." number in
> that line is 6, you have an RTL8211F.
> 
> Marius
> 
> 
Received on Fri Feb 05 2016 - 21:02:14 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:02 UTC