From owner-freebsd-current@freebsd.org Fri Feb 5 22:02:14 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 891E0A9E17F for ; Fri, 5 Feb 2016 22:02:14 +0000 (UTC) (envelope-from s.o.k@web.de) Received: from mout.web.de (mout.web.de [212.227.15.4]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.web.de", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E22F5DA9 for ; Fri, 5 Feb 2016 22:02:13 +0000 (UTC) (envelope-from s.o.k@web.de) Received: from [80.132.210.62] by 3capp-webde-bs40.server.lan (via HTTP); Fri, 5 Feb 2016 22:56:45 +0100 MIME-Version: 1.0 Message-ID: From: s.o.k@web.de To: "Marius Strobl" Cc: freebsd-current@freebsd.org Subject: Aw: Re: Re: Realtek 8168/8111 if_re not working in current r295091 Content-Type: text/plain; charset=UTF-8 Date: Fri, 5 Feb 2016 22:56:45 +0100 Importance: normal Sensitivity: Normal In-Reply-To: <20160205212912.GI15359@alchemy.franken.de> References: <20160204005132.GA1181@michelle.fasterthan.co.kr> , <20160205212912.GI15359@alchemy.franken.de> X-UI-Message-Type: mail X-Priority: 3 X-Provags-ID: V03:K0:HxTfNewaOMP8onznyRMes8d6fqw1+BVaULHx7TNtlbY uZ4Wb8ZoFqqVMxGD57rwTqbDSavSPR/yBEgDy/4W8BueTbOyYd tGVFLILj1gBwiCO7Lrkio7rGY8egwhXiNusmwmabSaSfwjEJOH itE4W1x09EachJ3FXYGgNb12n/G7UsGIrBYdDRLM/SSZUE5w4C amjLO763fN7F37EnIAlQOQoNlxog91hKMxzGCvOjqskwQ0644Q X/tV8UR2voMb5K2EckBiB9/xmC+64mDv3fzEKGky2oelF91idp Lb9rzY= X-UI-Out-Filterresults: notjunk:1;V01:K0:PO7FsSEIwJ4=:Hy+68rLmfYkb+xIjdMf8GV 49Uqj7Gxdk7PfkSeZ3SMEtLmn+RDEPiVahRkRcTesmKYqquaC4Nd5MOtZteDyjNJVoBMokd4l ppbZDM+8nNrPnd5hofjI44RoY7Ilksh2nsxswz0+azXBHn7E99gOLZ8sr+5GD3hBYHACzvsSA ug3/nCphTHLHDFBYvm8OWbdJ1sOQS8Y22rceSgGAwkVLtb27RX+JG//O6MgjulrQoOlE0/fah QsMXk0wOmnslETCeKE5whsq+gytwYprJdewy3LYMq8kNIkeu+ygw6GAhOMBtDyAVEeY7Tq1us U3oy7xVLk90OOze9Zth3xU2lN4nGVYjRd17IF3KgDb1WyG/o9uPJMtr1C+KPlporo395uLoOR OxGmwx+yhzQhiKNjxLtP/idsPjRjuoFyONmIK5FRt7kx5ZMoC9xWTJax3wJEOySyZ6fa8OwH4 C5DhzSPKpw== X-Mailman-Approved-At: Fri, 05 Feb 2016 22:12:10 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Feb 2016 22:02:14 -0000 Hi, this is the line from verbose boot: re0: port 0xe000-0xe0ff mem re0: Chip rev. 0x2c800000 re0: MAC rev. 0x00100000 rgephy0: 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 > >