linux-kernel - Re: 2.6.33-rc8 regression: irq11: nobody cared, during yenta registration

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.SOC.1.00.1002150743540.21314@math.ut.ee>
Date:	Mon, 15 Feb 2010 08:03:52 +0200 (EET)
From:	Meelis Roos <mroos@...ux.ee>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
cc:	Linux Kernel list <linux-kernel@...r.kernel.org>,
	Kernel Testers List <kernel-testers@...r.kernel.org>,
	Maciej Rutecki <maciej.rutecki@...il.com>,
	"H. Peter Anvin" <hpa@...or.com>, Ingo Molnar <mingo@...e.hu>
Subject: Re: 2.6.33-rc8 regression: irq11: nobody cared, during yenta
 registration

> > Just tried 2.6.33-rcx8 on my laptop (Thinkpad X20 in a dock) that was 
> > last running 2.6.33-rc5 without problems. Gor irq11: nobody carec like 
> > below. Seems to be repeatabale. lspci also below.
> 
> I have created the Bugzilla entry at http://bugzilla.kernel.org/show_bug.cgi?id=15307
> for your report.
> 
> Peter, Ingo, did we do anything to the interrupt handling between .33-rc5 and .33-rc8?

I just retested it and the problem appears even in -rc5 (missed it 
before). Come to think of it, I only tested -rc5 out of dock before.

With dock, the problem is there in 2.6.33-rc4-00399-g24bc734.

Without dock, even -rc8 is OK, so it only happens docked.

Will try to bisect but this takes time because I'm rarely near that 
computer.

-- 
Meelis Roos (mroos@...ux.ee)
--
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/