From: Thomas Gleixner <tglx@linutronix.de>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Jeff Garzik <jeff@garzik.org>, Ayaz Abdulla <aabdulla@nvidia.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: regression caused by: genirq: do not leave interupts enabled on free_irq
Date: Fri, 11 Apr 2008 09:01:02 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.1.10.0804110841370.3261@apollo.tec.linutronix.de> (raw)
In-Reply-To: <86802c440804102313k4546cd73s7bffb30a14239472@mail.gmail.com>
On Thu, 10 Apr 2008, Yinghai Lu wrote:
> last week found:
> after latest kernel kexec RHEL 5.1 or other stack kernel, the nvidia
> forcedeth doesn't work anymore.
>
> I stared at forcedeth.c two days. and revert every patches about that
> doesn't help.
So forcedeth does not come up again, when you kexec from linus.git
into an older distro kernel. Or is it the other way round ?
Does a non kexec boot work ?
> and figure out 2.6.25-rc2 works.
>
> with git-bisect found
>
> commit 89d694b9dbe769ca1004e01db0ca43964806a611
> Author: Thomas Gleixner <tglx@linutronix.de>
> Date: Mon Feb 18 18:25:17 2008 +0100
>
> genirq: do not leave interupts enabled on free_irq
>
> caused the regression.
>
> it affected all my servers that are using Nvidia MCP55.
>
> maybe we need to revert that patch.
Which causes an interrupt storm on the enabled irq line, when the
interrupt line is still active for whatever reason. So we trade one
badness vs. the other.
Reverting the patch is not going to give us any answer about the real
problem.
Is there anything in dmesg, which might give us an hint about that ?
Thanks,
tglx
next prev parent reply other threads:[~2008-04-11 7:03 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 [this message]
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
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=alpine.LFD.1.10.0804110841370.3261@apollo.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=aabdulla@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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