mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Charles Martin" <martinc@ucar.edu>
To: <linux-kernel@vger.kernel.org>
Cc: "'Charles Martin'" <martinc@ucar.edu>
Subject: RE: interrupts across  PCI bridge(s) not handled
Date: Mon, 3 Nov 2003 13:29:25 -0700	[thread overview]
Message-ID: <000001c3a249$2f9f30a0$c3507580@atdsputnik> (raw)
In-Reply-To: <Pine.LNX.4.44.0311031218250.20373-100000@home.osdl.org>



> -----Original Message-----
> From: Linus Torvalds [mailto:torvalds@osdl.org] 
> Sent: Monday, November 03, 2003 1:23 PM
> To: Charles Martin
> Cc: linux-kernel@vger.kernel.org; martinc@atd.ucar.edu
> Subject: RE: interrupts across PCI bridge(s) not handled
> 
> 
> 
> On Mon, 3 Nov 2003, Charles Martin wrote:
> > 
> > I enabled APIC_DEBUG, and here is the dmesg output.
> 
> 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 do notice that bus #6, which is the backplane extender,
has an APIC id of 0, but an APIC #0 was not enumerated. All other
buses get assigned to the identified APICs of 8, 9 and 10. 

Charlie


  reply	other threads:[~2003-11-03 20:29 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 [this message]
2003-11-03 21:51         ` Linus Torvalds
2003-11-03 21:46       ` Charles Martin
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='000001c3a249$2f9f30a0$c3507580@atdsputnik' \
    --to=martinc@ucar.edu \
    --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

all inboxes | Powered by JetHome®