linux-kernel - Re: 2.6.18-rc5-mm1 unusual IRQ number for VIA device

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]

Date:	Mon, 04 Sep 2006 19:57:30 -0500
From:	Jay Cliburn <jacliburn@...lsouth.net>
To:	Robert Hancock <hancockr@...w.ca>
CC:	linux-kernel@...r.kernel.org
Subject: Re: 2.6.18-rc5-mm1 unusual IRQ number for VIA device

Jay Cliburn wrote:
> Robert Hancock wrote:
>> Jay Cliburn wrote:
>>> Jay Cliburn wrote:
>>>> Running 2.6.18-rc5.mm1 on an Asus M2V mainboard with dual-core 
>>>> Athlon cpu, the onboard audio device gets assigned and IRQ of 8410.  
>>>> Under 2.6.18-rc4-mm3, the same device gets assigned IRQ 17.  Is this 
>>>> a way to get around this?
>>>
>>> What I meant to ask is:  Is there a way to get around this?
>>>
>>> Thanks,
>>> Jay
>>
>> What do you think needs to be "gotten around"? It is using MSI 
>> interrupts, I think that the IRQ numbers will be different.
>>
> I'll have to go research what MSI interrupts are.  Thanks for the pointer.

Nothing I've read about MSI so far indicates that an IRQ number greater 
than 255 is permissible, yet this device gets assigned an IRQ number of 
8,410 when MSI is enabled.  Booting 2.6.18-rc5-mm1 with pci=nomsi causes 
the device to be assigned IRQ 17 instead of 8410.

The problem with the large IRQ number is made manifest in Fedora's 
irqbalance program, which is run as an init script.  An array is built 
in that program that's indexed by IRQ number, with a max of 255.  When 
the program attempts to index element 8410, it segfaults.

Are IRQ numbers greater than 255 allowed with MSI?

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