All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roland Dreier <roland@topspin.com>
To: Lee Revell <rlrevell@joe-job.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Richard Rosenberg <richrosenberg@earthlink.net>
Subject: Re: weird APIC problem: irq 177 & irq 185
Date: Sat, 09 Oct 2004 18:38:26 -0700	[thread overview]
Message-ID: <52fz4nl5d9.fsf@topspin.com> (raw)
In-Reply-To: <1097368522.1363.41.camel@krustophenia.net> (Lee Revell's message of "Sat, 09 Oct 2004 20:35:23 -0400")

    Lee> There is no such thing as IRQ 177 and IRQ 185, correct?

With CONFIG_PCI_MSI (used to be CONFIG_PCI_USE_VECTOR) it's entirely
possible to get interrupt numbers like that.  On my dual Xeon system,
I have /proc/interrupts that looks like:

           CPU0       CPU1       CPU2       CPU3       
  0:  288964788          0          0          0    IO-APIC-edge  timer
  2:          0          0          0          0          XT-PIC  cascade
  4:        303          0          0          0    IO-APIC-edge  serial
 14:      67708          1          0          0    IO-APIC-edge  ide0
 15:         13          0          0          0    IO-APIC-edge  ide1
153:          0          0          0          0   IO-APIC-level  uhci_hcd
161:    1590294          0          0          0   IO-APIC-level  eth0
169:          0          0          0          0   IO-APIC-level  uhci_hcd
177:          0          0          0          0   IO-APIC-level  uhci_hcd
201:         81          0          0          0       PCI-MSI-X  ib_mthca (comp)
209:          2          0          0          0       PCI-MSI-X  ib_mthca (async)
217:       2171          0          0          0       PCI-MSI-X  ib_mthca (cmd)
NMI:   57794488   57794274   57794272   57794270 
LOC:  288981914  288981943  288981942  288981941 
ERR:          0
MIS:          0

 - Roland

      reply	other threads:[~2004-10-10  1:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-10  0:35 weird APIC problem: irq 177 & irq 185 Lee Revell
2004-10-10  1:38 ` Roland Dreier [this message]

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=52fz4nl5d9.fsf@topspin.com \
    --to=roland@topspin.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richrosenberg@earthlink.net \
    --cc=rlrevell@joe-job.com \
    /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.