From owner-freebsd-net@FreeBSD.ORG Wed Oct 29 17:01:30 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 620C5330 for ; Wed, 29 Oct 2014 17:01:30 +0000 (UTC) Received: from phlegethon.blisses.org (phlegethon.blisses.org [50.56.97.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 414056EA for ; Wed, 29 Oct 2014 17:01:29 +0000 (UTC) Received: from blisses.org (cocytus.blisses.org [23.25.209.73]) by phlegethon.blisses.org (Postfix) with ESMTPSA id 7FC061F13CF; Wed, 29 Oct 2014 13:01:28 -0400 (EDT) Date: Wed, 29 Oct 2014 13:01:26 -0400 From: Mason Loring Bliss To: Yonghyeon PYUN Subject: Re: Very bad Realtek problems Message-ID: <20141029170126.GG17150@blisses.org> References: <20141027195124.GI17150@blisses.org> <20141028015020.GB1054@michelle.fasterthan.com> <20141028034445.GR17150@blisses.org> <20141029014630.GA2503@michelle.fasterthan.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20141029014630.GA2503@michelle.fasterthan.com> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-net@freebsd.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Oct 2014 17:01:30 -0000 On Wed, Oct 29, 2014 at 10:46:30AM +0900, Yonghyeon PYUN wrote: > Given that you can reliably reproduce the issue, let's check simple ones > first. Just as a quick update, I couldn't tolerate the network outages any more as they were impacting my work, so I bought an Intel NIC. That said, this will actually free me up to do more debugging of the Realtek as soon as I get a chance to finish setting up a small test network - I'll be able to look at both sides of interactions instead of depending on the flaky interface. > If you think the issue intermittently happens regardless of network load, > try attached patch. I'm not sure whether the patch makes any difference for > you since many PCIe NICs don't implement CLKREQ feature. It's just a wild > guess. This is an onboard NIC, for what it's worth, on my: Base Board Information Manufacturer: ASUSTeK Computer INC. Product Name: M4A88T-M Version: Rev X.0x I'm not sure if that changes it as compared with a plug-in PCIe device. Just mentioning it for completeness. -- Mason Loring Bliss mason@blisses.org Ewige Blumenkraft! (if awake 'sleep (aref #(sleep dream) (random 2))) -- Hamlet, Act III, Scene I