From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Andrew Morton <akpm@osdl.org>
Cc: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>,
Matthias Hentges <oe@hentges.net>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: 2.6.18-rc5-mm1
Date: Sun, 03 Sep 2006 18:00:32 -0700 [thread overview]
Message-ID: <44FB7AB0.10103@goop.org> (raw)
In-Reply-To: <20060903175048.6fed40ab.akpm@osdl.org>
Andrew Morton wrote:
> Spose so.
>
> But what _did_ cause it? Looks like we took an IRQ and then leapt into
> outer space, when do_IRQ() called desc->handle_irq().
>
It was specifically an MSI interrupt problem; disabling CONFIG_MSI fixed
the problem for me. GregKH said that the MSI patch series in rc5-mm1 is
broken, and had been replaced.
J
--
VGER BF report: H 0
next prev parent reply other threads:[~2006-09-04 1:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-04 0:22 2.6.18-rc5-mm1 Pallipadi, Venkatesh
2006-09-04 0:50 ` 2.6.18-rc5-mm1 Andrew Morton
2006-09-04 1:00 ` Jeremy Fitzhardinge [this message]
2006-09-04 11:52 ` 2.6.18-rc5-mm1 Matthias Hentges
2006-09-04 23:39 ` 2.6.18-rc5-mm1 Matthias Hentges
[not found] <20060901015818.42767813.akpm@osdl.org>
2006-09-01 16:40 ` 2.6.18-rc5-mm1 Maciej Rutecki
2006-09-05 16:16 ` 2.6.18-rc5-mm1 Bjorn Helgaas
2006-09-06 16:55 ` 2.6.18-rc5-mm1 Maciej Rutecki
2006-09-07 3:08 ` 2.6.18-rc5-mm1 Andrew Morton
2006-09-07 17:33 ` 2.6.18-rc5-mm1 keith mannthey
[not found] ` <1157158847.20509.10.camel@mhcln03>
2006-09-02 1:30 ` 2.6.18-rc5-mm1 Andrew Morton
[not found] ` <44F93EB3.8050500@goop.org>
2006-09-02 8:37 ` 2.6.18-rc5-mm1 Jeremy Fitzhardinge
2006-09-02 8:44 ` 2.6.18-rc5-mm1 Greg KH
2006-09-02 8:47 ` 2.6.18-rc5-mm1 Jeremy Fitzhardinge
2006-09-02 8:52 ` 2.6.18-rc5-mm1 Greg KH
2006-09-02 9:36 ` 2.6.18-rc5-mm1 Jeremy Fitzhardinge
2006-09-02 9:38 ` 2.6.18-rc5-mm1 Jeff Garzik
2006-09-02 9:47 ` 2.6.18-rc5-mm1 Jeremy Fitzhardinge
2006-09-02 9:56 ` 2.6.18-rc5-mm1 Jeremy Fitzhardinge
2006-09-09 23:47 ` 2.6.18-rc5-mm1 Jeremy Fitzhardinge
2006-09-10 16:24 ` 2.6.18-rc5-mm1 Matthias Hentges
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=44FB7AB0.10103@goop.org \
--to=jeremy@goop.org \
--cc=akpm@osdl.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oe@hentges.net \
--cc=venkatesh.pallipadi@intel.com \
/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