From: Ingo Molnar <mingo@elte.hu>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Thomas Gleixner <tglx@linutronix.de>,
Jeff Garzik <jeff@garzik.org>, Ayaz Abdulla <aabdulla@nvidia.com>,
LKML <linux-kernel@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: regression caused by: genirq: do not leave interupts enabled on free_irq
Date: Tue, 15 Apr 2008 10:17:44 +0200 [thread overview]
Message-ID: <20080415081744.GB19452@elte.hu> (raw)
In-Reply-To: <86802c440804150103s59f6fe16ncf08a3154c03d2bb@mail.gmail.com>
* Yinghai Lu <yhlu.kernel@gmail.com> wrote:
> > Do we think it's a bug in the RHEL 5.1 kernel? Even so, that's a
> > problem for the 2.6.25 kernel.
>
> it is RHEL 5.1 kernel problem, it has code for maskbit with msi there,
> but that does work...
addendum - basically the argument is: we should kexec conservatively -
i.e. we should leave as few assumptions and hw changes around as
possible. So restoring the MSI state is fair enough as a robustness fix,
even though only kexec to older kernels is affected.
clearly 2.6.26 material, not 2.6.25.
Ingo
next prev parent reply other threads:[~2008-04-15 8:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-11 6:13 regression caused by: genirq: do not leave interupts enabled on free_irq Yinghai Lu
2008-04-11 7:01 ` Thomas Gleixner
2008-04-11 7:14 ` Yinghai Lu
2008-04-11 7:17 ` Yinghai Lu
2008-04-11 7:30 ` Eric W. Biederman
2008-04-11 8:40 ` Yinghai Lu
2008-04-11 15:59 ` Daniel Barkalow
2008-04-11 10:31 ` Thomas Gleixner
2008-04-11 15:19 ` Rafael J. Wysocki
2008-04-11 16:23 ` Yinghai Lu
2008-04-11 18:22 ` Yinghai Lu
2008-04-11 19:48 ` Yinghai Lu
2008-04-15 7:44 ` Andrew Morton
2008-04-15 8:03 ` Yinghai Lu
2008-04-15 8:17 ` Ingo Molnar [this message]
2008-04-15 8:23 ` Yinghai Lu
2008-04-15 8:06 ` Yinghai Lu
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=20080415081744.GB19452@elte.hu \
--to=mingo@elte.hu \
--cc=aabdulla@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=tglx@linutronix.de \
--cc=yhlu.kernel@gmail.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