The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: John Wong <kernel@implode.net>
To: linux-kernel@vger.kernel.org
Subject: via-rhine on 2.4.23-pre6 Too much work at interrupt, status=0x00001000.
Date: Thu, 16 Oct 2003 12:27:17 -0700	[thread overview]
Message-ID: <20031016192717.GA2749@gambit.implode.net> (raw)

The system used to run 2.4.22 and did not have this too much work
problem.  There were some other hardware changes.  The system used to be
a Pentium 100 on a Triton 430FX chipset Intel Advanced/EV board.  Now it 
is a K6 2 - 500 on a Via Apollo MVP3 chipset on FIC VA-503+ board.
The NIC stayed the same.  The kernel was recompiled and ACPI was
enabled.

I noticed in 2.4.23-pre2 -> pre3
	 [netdrvr] sync with 2.5: epic100, fealnx, via-rhine, winbond-840

via-rhine.c:v1.10-LK1.1.19  July-12-2003  Written by Donald Becker
  http://www.scyld.com/network/via-rhine.html
eth0: VIA VT86C100A Rhine at 0xe4001000, 00:80:c8:d3:36:a6, IRQ 10.
eth0: MII PHY found at address 8, status 0x782d advertising 05e1 Link 40a1.


eth0: Too much work at interrupt, status=0x00001000.
eth0: Too much work at interrupt, status=0x00001000.
eth0: Too much work at interrupt, status=0x00001000.
eth0: Too much work at interrupt, status=0x00001000.
eth0: Too much work at interrupt, status=0x00001000.
eth0: Too much work at interrupt, status=0x00001000.
eth0: Too much work at interrupt, status=0x00001000.
eth0: Too much work at interrupt, status=0x00001000.
eth0: Too much work at interrupt, status=0x00001000.
eth0: Too much work at interrupt, status=0x00001000.

John

                 reply	other threads:[~2003-10-16 19:27 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=20031016192717.GA2749@gambit.implode.net \
    --to=kernel@implode.net \
    --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