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 for Android: free password hash cracker in your pocket

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

Date:	Wed, 20 Aug 2008 23:56:32 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Frans Pop <elendil@...net.nl>
Cc:	linux-kernel@...r.kernel.org, Andi Kleen <andi@...stfloor.org>,
	Ingo Molnar <mingo@...e.hu>
Subject: Re: 2.6.27-rc3: 'APIC error on CPU1: 00(40)', but only on resume!

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
--
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/