From owner-freebsd-stable@FreeBSD.ORG Tue Apr 19 20:40:23 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 69FA816A4CE for ; Tue, 19 Apr 2005 20:40:23 +0000 (GMT) Received: from pop-a065d14.pas.sa.earthlink.net (pop-a065d14.pas.sa.earthlink.net [207.217.121.252]) by mx1.FreeBSD.org (Postfix) with ESMTP id 49D2F43D3F for ; Tue, 19 Apr 2005 20:40:23 +0000 (GMT) (envelope-from mvh@ix.netcom.com) Received: from lsanca1-ar6-4-62-201-077.lsanca1.elnk.dsl.genuity.net ([4.62.201.77] helo=bsd.mvh) by pop-a065d14.pas.sa.earthlink.net with esmtp (Exim 3.36 #10) id 1DNzWA-0005uQ-00; Tue, 19 Apr 2005 13:40:22 -0700 Received: from localhost (localhost.mvh [127.0.0.1]) by bsd.mvh (Postfix) with ESMTP id 5D5A81714A; Tue, 19 Apr 2005 13:40:22 -0700 (PDT) Received: from bsd.mvh ([127.0.0.1]) by localhost (bsd.mvh [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 10246-06; Tue, 19 Apr 2005 13:40:18 -0700 (PDT) Received: by bsd.mvh (Postfix, from userid 1001) id 45F3317171; Tue, 19 Apr 2005 13:40:18 -0700 (PDT) From: mvh@ix.netcom.com To: kris@obsecurity.org (Kris Kennaway), stable@freebsd.org In-Reply-To: X-Newsgroups: mailing.freebsd.stable User-Agent: tin/1.7.7-20041215 ("Scalpay") (UNIX) (FreeBSD/5.4-RC2 (i386)) Message-Id: <20050419204018.45F3317171@bsd.mvh> Date: Tue, 19 Apr 2005 13:40:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at bsd.mvh Subject: Re: %idle stuck at 33%? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2005 20:40:23 -0000 In article you wrote: > > This kind of thing can happen if your world is out of sync with your > kernel. > > Kris > The world and kernel are in sync - I used a world/kernel build to generate the load (several times with the same source). I don't see the same behavior on a Dell desktop machine with 2 processors, hyperthreading disabled, so it must be something specific to the Dell 2650. - Mike H.