From: "Charles Martin" <martinc@ucar.edu>
To: <linux-kernel@vger.kernel.org>
Cc: <martinc@atd.ucar.edu>
Subject: RE: interrupts across PCI bridge(s) not handled
Date: Mon, 3 Nov 2003 14:46:57 -0700 [thread overview]
Message-ID: <000001c3a254$043d88c0$c3507580@atdsputnik> (raw)
In-Reply-To: <Pine.LNX.4.44.0311031218250.20373-100000@home.osdl.org>
>
> Hmm..
>
> The MP tables mention IRQ's up to 51, but no further.
>
> But the PIRQ routing tables talk about irqs 92-95 for bus 6.
>
> It really looks like the IRQ routing entries are just broken. One
> potential fix is to enable ACPI, and hope that the ACPI irq
> routing isn't
> as broken as the PIRQ stuff.
>
> Other than that I don't see anything we can do. Anybody else?
>
> Linus
>
I enabled ACPI, and the interrupts are now assigned correctly,
and in the range of 48-51:
CPU0 CPU1
48: 878 389 IO-APIC-level piraq
49: 923 336 IO-APIC-level piraq
50: 17239 838 IO-APIC-level ioc2, piraq
51: 879 404 IO-APIC-level piraq
They are now getting handled properly, i.e. I am receiveing
interrupts from the boards located in the backplane extender.
This is with 2.4.22.
I didn't realize that ACPI is related to interrupt management
as well as power control. Is there any downside to using ACPI?
Thanks,
Charlie
next prev parent reply other threads:[~2003-11-03 21:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-03 16:08 Charles Martin
2003-11-03 17:04 ` Linus Torvalds
2003-11-03 19:50 ` Charles Martin
2003-11-03 20:23 ` Linus Torvalds
2003-11-03 20:29 ` Charles Martin
2003-11-03 21:51 ` Linus Torvalds
2003-11-03 21:46 ` Charles Martin [this message]
2003-11-04 0:31 ` Linus Torvalds
2003-11-04 9:51 ` Jes Sorensen
2003-11-04 2:47 ` Zwane Mwaikambo
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='000001c3a254$043d88c0$c3507580@atdsputnik' \
--to=martinc@ucar.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=martinc@atd.ucar.edu \
/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
all inboxes | Powered by JetHome®