From: Frans Pop <elendil@planet.nl>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.27-rc3: 'APIC error on CPU1: 00(40)', but only on resume!
Date: Wed, 20 Aug 2008 22:26:45 +0200 [thread overview]
Message-ID: <200808202226.45655.elendil@planet.nl> (raw)
In-Reply-To: <200808202138.13302.rjw@sisk.pl>
Thanks for the quick responses Rafael.
On Wednesday 20 August 2008, Rafael wrote:
> On Wednesday, 20 of August 2008, Frans Pop wrote:
> > <snip>
> > CPU1 is up
> > ACPI: Waking up from system sleep state S3
> > APIC error on CPU1: 00(40)
> > ACPI: EC: non-query interrupt received, switching to interrupt mode
> > </snip>
>
> Does the box work after that?
Yes, it does. Both cores seem to be working fine.
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.
This also happens immediately after boot (so not suspend related) and may
be "normal" or unrelated.
next prev parent reply other threads:[~2008-08-20 20:27 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 [this message]
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
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=200808202226.45655.elendil@planet.nl \
--to=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