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]

Date:	Sat, 30 Aug 2008 21:16:58 +0100 (BST)
From:	"Maciej W. Rozycki" <macro@...ux-mips.org>
To:	Frans Pop <elendil@...net.nl>
cc:	"Rafael J. Wysocki" <rjw@...k.pl>, 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 Sat, 30 Aug 2008, Frans Pop wrote:

> >  Barring a hardware erratum, this is a bug in the kernel.  It should be
> > moderately easy to track down with some debugging added to writes
> > accessing LVT and redirection table entries.
> 
> Could you please provide some more specific debugging instructions? I'm at 
> a complete loss what I should do here.

 Debugging code can be added to apic_write() and io_apic_{write,modify}()  
so that a warning is output into the kernel log whenever a suspicious
value is written to one of the vector registers.  Similarly for MSI/HT
interrupts, although I do not know names of the functions involved off the
head.  Due to performance considerations it is unfortunately infeasible to
have such debugging enabled in production kernels.

  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/