All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Charles Martin" <martinc@ucar.edu>
To: <linux-kernel@vger.kernel.org>
Subject: interrupts across  PCI bridge(s) not handled
Date: Mon, 3 Nov 2003 09:08:27 -0700	[thread overview]
Message-ID: <004201c3a224$bad501b0$c3507580@atdsputnik> (raw)

I have a pci backplane extender, with 4 cards 
(named piraq) in it. The cards are detected by 
the PCI system, and irqs 92-95 are assigned, 
as shown in /var/log/messages:

kernel: PCI->APIC IRQ transform: (B6,I4,P0) -> 93 
kernel: PCI->APIC IRQ transform: (B6,I6,P0) -> 95 
kernel: PCI->APIC IRQ transform: (B6,I7,P0) -> 92
kernel: PCI->APIC IRQ transform: (B6,I9,P0) -> 94

My driver loads happily, with succesful registering 
of these interrupts. However, the interrupts don't 
get handled properly, and /proc/interrupts shows that 
they have not been correctly setup:

          CPU0       CPU1
  0:       4946      10162    IO-APIC-edge  timer
  1:         53        131    IO-APIC-edge  keyboard
  2:          0          0          XT-PIC  cascade
  8:          1          0    IO-APIC-edge  rtc
 12:       4816          0    IO-APIC-edge  PS/2 Mouse
 15:        903          1    IO-APIC-edge  ide1
 16:          0          0   IO-APIC-level  usb-uhci
 18:          0          0   IO-APIC-level  usb-uhci
 19:          0          0   IO-APIC-level  usb-uhci
 20:          3          0   IO-APIC-level  ohci1394
 23:          0          0   IO-APIC-level  ehci_hcd
 24:        748          0   IO-APIC-level  eth0
 25:         43          0   IO-APIC-level  ioc0
 26:         43          0   IO-APIC-level  ioc1
 50:       9142       4235   IO-APIC-level  ioc2
 92:          0          0            none  piraq
 93:          0          0            none  piraq
 94:          0          0            none  piraq
 95:          0          0            none  piraq
NMI:          0          0
LOC:      15017      15016
ERR:          0
MIS:          0

If I boot with "noapic", the interrupts do get 
assigned to XT-PIC, and will trigger correctly.

Same results are seen in 2.4.22 and 2.6.0-test9.

Thanks,
Charlie

N.B. System is Dell 650 w/ dual Xeons.
Backplane extender is a Magma. This scheme uses
a PCI interconnect card in both the Dell and 
the Magma, with a connecting cable.


             reply	other threads:[~2003-11-03 16:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-03 16:08 Charles Martin [this message]
2003-11-03 17:04 ` interrupts across PCI bridge(s) not handled 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
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='004201c3a224$bad501b0$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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.