From owner-freebsd-hackers@FreeBSD.ORG  Sun Dec  4 17:50:33 2005
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
X-Original-To: hackers@freebsd.org
Delivered-To: freebsd-hackers@FreeBSD.ORG
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 4BC0A16A422
	for <hackers@freebsd.org>; Sun,  4 Dec 2005 17:50:33 +0000 (GMT)
	(envelope-from gizmen@blurp.t2.ds.pwr.wroc.pl)
Received: from blurp.t2.ds.pwr.wroc.pl (blurp.t2.ds.pwr.wroc.pl [156.17.224.5])
	by mx1.FreeBSD.org (Postfix) with ESMTP id CA58643D91
	for <hackers@freebsd.org>; Sun,  4 Dec 2005 17:50:19 +0000 (GMT)
	(envelope-from gizmen@blurp.t2.ds.pwr.wroc.pl)
Received: by blurp.t2.ds.pwr.wroc.pl (Postfix, from userid 1001)
	id 4D4BB723; Sun,  4 Dec 2005 18:50:13 +0100 (CET)
Date: Sun, 4 Dec 2005 18:50:13 +0100
From: GiZmen <gizmen@zion.vsip.pl>
To: hackers@freebsd.org
Message-ID: <20051204175013.GA53785@blurp.pl>
References: <20051204142744.GA53154@blurp.pl> <43932040.8040207@fer.hr>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <43932040.8040207@fer.hr>
User-Agent: Mutt/1.5.11
Cc: 
Subject: Re: clock interrupts eating whole cpu
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Dec 2005 17:50:33 -0000

> >yesterday i have noticed that my cpu is runnig on 100%.
> >And almost 100% is used on interrupts
> 
> >
> >  PID USERNAME  THR PRI NICE   SIZE    RES STATE    TIME   WCPU COMMAND
> >   27 root        1 -32 -151     0K     8K RUN     62:48 67.72% swi4: clock
> 
> Verify you don't have a console screen-saver configured, especially a 
> graphical one - it happened to me several times.

No i don't have screen saver on my box.