public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Frans Pop <elendil@planet.nl>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.27-rc3: 'APIC error on CPU1: 00(40)', but only on resume!
Date: Thu, 21 Aug 2008 12:31:41 +0100	[thread overview]
Message-ID: <20080821113141.GB3796@srcf.ucam.org> (raw)
In-Reply-To: <200808202226.45655.elendil@planet.nl>

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@srcf.ucam.org

  parent reply	other threads:[~2008-08-21 11:31 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-20 19:06 2.6.27-rc3: 'APIC error on CPU1: 00(40)', but only on resume! Frans Pop
2008-08-20 19:38 ` Rafael J. Wysocki
2008-08-20 20:26   ` Frans Pop
2008-08-20 21:56     ` Rafael J. Wysocki
2008-08-21  9:27       ` Maciej W. Rozycki
2008-08-21 11:18         ` Vegard Nossum
2008-08-21 11:51           ` Maciej W. Rozycki
2008-08-21 12:01             ` Maciej W. Rozycki
2008-08-21 12:20             ` Vegard Nossum
2008-08-21 12:57               ` Maciej W. Rozycki
2008-08-21 13:14                 ` Vegard Nossum
2008-08-21 13:15                 ` Mikael Pettersson
2008-08-30 19:33               ` Yinghai Lu
2008-08-30 19:16         ` Frans Pop
2008-08-30 20:16           ` Maciej W. Rozycki
2008-09-04 20:18             ` Frans Pop
2008-08-21 11:30       ` Matthew Garrett
2008-08-21 11:31     ` Matthew Garrett [this message]
2008-08-22  0:02       ` Frans Pop

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080821113141.GB3796@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=elendil@planet.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox