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: <200808220202.52853.elendil@planet.nl>
Date:	Fri, 22 Aug 2008 02:02:52 +0200
From:	Frans Pop <elendil@...net.nl>
To:	linux-kernel@...r.kernel.org
Cc:	Matthew Garrett <mjg59@...f.ucam.org>
Subject: Re: 2.6.27-rc3: 'APIC error on CPU1: 00(40)', but only on resume!

On Thursday 21 August 2008, Matthew Garrett wrote:
> 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.

That makes sense.

> Some older kernels 
> would give the impression that they could, but the package itself will
> run at the greater of the defined frequencies.

It does not seem to be kernel related, but processor related.
Here are some results from two different systems (desktop and laptop) 
running an _identical_ 2.6.27-rc4 x86_64 kernel.
(The desktop is actually Pentium D, not also Core Duo.)

Desktop
=======
processor       : 1
vendor_id       : GenuineIntel
cpu family      : 15
model           : 4
model name      :               Intel(R) Pentium(R) D CPU 3.20GHz
stepping        : 7
cpu MHz         : 2800.000
cache size      : 1024 KB
physical id     : 0
siblings        : 2
core id         : 1
cpu cores       : 2

Samples from /sys/devices/system/cpu/cpu*/cpufreq/scaling_cur_freq:
2800000 2800000
2800000 2800000
2800000 3200000		# Start single busy loop, one core idle
3200000 3200000
2800000 3200000
2800000 3200000

Laptop
======
processor       : 1
vendor_id       : GenuineIntel
cpu family      : 6
model           : 15
model name      : Intel(R) Core(TM)2 Duo CPU     U7700  @ 1.33GHz
stepping        : 13
cpu MHz         : 1333.000
cache size      : 2048 KB
physical id     : 0
siblings        : 2
core id         : 1
cpu cores       : 2

Samples from /sys/devices/system/cpu/cpu*/cpufreq/scaling_cur_freq:
800000 800000
800000 800000
1333000 1333000		# Start single busy loop, one core idle
1333000 1333000
1333000 1333000

So in the first case frequency changes are reported as if the cores are 
independent while in the second case the cores appear linked.

Is a Pentium D really different from a Core Duo in that respect?
--
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/