linux-kernel - Re: 2.6.27-rc3: 'APIC error on CPU1: 00(40)', but only on resume!

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080821113141.GB3796@srcf.ucam.org>
Date:	Thu, 21 Aug 2008 12:31:41 +0100
From:	Matthew Garrett <mjg59@...f.ucam.org>
To:	Frans Pop <elendil@...net.nl>
Cc:	"Rafael J. Wysocki" <rjw@...k.pl>, linux-kernel@...r.kernel.org
Subject: Re: 2.6.27-rc3: 'APIC error on CPU1: 00(40)', but only on resume!

On Wed, Aug 20, 2008 at 10:26:45PM +0200, Frans Pop wrote:

> The only weirdness I can see (only spotted that just now) is that both 
> cores will always seem to be changing frequency together (using ondemand 
> governor), even when 'top' shows one as idle. On my other Core Duo system 
> (an older desktop) the cores react independently.

The cores can't actually be independently scaled. Some older kernels 
would give the impression that they could, but the package itself will 
run at the greater of the defined frequencies.

-- 
Matthew Garrett | mjg59@...f.ucam.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/