linux-kernel - Re: 2.6.19-rc5 x86_64 irq 22: nobody cared

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] [day] [month] [year] [list]

Message-ID: <m1d57wo86r.fsf@ebiederm.dsl.xmission.com>
Date:	Thu, 09 Nov 2006 10:12:44 -0700
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	Stephen Hemminger <shemminger@...l.org>
Cc:	Adrian Bunk <bunk@...sta.de>,
	Olivier Nicolas <olivn@...llprod.org>,
	Takashi Iwai <tiwai@...e.de>, Jaroslav Kysela <perex@...e.cz>,
	linux-kernel@...r.kernel.org, alsa-devel@...a-project.org,
	gregkh@...e.de, linux-pci@...ey.karlin.mff.cuni.cz,
	len.brown@...el.com, linux-acpi@...r.kernel.org,
	Andrew Morton <akpm@...l.org>,
	Linus Torvalds <torvalds@...l.org>
Subject: Re: 2.6.19-rc5 x86_64  irq 22: nobody cared

Stephen Hemminger <shemminger@...l.org> writes:

> On Thu, 9 Nov 2006 07:49:56 +0100
> Adrian Bunk <bunk@...sta.de> wrote:
>
>> On Wed, Nov 08, 2006 at 01:44:29PM +0100, Olivier Nicolas wrote:
>> 
>> > Hi,
>> 
>> Hi Olivier,
>> 
>> > 2.6.19-rc5 does not boot properly, I have tried pci=routeirq, irpoll 
>> > without success.
>> > 
>> > Full details (.config, dmesg, /proc/interrupts) are in 
>> > http://olivn.trollprod.org/2.6.19-rc5-irq.tar.gz
>> 
>> thanks for your report!
>> 
>> I might be wrong, but looking at the dmesg:
>> - irq 22 is the hda_intel IRQ
>> - the "irq 22: nobody cared" is immediately before the
>>   "hda_intel: No response from codec, disabling MSI..."
>> - in the routeirq case, the hda_intel IRQ as well as the
>>   IRQ in the error message change to 21
>> 
>> So it might be related to the hda_intel MSI check.
>
> More likely the MSI management routines don't work for disabling MSI.

Well brand new MSI handling could be buggy, the disable hypothesis doesn't
make much sense on boot up.

> I am debugging a problem where MSI doesn't work across suspend/resume,
> I suspect the base MSI code needs fixing.

Rethinking the interfaces maybe I don't think the code is broken I think
most likely it is just not designed to do the right thing.  I remember
thinking how horrible that code is, when I read through it.

Eric

-
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/