From owner-freebsd-questions@FreeBSD.ORG  Wed Jan  7 07:12:33 2004
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 77FA816A4CE
	for <questions@freebsd.org>; Wed,  7 Jan 2004 07:12:33 -0800 (PST)
Received: from sccrmhc13.comcast.net (sccrmhc13.comcast.net [204.127.202.64])
	by mx1.FreeBSD.org (Postfix) with ESMTP id B7CE043D5C
	for <questions@freebsd.org>; Wed,  7 Jan 2004 07:12:28 -0800 (PST)
	(envelope-from freebsd-questions-local@be-well.ilk.org)
Received: from be-well.no-ip.com ([66.30.200.37])
          by comcast.net (sccrmhc13) with ESMTP
          id <2004010715122801600qkqlke>; Wed, 7 Jan 2004 15:12:28 +0000
Received: by be-well.no-ip.com (Postfix, from userid 1147)
	id 276113A; Wed,  7 Jan 2004 10:12:28 -0500 (EST)
Sender: lowell@be-well.ilk.org
To: mattv@iinet.net.au
References: <20040106075951.4910.qmail@www-01.iinet.net.au>
From: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org>
Date: 07 Jan 2004 10:12:27 -0500
In-Reply-To: <20040106075951.4910.qmail@www-01.iinet.net.au>
Message-ID: <44hdz7rdwk.fsf@be-well.ilk.org>
Lines: 22
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
cc: questions@freebsd.org
Subject: Re: Run away CPU FreeBSD 4.9 Release #0
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: questions@freebsd.org
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Jan 2004 15:12:33 -0000

"Matt Villion" <mattv@iinet.net.au> writes:

> I have just installed 4.9 R0 on to new hardware and have encountered an
> unusual issue.
> It was not detected straight away as everything appeared to do what it was
> supposed to do...
> 
> Some processes run away with the CPU.  Screen is one of the worst offenders
> along with python..
> The CPU starts out at about 15% and slowly ramps up to 100%.
> As the % ramps up, the priority increases up to about 60
> If more than one screen is launched, then the will share the CPU but the
> priority still sits about 60.
> 
> Any ideas what this could be and how to fix.

What's the actual problem?  Are important programs failing to get cycles?

-- 
Lowell Gilbert, embedded/networking software engineer, Boston area: 
		resume/CV at http://be-well.ilk.org:8088/~lowell/resume/
		username/password "public"