linux-kernel - Re: regression caused by: genirq: do not leave interupts enabled on free

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.LFD.1.10.0804110841370.3261@apollo.tec.linutronix.de>
Date:	Fri, 11 Apr 2008 09:01:02 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Yinghai Lu <yhlu.kernel@...il.com>
cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Ingo Molnar <mingo@...e.hu>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Jeff Garzik <jeff@...zik.org>,
	Ayaz Abdulla <aabdulla@...dia.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: regression caused by: genirq: do not leave interupts enabled on
 free_irq

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@...utronix.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/