linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc Heckmann <mh@nadir.org>
To: linux-kernel@vger.kernel.org
Subject: 2.4.22-pre9, 8139too driver: eth0: Too much work at interrupt
Date: Tue, 5 Aug 2003 11:58:12 -0400	[thread overview]
Message-ID: <20030805155811.GA17539@nadir.org> (raw)

Hi,

[I searched lkml archives for this, but nothing really useful came up,
othewr than it did not happen on much older versions of 2.4.x]

When I transfer any large files via scp or other means on the local
100 Mbps network, I get the following error messages:

eth0: Too much work at interrupt: IntrStatus=0x0040

Are they just debug printk's? My NFS connections stall and sometimes
cause errors in programs writing via NFS. (The machine exhibiting the
symptoms is the NFS client.)

This is with 2.4.22-pre9, UP IO-APIC and ACPI enabled. The board is a
Gigabyte GA7VXP with onboard 8139 ethernet.

This also happens with 2.4.21. I haven't tried any older kernels since
the machine is new.

Does anyone have any ideas? thanks in advance.

-m



             reply	other threads:[~2003-08-05 15:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-05 15:58 Marc Heckmann [this message]
2003-08-11 21:01 ` UPDATE: 2.4.22-pre9, 8139too driver: eth0: Too much work at interrupt Marc Heckmann

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=20030805155811.GA17539@nadir.org \
    --to=mh@nadir.org \
    --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;
as well as URLs for NNTP newsgroup(s).