From owner-freebsd-current@FreeBSD.ORG Wed Nov 23 09:07:10 2005 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1547316A41F; Wed, 23 Nov 2005 09:07:10 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id C4FD043D5C; Wed, 23 Nov 2005 09:07:09 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id A24871A3C2A; Wed, 23 Nov 2005 01:07:09 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 89981528C8; Wed, 23 Nov 2005 04:07:07 -0500 (EST) Date: Wed, 23 Nov 2005 04:07:07 -0500 From: Kris Kennaway To: Kris Kennaway Message-ID: <20051123090706.GA91223@xor.obsecurity.org> References: <20051123090334.GA90972@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="cWoXeonUoKmBZSoM" Content-Disposition: inline In-Reply-To: <20051123090334.GA90972@xor.obsecurity.org> User-Agent: Mutt/1.4.2.1i Cc: cperciva@FreeBSD.org, current@FreeBSD.org, jhb@FreeBSD.org Subject: Re: idle task running on the wrong CPU X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Nov 2005 09:07:10 -0000 --cWoXeonUoKmBZSoM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 23, 2005 at 04:03:34AM -0500, Kris Kennaway wrote: > On 6.0-STABLE: >=20 > PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND > 13 root 1 171 52 0K 8K CPU1 0 0:00 100.00% idle: = cpu1 > =20 > Note: the cpu1 idle task is running on CPU 0. Actually it is not > running, since it's not accumulating any CPU time, and in fact nothing > at all is being scheduled on CPU 1. >=20 > Kris It was pointed out that machdep.hyperthreading_allowed=3D1 fixes this bug (it was set to 0). However, hyperthreading was already in use (partly), because this machine has 2 physical CPUs with HTT, and CPUs 0, 2 and 3 were running jobs. Looks like machdep.hyperthreading_allowed=3D0 does not work as intended. Kris --cWoXeonUoKmBZSoM Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDhDE6Wry0BWjoQKURAonNAJ9QsfYWiBrZlX0TPcvKV1bujvQDpwCeNJOJ 50ujf6MlrbgBncmN5CBcm08= =//dH -----END PGP SIGNATURE----- --cWoXeonUoKmBZSoM--