public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Newton <newton@unb.ca>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: FWD: RE: excessive interrupts on network cards
Date: Tue, 25 Sep 2001 20:04:54 -0300	[thread overview]
Message-ID: <3BB13732@webmail1> (raw)

Francois Romieu got me to run 'lspci -x', and came to the conclusion that the 
net card and scsi card are sharing IRQs...

  Someone just told me tha the had had a sound card and a network card sharing 
IRQs, and that caused the network card to generate 'oodles of interrupts for 
no apparent reason'.

  This on the right track?

Thanks

Chris

>===== Original Message From Francois Romieu <romieu@cogenit.fr> =====
Chris Newton <newton@unb.ca> :
[...]
> 00:02.0 Ethernet controller: Intel Corporation 82557 [Ethernet Pro 100] (rev
> 08)
> 00: 86 80 29 12 17 01 90 02 08 00 00 02 08 20 00 00
> 10: 00 20 10 fe c1 ec 00 00 00 00 00 fe 00 00 00 00
> 20: 00 00 00 00 00 00 00 00 00 00 00 00 28 10 9b 00
> 30: 00 00 00 fd dc 00 00 00 00 00 00 00 0b 01 08 38
                                           ^
[...]
> 01:02.0 SCSI storage controller: Adaptec 7899P (rev 01)
> 00: 05 90 cf 00 16 01 b0 02 01 00 00 01 08 20 80 80
> 10: 01 dc 00 00 04 10 00 f9 00 00 00 00 00 00 00 00
> 20: 00 00 00 00 00 00 00 00 00 00 00 00 28 10 ce 00
> 30: 00 00 00 f8 dc 00 00 00 00 00 00 00 05 01 28 19
                                           ^
[...]
> 01:02.1 SCSI storage controller: Adaptec 7899P (rev 01)
> 00: 05 90 cf 00 16 01 b0 02 01 00 00 01 08 20 80 80
> 10: 01 d8 00 00 04 00 00 f9 00 00 00 00 00 00 00 00
> 20: 00 00 00 00 00 00 00 00 00 00 00 00 28 10 ce 00
> 30: 00 00 00 f8 dc 00 00 00 00 00 00 00 0b 02 28 19
                                           ^
[...]
> 01:06.0 Ethernet controller: 3Com Corporation 3c980-TX 10/100baseTX NIC
> [Python-T] (rev 78)
> 00: b7 10 05 98 17 01 10 02 78 00 00 02 08 20 00 00
> 10: 81 d4 00 00 00 24 00 f9 00 00 00 00 00 00 00 00
> 20: 00 00 00 00 00 00 00 00 00 00 00 00 b7 10 00 10
> 30: 00 00 00 f8 dc 00 00 00 00 00 00 00 05 01 0a 0a
                                           ^
[...]
> 01:08.0 Ethernet controller: 3Com Corporation 3c980-TX 10/100baseTX NIC
> [Python-T] (rev 78)
> 00: b7 10 05 98 17 01 10 02 78 00 00 02 08 20 00 00
> 10: 01 d4 00 00 00 20 00 f9 00 00 00 00 00 00 00 00
> 20: 00 00 00 00 00 00 00 00 00 00 00 00 b7 10 00 10
> 30: 00 00 00 f8 dc 00 00 00 00 00 00 00 0b 01 0a 0a
                                           ^
Each of your ethernet adapter shares an irq with a scsi controller.
I had some results pulling some cards from the PCI slots and moving
the network adapter around until its irq differs but I won't claim
it's the cure for your problem (it was on HP Netserver motherboards).

--
Ueimor


             reply	other threads:[~2001-09-25 22:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-25 23:04 Chris Newton [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-09-25 23:19 FWD: RE: excessive interrupts on network cards Chris Newton
2001-09-25 23:58 ` Tim Moore
2001-09-26 15:41 Chris Newton

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=3BB13732@webmail1 \
    --to=newton@unb.ca \
    --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