Next-in-Thread Next Message

None Re: Question: eth0: interrupt(s) dropped! messages 

Forum: PCMCIA Network Adapter Issues
Re: Question eth0: interrupt(s) dropped! messages (Rick Lerner)
Date: 1999, Nov 01
From: David Hinds <>

On Mon, Nov 01, 1999 at 03:08:48PM -0800, Rick Lerner wrote:
> Nov  1 15:46:06 localhost kernel: eth0: interrupt(s) dropped! 

"interrupt(s) dropped" means that the card indicates it tried to
generate an interrupt, but the host didn't actually see it.

There are a couple possible causes for this.  One is that another
system device could be occupying this interrupt line, electrically
interfering with the PCMCIA card's attempt to trigger an interrupt.
Another possibility is a problem with interrupt setup in the PCMCIA

In the first case, you could exclude the interrupt line used by the
PCMCIA device in your /etc/pcmcia/config.opts file, to force the card
to get a different interrupt.  The second case is more tricky because
it indicates a problem in the Linux socket driver.

In your case, I think it is a problem of the second type.  The O2Micro
CardBus bridges have some known problems with the current Linux driver
package.  Interrupt routing is handled differently from other bridges,
and the datasheets are confusing.

One thing to try: in /etc/sysconfig/pcmcia, set:


which will disable the i82365 module's interrupt scanning code.  The
driver seems to think that irq 10 is the only one available for
PCMCIA, and that seems likely to be wrong.  It is possible that
another interrupt line will behave better.

If this doesn't improve things, I'd count your blessings, since you've
picked a card with a driver that (relatively) painlessly recovers from
missed interrupts.  You won't get great performance, but it is better
than a card that doesn't work at all.

-- Dave

Next-in-Thread Next Message

Messages Inline: 1 All Outline: 1 2 All

1. Ok do_scan did the trick by Rick Lerner, 1999, Nov 02

Add Message to: "Re: Question: eth0: interrupt(s) dropped! messages"

Members Subscribe Admin Mode Show Frames Help for HyperNews at 1.10