From owner-freebsd-sparc64@FreeBSD.ORG Wed Nov 13 20:40:40 2013 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2FAD098E for ; Wed, 13 Nov 2013 20:40:40 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A3E152DD8 for ; Wed, 13 Nov 2013 20:40:39 +0000 (UTC) Received: from lemon ([80.7.17.14]) by mail.gmx.com (mrgmx003) with ESMTPSA (Nemesis) id 0MFuC6-1VuQjh3DXS-00Ez2G for ; Wed, 13 Nov 2013 21:40:31 +0100 Received: by lemon (Postfix, from userid 1001) id 01BDAEB27E; Wed, 13 Nov 2013 20:40:30 +0000 (GMT) Date: Wed, 13 Nov 2013 20:40:30 +0000 From: symbolics@gmx.com To: freebsd-sparc64@freebsd.org Subject: High system time, 10-BETA3 on a Netra T1 Message-ID: <20131113204030.GA76860@lemon> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Provags-ID: V03:K0:fYH4wePutFhvpRgjmnr28qt8Sore7dcQpcG17cCMtoEcxiKiOSI wFn4xNPjFu4dmcTZPh1pnLdzcPu1uS/xrNym1iG1Co0DsEAXa46VzMv977iEN/qL2tANcD5 1sJW14qtoSPbNxmbfZwzzJER+XEcbGi8TK5ig03KcgHNTPI7GlzAmK0UmfA+Jih4IIe4dWu cf5dsbrj5yt1A8G8MjbLg== X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Nov 2013 20:40:40 -0000 List, I've recently obtained a Netra T1 AC200 and installed FreeBSD 10-BETA3. I know this system is old and won't be quick, however, something looks odd. I'm running portsnap extract. top is reporting that ~65% of the time is being spent in the kernel, with about 25% left for user, about ~10 for idle and the rest on interrupts. The disc itself is running at about 20% busy according to gstat. Looking at 'top -S -m io' I see that bufdaemon is running at ~98%. Is this something I should look into further or just accept? --sym