public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frans Pop <elendil@planet.nl>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
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!
Date: Thu, 4 Sep 2008 22:18:55 +0200	[thread overview]
Message-ID: <200809042218.56310.elendil@planet.nl> (raw)
In-Reply-To: <Pine.LNX.4.55.0808302106140.29414@cliff.in.clinika.pl>

On Saturday 30 August 2008, Maciej W. Rozycki wrote:
> 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.

Thanks for the reply Maciej, but that is still way over my head I'm 
afraid. I think I'll need an actual debug patch from someone that I can 
apply and test with to get any further with this.

  reply	other threads:[~2008-09-04 20:19 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
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 [this message]
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=200809042218.56310.elendil@planet.nl \
    --to=elendil@planet.nl \
    --cc=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macro@linux-mips.org \
    --cc=mingo@elte.hu \
    --cc=rjw@sisk.pl \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox