From: Patrick Cole <z@amused.net>
To: Dennis Schoen <dennis@cobolt.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG]: RT8139 Too much work at interrupt, IntrStatus=....
Date: Tue, 19 Feb 2002 16:52:43 +1100 [thread overview]
Message-ID: <20020219055243.GA4398@jaded.anu.edu.au> (raw)
In-Reply-To: <20020109090855.GA338@cobolt.net>
In-Reply-To: <20020109090855.GA338@cobolt.net>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=unknown-8bit, Size: 1866 bytes --]
Wed, Jan 09, 2002 at 10:08:55AM +0100, Dennis Schoen wrote:
> yesterday I upgraded a firewall/router of a *busy* customer site
> from version 2.4.7 -> 2.4.17. Only 1-2 seconds after the reboot the
> network card to the DMZ stopped working. I noticed this messages in
> /var/log/messages:
>
> Jan 8 17:07:45 liquice kernel: 8139too: rx stop wait too long
> Jan 8 17:07:46 liquice kernel: eth1: Too much work at interrupt, IntrStatus=0x0050.
> Jan 8 17:07:46 liquice kernel: eth1: Too much work at interrupt, IntrStatus=0x0010.
> Jan 8 17:07:49 liquice kernel: 8139too: rx stop wait too long
> Jan 8 17:07:49 liquice kernel: eth1: Too much work at interrupt, IntrStatus=0x0001.
> Jan 8 17:07:51 liquice kernel: eth1: Too much work at interrupt, IntrStatus=0x0001.
> Jan 8 17:07:57 liquice kernel: eth1: Too much work at interrupt, IntrStatus=0x0050.
> Jan 8 17:07:57 liquice kernel: eth1: Setting 100mbps half-duplex based on auto-negotiated partner ability 40a1.
> Jan 8 17:08:09 liquice kernel: NETDEV WATCHDOG: eth1: transmit timed out
> Jan 8 17:08:09 liquice kernel: eth1: Setting 100mbps half-duplex based on auto-negotiated partner ability ffff.
>
> after a reboot the same problem occured.
>
> Switching back to v2.4.7 solved the problem so I don't think that
> it's a hardware issue.
Hi dennis, I'm getting these messages too with an identical card...
8139 (rev 10)... seems to have started happening after I went to
2.4.17... strangely enough I'm getting very similar mæssages on the
machine right beside it.. running 2.4.13, SMP, and a 3com 3c905b
(Boomerang).
Anyone have any insight on this one?
--
Patrick Cole - Debian Developer <ltd@debian.org>
- John Curtin, ANU <Patrick.Cole@anu.edu.au>
- Linear-G Network Solutions <z@linearg.com>
- PGP 1024R/60D74C7D C8E0BC7969BE7899AA0FEB16F84BFE5A
next prev parent reply other threads:[~2002-02-19 5:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-09 9:08 Dennis Schoen
[not found] ` <Pine.LNX.4.33.0201091759120.22941-100000@coffee.psychology.mcmaster.ca>
2002-01-10 9:52 ` Dennis Schoen
2002-02-19 5:52 ` Patrick Cole [this message]
2002-02-26 20:57 ` Jes Sorensen
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=20020219055243.GA4398@jaded.anu.edu.au \
--to=z@amused.net \
--cc=dennis@cobolt.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
all inboxes | Powered by JetHome®