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: <Pine.LNX.4.55.0808211240090.22938@cliff.in.clinika.pl>
Date:	Thu, 21 Aug 2008 12:51:14 +0100 (BST)
From:	"Maciej W. Rozycki" <macro@...ux-mips.org>
To:	Vegard Nossum <vegard.nossum@...il.com>
cc:	"Rafael J. Wysocki" <rjw@...k.pl>, Frans Pop <elendil@...net.nl>,
	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 Thu, 21 Aug 2008, Vegard Nossum wrote:

> I've also seen this a lot, so I have now written (I think) such a
> debug patch (it's very crude) and tested it on my laptop, which
> exhibits this problem.
[...]
> APIC error on CPU0: 00(40)
> Last 16 APIC writes:
[...]
> The order is from oldest (0) to newest (15) write. I don't see any
> writes to ICR in there, which means that IPIs can be ruled out? It
> seems that it is the write to Timer that causes it. In another place,
> we have this:

 You are correct about the ICR -- IPIs are unlikely to be a problem 
because only a couple of predefined vectors are used.  Besides, they are 
normally critical enoug for the system to become unstable if unhandled.

 Otherwise there is no correlation between the sequence of APIC writes and
an error triggering -- a bad vector in a LVT or interrupt redirection
entry will be reported whenever its associated interrupt line gets active
even though the entry might have been initialised long ago.  Depending on
the device signalling hardware interrupts may quite often be ignored for a
long time without affecting the stability of the rest of the system.

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