public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Andrew Morton <akpm@osdl.org>
Cc: Brandon Philips <brandon@ifup.org>,
	linux-kernel@vger.kernel.org, Brice Goglin <brice@myri.com>,
	Greg Kroah-Hartman <gregkh@suse.de>,
	Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
	Robert Love <rml@novell.com>
Subject: Re: 2.6.18-rc6-mm1 2.6.18-rc5-mm1 Kernel Panic on X60s
Date: Mon, 11 Sep 2006 11:55:32 -0600	[thread overview]
Message-ID: <m1ac569tkb.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20060911095106.2a7d6d95.akpm@osdl.org> (Andrew Morton's message of "Mon, 11 Sep 2006 09:51:06 -0700")

Andrew Morton <akpm@osdl.org> writes:

> OK, thanks.
>
> I don't think this necessarily tells us where the bug lies.  It could be
> some pre-existing thing in MSI, or it could be added by Bryce's changes. 
> Or by Eric's.  Or, of course, by
> genirq-convert-the-i386-architecture-to-irq-chips.patch.
>
> There doesn't seem to be a lot of movement on this and we want to get the
> x86 genirq conversion into 2.6.19.  Could be that we end up having to merge
> known-buggy stuff into mainline and crash enough computers to irritate
> someone into fixing it.  Rather sad.

My planning to take a good hard look at it, in a bit.
Since it was failing in do_IRQ with a page fault something is obviously being
left as NULL, so this should be quite easy to track down once we look
closely.

I'm very suspicious that this failure started happening in just
the last two -mm releases.  That seems to implicate Bryce's work,
but if it is just about enabling MSI he should not have touched
the code path where the failure happened.

Also I noticed a little while ago that I didn't quite take the
msi code far enough.  In particular the generic code still does some
apic accesses which doesn't make any sense at all for architectures
like ppc.

I'm currently sitting on a queue of 30 about 99% complete struct pid
conversions, that I just need to review one last time and then send
out to get merged, hopefully I can get the rest of these patches sent
out in the next day or two, so I can focus on irq issues for a bit.

Eric

  reply	other threads:[~2006-09-11 17:56 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-08 17:44 2.6.18-rc6-mm1 2.6.18-rc5-mm1 Kernel Panic on X60s Brandon Philips
2006-09-08 19:13 ` Andrew Morton
2006-09-08 19:43   ` Brandon Philips
2006-09-08 19:50     ` Andrew Morton
2006-09-09  2:22       ` Benoit Boissinot
2006-09-09  3:27       ` Eric W. Biederman
2006-09-09  5:21         ` Andrew Morton
2006-09-09  5:47           ` Brice Goglin
2006-09-09  6:01             ` Brandon Philips
2006-09-09  6:14               ` Brice Goglin
2006-09-11  2:14       ` Brandon Philips
2006-09-11 16:51         ` Andrew Morton
2006-09-11 17:55           ` Eric W. Biederman [this message]
2006-09-12  6:20           ` Eric W. Biederman
2006-09-12  7:50             ` [patch] genirq/MSI: restore __do_IRQ() compat logic temporarily Ingo Molnar
2006-09-12 12:44               ` Brandon Philips
2006-09-12 14:37               ` Eric W. Biederman

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=m1ac569tkb.fsf@ebiederm.dsl.xmission.com \
    --to=ebiederm@xmission.com \
    --cc=akpm@osdl.org \
    --cc=brandon@ifup.org \
    --cc=brice@myri.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rml@novell.com \
    --cc=tglx@linutronix.de \
    /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