From owner-freebsd-arm@FreeBSD.ORG Fri Sep 5 22:08:24 2014 Return-Path: Delivered-To: freebsd-arm@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 A995EA98 for ; Fri, 5 Sep 2014 22:08:24 +0000 (UTC) Received: from bein.link (vps-6159-8629.cloud.tilaa.com [37.252.124.82]) by mx1.freebsd.org (Postfix) with ESMTP id 6F37014F7 for ; Fri, 5 Sep 2014 22:08:24 +0000 (UTC) Received: from quad.localnet (unknown [188.134.8.193]) by bein.link (Postfix) with ESMTPSA id 457FF4051F; Sat, 6 Sep 2014 00:08:22 +0200 (CEST) From: Maxim V FIlimonov To: ticso@cicely.de Subject: Re: Cubieboard: load average above 2 Date: Sat, 06 Sep 2014 02:08:22 +0400 Message-ID: <6240427.cmkfEefv07@quad> User-Agent: KMail/4.12.5 (FreeBSD/10.0-RELEASE-p7; KDE/4.12.5; amd64; ; ) In-Reply-To: <20140905215555.GK3196@cicely7.cicely.de> References: <27116175.UDSoyStjsX@quad> <20140905215555.GK3196@cicely7.cicely.de> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Cc: freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Sep 2014 22:08:24 -0000 On Friday 05 September 2014 23:55:55 Bernd Walter wrote: > On Sat, Sep 06, 2014 at 01:41:40AM +0400, Maxim V FIlimonov wrote: > > Recently, I installed FreeBSD-current to my Cubieboard2: > > root@cubie:~ # uname -a > > FreeBSD cubie 11.0-CURRENT FreeBSD 11.0-CURRENT #2 r271182M: Sat Sep 6 > > 01:17:28 MSK 2014 root@quad:/usr/obj/arm.armv6/home/che/freebsd- > > src/head/sys/CUBIEBOARD2 arm > > > > And the system's load average keeps being above 2: > > root@cubie:~ # uptime > > > > 8:31PM up 19 mins, 1 user, load averages: 2.36, 1.89, 1.32 > > > > Everything is not really slow, but sometimes takes time. > > What could be the problem here? What can I do with that? > > top -SH is the first thing I do to find what's consuming CPU. > Note that an idle thread consuming CPU means it's really idling. I took away I2C support from the kernel config, and now LA is about 1.3 which is also a bit too much, but not that big, AFAIK. Could i2c be the problem here? -- wbr, Maxim Filimonov che@bein.link