From: Aaron Baer <judah@opusnet.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: 3c574_cs driver interrupt dropped errors?
Date: 02 Apr 2002 13:13:17 -0800 [thread overview]
Message-ID: <1017781997.5510.6.camel@laptop> (raw)
Google sure isn't turning up much detailed information about this so I
thought I'd see if anyone else here has seen this error before.
(I've seen this with 2.4.17 and 2.4.18 currently running 2.4.18+preempt)
I'm getting a lot of this in /var/log/messages
Mar 26 11:37:52 laptop kernel: eth0: interrupt(s) dropped!
Mar 26 11:49:14 laptop kernel: eth0: interrupt(s) dropped!
Mar 26 11:52:47 laptop kernel: eth0: interrupt(s) dropped!
Mar 26 11:55:22 laptop kernel: eth0: interrupt(s) dropped!
it's a 3Com 572/574 Fast Ethernet card using the 3c574_cs.o driver
the man page says this, which makes sense:
eth#: interrupt(s) dropped!
Indicates that the driver did not receive an interrupt notification for
some reason. The driver will poll the card (with a significant
performance penalty) if the problem persists. The most likely cause is
an interrupt conflict and/or host bridge configuration problem.
because the source code says this,
(/usr/src/linux/drivers/net/pcmcia/3c574_cs.c)
<snip>
/* Check for pending interrupt with expired latency timer: with
this, we can limp along even if the interrupt is blocked */
if ((inw(ioaddr + EL3_STATUS) & IntLatch) &&
(inb(ioaddr + Timer) == 0xff)) {
if (!lp->fast_poll)
printk(KERN_INFO "%s: interrupt(s) dropped!\n",
dev->name);
el3_interrupt(dev->irq, lp, NULL);
lp->fast_poll = HZ;
}
</snip>
And I've tried multiple interrupts by manipulating
/etc/pcmcia/config.opts
Making sure that the irq's used do not conflict with anything in
/proc/interrupts
Yet I still see this problem. Anyone have any idea what might be going
on here?
Thanks,
A-
--
----
Aaron Baer
judah@opusnet.com
http://www.cat.pdx.edu/~baera/
reply other threads:[~2002-04-02 21:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1017781997.5510.6.camel@laptop \
--to=judah@opusnet.com \
--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.