From owner-freebsd-stable@FreeBSD.ORG Wed Sep 27 21:32:04 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0266416A5E2 for ; Wed, 27 Sep 2006 21:32:03 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id E7B6743E42 for ; Wed, 27 Sep 2006 21:31:08 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [10.10.3.185] ([165.236.175.187]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k8RLTbqu020899; Wed, 27 Sep 2006 15:29:43 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <451AED3B.2090707@samsco.org> Date: Wed, 27 Sep 2006 15:29:31 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060206 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Volker References: <451A1375.5080202@gneto.com> <20060927071538.GF22229@e-Gitt.NET> <451A4189.5020906@samsco.org> <20060927094509.GB75104@hugo10.ka.punkt.de> <451AE762.9080403@vwsoft.com> In-Reply-To: <451AE762.9080403@vwsoft.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.0 required=3.8 tests=none autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on pooker.samsco.org Cc: freebsd-stable@freebsd.org, Oliver Brandmueller Subject: Re: 6.2 SHOWSTOPPER - em completely unusable on 6.2 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Sep 2006 21:32:04 -0000 Volker wrote: > On 37378-12-23 20:59, Patrick M. Hausen wrote: > >>Hello! >> >> >>>Well, the best I can say at the moment is, "Wow." =-( I guess the >>>thing to do here is to figure out if the problem lies with the em >>>interrupt handler not getting run, or the taskqueue not getting run. >> >>I helped Pyun with some debugging by providing ssh access to >>a machine showing the (seemingly) same problem. >> >>At first he thought the interrupt handler of the em driver was >>the culprit, but we applied quite a few patches and tested >>afterwards - seems like the driver is not the cause. >> >>On -stable occasionally other people complained about very similar >>looking problems with bge and other drivers. My guess is, though >>I'm not a kernel developer, just an experienced admin, that >>em stands out as problematic just by coincidence. Certain onboard >>network components tend to come with certaiin chipsets and certain >>architectures. >> >>So, Pyun suggested it was a problem with the taskqueue that was >>introduced some time between 6.0 and 6.1. >> >>With my system (Tyan GT20 B5161G20) the problem shows when there >>is heavy disk and cpu activity, like "make buildworld". >>I made sure that the em interface doesn't share an interrupt >>with the SATA controller. When the problem occurs, I get the >>well known "watchdog timeout" messages and then the system's >>network activity over that interface freezes completely for >>a couple of minutes. >>Usually the system recovers after a while without reboot or >>other measures. >> > > > Strange... I've seen exactly that on a (recent) RELENG_6 box but > using a dirty old USB 1.1 NIC (aue). I've seen DOWN and UP messages > (mostly while rebuilding kernel + world + ports) on the console all > the time (but did not care about). > > The machine in question is an Athlon XP-64 Socket 939, Asus A8N-VM > CSM. The USB ethernet NIC is a low budget ADMtek device. My > observations are probably not related to your issues but maybe a > sign of not really being a driver issue or not GigE related. > > Greeting, > > Volker As soon as I can locate the O/U/EHCI register docs, I'll crank out a patch for everyone to try. If that works then I'll give the same treatment to ichsmb. Scott