Date: Fri, 20 Mar 2009 10:22:23 +0900 From: Pyun YongHyeon <pyunyh@gmail.com> To: Steve Wills <STEVE@stevenwills.com> Cc: stable@freebsd.org, yongari@freebsd.org Subject: Re: 7.1-R to RELENG_7 upgrade breaks re nic Message-ID: <20090320012223.GA50100@michelle.cdnetworks.co.kr> In-Reply-To: <20090309035613.GF5039@michelle.cdnetworks.co.kr> References: <AE144701-409A-4D9F-9947-A725B0810ACA@STEVENWILLS.COM> <20090226003842.GB63173@michelle.cdnetworks.co.kr> <95AD32AC-93AE-4945-A18E-CE7099BEC3CA@stevenwills.com> <20090226041023.GD63173@michelle.cdnetworks.co.kr> <594BAC6A-498A-4B82-A18B-EB09FEA2F322@stevenwills.com> <20090226042732.GE63173@michelle.cdnetworks.co.kr> <22F5A82D-290D-4B84-92AB-670EDB49AF22@stevenwills.com> <20090303120734.GB84434@michelle.cdnetworks.co.kr> <26A74AAD-1556-4BA7-8E89-72BE36C667A7@stevenwills.com> <20090309035613.GF5039@michelle.cdnetworks.co.kr>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Mar 09, 2009 at 12:56:13PM +0900, Pyun YongHyeon wrote: > On Sun, Mar 08, 2009 at 09:52:19PM -0400, Steve Wills wrote: > > Hi, > > > > Sorry for the late reply. > > > > On Mar 3, 2009, at 7:07 AM, Pyun YongHyeon wrote: > > >Ok, when you plug UTP cable can you see "re0: link state changed to > > >UP" in dmesg output? Or if you unplug the cable, you should see > > >"re0: link state changed to DOWN"(With "tail -f /var/log/message", > > >you can easily check this.) > > > > Nope. > > > > > > > >If this is not the case something is wrong on RTL8168D. Since > > >you've said re0 works for a short time, can you see "re0: link > > >state changed to DOWN" on your dmesg output right before seeing > > >"re0: PHY read failed" message? > > > > After boot and DHCP, it works for about a minute, then I see "PHY read > > failed" for a few seconds, network continues to work, then I see "link > > state changed to DOWN", network stops working and frequency of read > > failed message increases. Unplugging the cable and plugging it back in > > doesn't change anything or cause the system to log any messages beyond > > "PHY read failed". > > > > >I've also attached patch which may apply to your case. Would you > > >give it spin? Note, the patch was generated against CURRENT, so > > >you should use re(4) in CURRENT. Just save your old re(4)/rl(4) > > >files and download if_re.c, if_rl.c and if_rlreg.h from CURRENT > > >and apply the patch. > > ><re.RTL8168D.patch> > > > > Unfortunately, for me, this patch doesn't change things. > > > > Ok, please try again with attached patch. Any progress here? I've checked changes made in RELENG7 but I failed to see what revision broke RTL8168D support. Can you narrow down which revision broke RTL8168D support if previous patch have no effect? > Index: sys/dev/re/if_re.c > =================================================================== > --- sys/dev/re/if_re.c (revision 189551) > +++ sys/dev/re/if_re.c (working copy) > @@ -1266,6 +1266,8 @@ > /* FALLTHROUGH */ > case RL_HWREV_8168CP: > case RL_HWREV_8168D: > + if (hw_rev->rl_rev == RL_HWREV_8168D) > + sc->rl_flags |= 0x10000; > sc->rl_flags |= RL_FLAG_PHYWAKE | RL_FLAG_PAR | > RL_FLAG_DESCV2 | RL_FLAG_MACSTAT | RL_FLAG_CMDSTOP; > /* > @@ -2061,6 +2063,8 @@ > > RL_LOCK_ASSERT(sc); > > + if ((sc->rl_flags & 0x10000) != 0) > + re_miibus_writereg(sc->rl_dev, 1, 0x1f, 0); > mii = device_get_softc(sc->rl_miibus); > mii_tick(mii); > if ((sc->rl_flags & RL_FLAG_LINK) == 0)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090320012223.GA50100>