All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Frans Pop <elendil@planet.nl>
Cc: linux-kernel@vger.kernel.org, Andi Kleen <andi@firstfloor.org>,
	Ingo Molnar <mingo@elte.hu>
Subject: Re: 2.6.27-rc3: 'APIC error on CPU1: 00(40)', but only on resume!
Date: Wed, 20 Aug 2008 23:56:32 +0200	[thread overview]
Message-ID: <200808202356.33036.rjw@sisk.pl> (raw)
In-Reply-To: <200808202226.45655.elendil@planet.nl>

On Wednesday, 20 of August 2008, Frans Pop wrote:
> 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.

On my box I see many "APIC error on CPU1: 00(40)" messages that don't seem
to be related to anything obviously bad and I've alwas been seeing them.

Please monitor things for some time to check if you can find a connection
between those messages and any erroneous behavior.

Thanks,
Rafael

  reply	other threads:[~2008-08-20 21:53 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 [this message]
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=200808202356.33036.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=andi@firstfloor.org \
    --cc=elendil@planet.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.