From owner-freebsd-sparc64@FreeBSD.ORG Fri Aug 15 07:00:58 2003 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 61B1B37B401; Fri, 15 Aug 2003 07:00:58 -0700 (PDT) Received: from mail.seekingfire.com (coyote.seekingfire.com [24.72.10.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8B4DF43FDF; Fri, 15 Aug 2003 07:00:57 -0700 (PDT) (envelope-from tillman@seekingfire.com) Received: from blues.seekingfire.prv (blues.seekingfire.prv [192.168.23.211]) by mail.seekingfire.com (Postfix) with ESMTP id B54902A8; Fri, 15 Aug 2003 08:00:56 -0600 (CST) Received: (from tillman@localhost) by blues.seekingfire.prv (8.11.6/8.11.6) id h7FE0ui12358; Fri, 15 Aug 2003 08:00:56 -0600 Date: Fri, 15 Aug 2003 08:00:56 -0600 From: Tillman To: sparc64@freebsd.org Message-ID: <20030815080055.O22214@seekingfire.com> References: <20030815121010.I97608@beagle.fokus.fraunhofer.de> <20030815135034.GA701@crow.dom2ip.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20030815135034.GA701@crow.dom2ip.de>; from t.moestl@tu-bs.de on Fri, Aug 15, 2003 at 03:50:35PM +0200 X-Urban-Legend: There is lots of hidden information in headers cc: jmg@freebsd.org Subject: Re: Sparc slowdown - problem identified... X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Aug 2003 14:00:58 -0000 On Fri, Aug 15, 2003 at 03:50:35PM +0200, Thomas Moestl wrote: > On Fri, 2003/08/15 at 12:20:39 +0200, Harti Brandt wrote: > > > > Hi all, > > > > it seems I have identified which commit causes the slow down on some > > sparcs. The kernel from just before that commit works just fine, the > > kernel from just after it is 3x slower on my Ultra-10 (as was also > > reported by others). I have no idea why that happens. The only difference > > in the time -l report is user and system time going up by a factor of > > three and the involuntary context switches doubling. > > It seems that deferred errors (and thus the data access errors > generated due to PCI bus timeouts from non-existant devices) will > disable the instruction and data cache by resetting the corresponding > enable bits in the LSU control register, and the current code fails to > reenable them (which also requires a cache flush). A simple workaround > for now is to avoid triggering these errors, so enabling OFW_NEWPCI > should help. Is OFW_NEWPCI where -CURRENT on Sparc is heading? I.e., if I enable it now and go through any needed reconfiguration will I be saving myself time in the future? The notes for OFW_NEWPCI say: # New OpenFirmware PCI framework. This fixes a number of interrupt- # routing problems and changes the device enumeration to be hopefully # closer to Solaris. Be aware that, because of the latter, enabling or # disabling this option may require reconfiguration, and can even # cause the machine to not boot without manual intervention before the # fstab is adjusted. What sort of changes are likely to occur that would affect fstab? The box is remote, so I can fix most things via a serial console as long as it'll boot :-) Thanks! -T -- The supreme irony of life is that hardly anyone gets out alive. - Robert Heinlein