Date: Sat, 30 Aug 2008 21:16:58 +0100 (BST)
From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Frans Pop <elendil@planet.nl>
cc: "Rafael J. Wysocki" <rjw@sisk.pl>, 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!
In-Reply-To: <200808302116.07421.elendil@planet.nl>
Message-ID: <Pine.LNX.4.55.0808302106140.29414@cliff.in.clinika.pl>
References: <200808202106.41058.elendil@planet.nl> <200808202356.33036.rjw@sisk.pl>
 <Pine.LNX.4.55.0808211023020.22938@cliff.in.clinika.pl>
 <200808302116.07421.elendil@planet.nl>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1030
Lines: 22

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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/