From owner-freebsd-stable@FreeBSD.ORG Wed Sep 27 15:56:33 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 8CC1C16A4C2 for ; Wed, 27 Sep 2006 15:56:33 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from sccrmhc15.comcast.net (sccrmhc15.comcast.net [63.240.77.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5EED943E32 for ; Wed, 27 Sep 2006 15:55:54 +0000 (GMT) (envelope-from jdc@koitsu.dyndns.org) Received: from icarus.home.lan (c-67-174-220-97.hsd1.ca.comcast.net[67.174.220.97]) by comcast.net (sccrmhc15) with ESMTP id <2006092715555301500ilt9le>; Wed, 27 Sep 2006 15:55:53 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 6E45A1FA037; Wed, 27 Sep 2006 08:55:53 -0700 (PDT) Date: Wed, 27 Sep 2006 08:55:53 -0700 From: Jeremy Chadwick To: freebsd-stable@freebsd.org Message-ID: <20060927155553.GB14563@icarus.home.lan> Mail-Followup-To: freebsd-stable@freebsd.org References: <451A1375.5080202@gneto.com> <20060927071538.GF22229@e-Gitt.NET> <451A4189.5020906@samsco.org> <20060927152824.GJ22229@e-Gitt.NET> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060927152824.GJ22229@e-Gitt.NET> X-PGP-Key: http://jdc.parodius.com/pubkey.asc User-Agent: Mutt/1.5.13 (2006-08-11) 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 15:56:33 -0000 On Wed, Sep 27, 2006 at 05:28:24PM +0200, Oliver Brandmueller wrote: > Disk activity does not trigger the problem, I hammered the disk with > around 85 MB/s (dd) for about half an hour without seeing any effect. A > CPU bound thing like a buildworld triggered the problem. > > The SMBus Interface is not used at all (it's not even really usable). > Anyway, as soon as I unload the ichsmb module I cannot triger the > problem anymore. If I load it again, the problem cann again be triggered > by a buildworld. Statistical relevance: I did 4 buildworlds, alternating > the load/unload of ichsmb - both times with ichsmb loaded I saw 3 > watchdog timeouts during the buildworld was running, while ichsmb was > not loaded I did not see a single watchdog timeout. The use of the > interface was around the same during all the time (constant NFS traffic > of around 1-2 MBit/s). Interesting find. For what it's worth -- I too load the appropriate smbus drivers on the system with the "em0 problem" (loading smbus and ichsmb). That system is a single processor / single core system, with HT disabled in the BIOS (which doesn't matter since FreeBSD disables it anyways). Kernel is non-SMP. Only reason I mention this is: > The UP/SMP idea seems to be only of interest, because on an UP machine > it's more likely to share interrupts than on SMP machines, it has > nothing to do with the fact of UP or SMP itself. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |