Bug 11703 - PCMCIA Network Dropping Interrupts
Summary: PCMCIA Network Dropping Interrupts
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel
Version: 6.2
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Michael K. Johnson
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2000-05-27 03:37 UTC by tix
Modified: 2008-05-01 15:37 UTC (History)
1 user (show)

Clone Of:
Last Closed: 2002-12-14 23:38:55 UTC

Attachments (Terms of Use)

Description tix 2000-05-27 03:37:59 UTC
Using RH6.2 Workstation install (with applicable updates), started getting
kernel error messages after switching from KDE to GNOME.
Error is:
kernel: eth0: interrupt(s) dropped!

This causes all network activity to stop and the pcmcia service must be
I installed KDE as my desktop environment WITHOUT any Gnome components.
Upon installing Gnome and Helix, started getting the above errors at random
intervals ranging from 1 sec to hours after restarting the pcmcia service.

The module man page states:
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.

I suspect this is related to ESD as it was not installed prior to Gnome and
did not have this message until this time.  Can this be confirmed?  Any
work-arounds?  I tried turning off sound events and even the sound server
in Gnome-config without change.

Have tried changing the module "max_interrupt_work" and "irq_list" options
in /etc/pcmcia/config.opts to no avail.

Configuration as follows:
Toshiba Tecra 550CDT Laptop
160 M Mem
Have ran RH on this laptop since 5.1  :-)

Comment 1 Alan Cox 2000-08-08 21:39:21 UTC
Do you see this problem with the RH gnome rpms installed, or just Helix ?

Comment 2 Alan Cox 2002-12-14 23:38:55 UTC
No answer in 18 months

Note You need to log in before you can comment on or make changes to this bug.