All of lore.kernel.org
 help / color / mirror / Atom feed
From: miquels@cistron-office.nl (Miquel van Smoorenburg)
To: linux-kernel@vger.kernel.org
Subject: Re: XT-PIC vs IO-APIC and PCI devices
Date: Fri, 30 Nov 2001 11:44:28 +0000 (UTC)	[thread overview]
Message-ID: <9u7res$3iq$2@ncc1701.cistron.net> (raw)
In-Reply-To: <Pine.LNX.4.33.0111301241410.4564-100000@netfinity.realnet.co.sz>

In article <Pine.LNX.4.33.0111301241410.4564-100000@netfinity.realnet.co.sz>,
Zwane Mwaikambo  <zwane@linux.realnet.co.sz> wrote:
>	I'm trying to get a PCI device (network) to work on one of my
>boxes, and thus far i've only managed to get it to work with "noapic".
>Without that kernel option the card stops processing interrupts (as can be
>observed in /proc/interrupts) after about ~100 on each CPU. Are there any
>things i should look out for when trying to track down the problem?
>I've tried swapping the card around in different slots just in case it
>was an IRQ routing problem (as suggested by various folks) to no avail.
>The box is an IBM Netfinity 3500M20 SMP rig.

What does cat /proc/interrupts say in APIC mode? Perhaps it thinks the
device uses edge-triggered interrupts instead of level-triggered ?

Mike.
-- 
"Only two things are infinite, the universe and human stupidity,
 and I'm not sure about the former" -- Albert Einstein.


  reply	other threads:[~2001-11-30 11:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-30 11:05 XT-PIC vs IO-APIC and PCI devices Zwane Mwaikambo
2001-11-30 11:44 ` Miquel van Smoorenburg [this message]
2001-11-30 12:49 ` Zwane Mwaikambo
2001-11-30 12:59   ` Miquel van Smoorenburg
2001-11-30 13:12   ` Maciej W. Rozycki
2001-11-30 13:30     ` Zwane Mwaikambo
2001-11-30 14:03       ` Maciej W. Rozycki
     [not found] <Pine.LNX.4.10.10111301139590.24770-100000@coffee.psychology.mcmaster.ca>
2001-12-01 11:21 ` 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='9u7res$3iq$2@ncc1701.cistron.net' \
    --to=miquels@cistron-office.nl \
    --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.