From owner-freebsd-stable@FreeBSD.ORG Fri Mar 20 01:21:55 2009 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 426771065670; Fri, 20 Mar 2009 01:21:55 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.227]) by mx1.freebsd.org (Postfix) with ESMTP id 02B188FC17; Fri, 20 Mar 2009 01:21:54 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0506.google.com with SMTP id l9so832247rvb.43 for ; Thu, 19 Mar 2009 18:21:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:from:date:to:cc :subject:message-id:reply-to:references:mime-version:content-type :content-disposition:in-reply-to:user-agent; bh=JeqV0DCafpuIh3aoo3P6oXv7wfWYTJxL3pIDxDt0WUQ=; b=h2kfPM6n/GOQxScyD6xsFyAbo2GQv4OxzTl/j0nbdvp4OA7Vi/CRp/Nqsgmnh714Vz byFdGrI0TCXzbWcHCamYVJlf2QR1od+x9OANMsbKl/PVdJWDb34Yxiu4febETq5ffGKQ KQjYjDsvSD6ZoNUxBZrH4O0jDdbTzT2c4acBo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=MskflxPI0yszB59hl7klw8+gGyH+yz5uK+S4Rbmyh+TbuA6wGJu5tji1pH3aSMywcF fB0arO7EGIkw20r10FtVYbGh2ePqbgNGQRDtc5ByOWWioVOSGYVRfjfCxBQbPUrcKJgg HmudkvXrsQ3PWCjOat6V2A+bRA4vBqsGepi4Q= Received: by 10.141.53.4 with SMTP id f4mr1056988rvk.35.1237512114738; Thu, 19 Mar 2009 18:21:54 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ([114.111.62.249]) by mx.google.com with ESMTPS id k2sm3512179rvb.14.2009.03.19.18.21.52 (version=SSLv3 cipher=RC4-MD5); Thu, 19 Mar 2009 18:21:53 -0700 (PDT) Received: by michelle.cdnetworks.co.kr (sSMTP sendmail emulation); Fri, 20 Mar 2009 10:22:23 +0900 From: Pyun YongHyeon Date: Fri, 20 Mar 2009 10:22:23 +0900 To: Steve Wills Message-ID: <20090320012223.GA50100@michelle.cdnetworks.co.kr> References: <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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090309035613.GF5039@michelle.cdnetworks.co.kr> User-Agent: Mutt/1.4.2.3i Cc: stable@freebsd.org, yongari@freebsd.org Subject: Re: 7.1-R to RELENG_7 upgrade breaks re nic X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Mar 2009 01:21:55 -0000 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. > > > > > > > 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)