From owner-freebsd-current@freebsd.org Sat Feb 13 23:14:46 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 23E28AA8724 for ; Sat, 13 Feb 2016 23:14:46 +0000 (UTC) (envelope-from freebsd@go4more.de) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.187]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8DA021442 for ; Sat, 13 Feb 2016 23:14:44 +0000 (UTC) (envelope-from freebsd@go4more.de) Received: from [80.132.215.157] by 3capp-1and1-bs02.server.lan (via HTTP); Sun, 14 Feb 2016 00:09:09 +0100 MIME-Version: 1.0 Message-ID: From: "Stefan Kohl" To: "Marius Strobl" Cc: freebsd-current@freebsd.org Subject: Aw: Re: Re: Re: Realtek 8168/8111 if_re not working in current r295091 Content-Type: text/plain; charset=UTF-8 Date: Sun, 14 Feb 2016 00:09:09 +0100 Importance: normal Sensitivity: Normal In-Reply-To: <20160213212720.GH15359@alchemy.franken.de> References: <20160204005132.GA1181@michelle.fasterthan.co.kr> <20160205212912.GI15359@alchemy.franken.de> , <20160213212720.GH15359@alchemy.franken.de> X-UI-Message-Type: mail X-Priority: 3 X-Provags-ID: V03:K0:xmTlNorDyeQ/TnpXfSuPRJQEqAJ/ymWibGb/Q6esf9C kIv+lO6maEIGtm/Ji5P0dFeE19/hjXK0JFvbugJT7Y6+M+1yV3 B6sIAuEKJUreJbRGeYGSoCthmysWSNTvCUK9DB6qp2nJNoQDk+ U5oUrZetJhDmX+eFEcMCnOx+eQN/rZCl+sy0O3EnFYhBI0PEfv M/WB+T3BjwZK4Goqk78hKxwzlGX0n94OvrDNP3kkYN+jDHGi/Z B+6rdXRnkvtLN3TIBtGkQHo/gMiPe7lXlUTwQUHsDq0Peg+A7L mvFNcc= X-UI-Out-Filterresults: notjunk:1;V01:K0:a/ne70YjZks=:jzhmh+RVrdW/271X+UXB8N YLbu377/roYmXWPyaa46OSNt7vDFkqdm0fHtWrKS6yCvMRMG61QpupGe+WuE2ySD1dCS39a/h RVjni9UFbpT12MfG6mZu2NOkH/EdS+3T5HGBlqsWE1kF0n+UmFwOCQV0fEq9GY2mBPZozIsRf ghffqIJPGADxczhm/Qs72dJa6OAkeupGCjOIc+puTrx+nNe0KwQMCwyt7aqQbEF+Z2dxdFfEF jJHNZw/Qr4b7Z1L6qeLPYoR8BPP3AOmIG0iKwbWu8I78DZK5fNwLjJl2OqFyd76wXpyu7niFJ Oyr1Wz 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: Sat, 13 Feb 2016 23:14:46 -0000 Hi Marius, thanks for your time and thoughts in this matter! Unfortunately the chip seems to be seriously broken; I applied the suggested patch re.8168evl.diff from yongari to no avail, I am still getting the same connection error. For the time being I can live with my "phoney" workaround as long as I do not encounter any adverse side-effects, but I hope that it can be properly fixed. Regards, Stefan > Gesendet: Samstag, 13. Februar 2016 um 22:27 Uhr > Von: "Marius Strobl" > An: "Stefan Kohl" > Cc: pyunyh@gmail.com, freebsd-current@freebsd.org > Betreff: Re: Re: Re: Realtek 8168/8111 if_re not working in current r295091 > On Sat, Feb 13, 2016 at 09:21:06PM +0100, Stefan Kohl wrote: > > Hi Marius, > > > > I finally got my RT 8168 Ethernet Card (Zotac Ri323) working after > > patching if_re.c (r295601). Contrary to the assumption that > > HWREV_8168E_VL with Chip Rev 0x2c800000 should not require RTL8168G > > handling as soon as I expand the sc->rl_flags for the respective > > HWREV and define the (ominous) 8168G_Plus Flag for RL_HWREV_8168E_VL > > the card is functioning correctly. > > My best guess currently is that treating HWREV_8168E_VL as RTL8168G > or later chip - which it simply isn't - serves as workaround by e. g. > resetting parts of the RX/TX MAC configuration, that doesn't make it > an appropriate fix, though. I have a WIP which does a more complete > initialization of Realtek Ethernet MACs, part of which is a workaround > for broken BIOSes and is specific to HWREV_8168E_VL. I suspect that's > the more likely cause for your problem and would also explain why there > was no other such report so far. Currently, 10.3-RELEASE and its show- > stoppers have higher priority for me, though. > > > When broken (without the patch) I got the following tcpdump output: > > > > 19:18:46.299360 00:00:00:00:00:00 (oui Ethernet) > 00:00:00:00:00:00 > > (oui Ethernet) Null Information, send seq 0, rcv seq 0, Flags [Command], > > length 84 > > Actually, this pretty much confirms the assumption that your problem > is caused by a broken BIOS as the correct workaround for that bug > consists of making the GMAC aware of the MAC address via the driver > in addition to only setting it in the MAC. > Err, wait, IIRC yongari@ had a similar change as far as the broken > BIOS workaround is concerned. You may want to give the following > patch a try instead of treating HWREV_8168E_VL as RTL8168G+ (I don't > know whether that patch applies cleanly to current re(4), though): > https://people.freebsd.org/~yongari/re/re.8168evl.diff > > Marius > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current[https://lists.freebsd.org/mailman/listinfo/freebsd-current] > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"