From: Jay Cliburn <jacliburn@bellsouth.net>
To: Robert Hancock <hancockr@shaw.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.18-rc5-mm1 unusual IRQ number for VIA device
Date: Mon, 04 Sep 2006 19:57:30 -0500 [thread overview]
Message-ID: <44FCCB7A.8000105@bellsouth.net> (raw)
In-Reply-To: <44FCA920.4020706@bellsouth.net>
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?
next prev parent reply other threads:[~2006-09-05 0:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.zOFUKsGFxa+fu0uGVN6HuRT+Krg@ifi.uio.no>
[not found] ` <fa.2CAUcMm0GNX2+CNwugoJEUNtwzQ@ifi.uio.no>
2006-09-04 22:13 ` 2.6.18-rc5-mm1 unusual IRQ number for VIA device Robert Hancock
2006-09-04 22:30 ` Jay Cliburn
2006-09-05 0:57 ` Jay Cliburn [this message]
2006-09-05 14:32 ` Robert Hancock
2006-09-04 13:51 Jay Cliburn
2006-09-04 15:26 ` Jay Cliburn
2006-09-05 7:05 ` Andrew Morton
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=44FCCB7A.8000105@bellsouth.net \
--to=jacliburn@bellsouth.net \
--cc=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.org \
/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