From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Brian May <bam@snoopy.apana.org.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.4.2and 8139too
Date: Fri, 16 Mar 2001 08:06:56 -0500 [thread overview]
Message-ID: <3AB20FF0.33ADDFDD@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0103151527420.2382-100000@ve1drg.com> <84u24ufv9h.fsf@snoopy.apana.org.au>
Brian May wrote:
> However, I have just put a 8139 based card into my Linux 2.4.2
> system. At one stage, these lines were logged:
>
> Mar 15 09:42:56 snoopy kernel: eth0: Abnormal interrupt, status 00000020.
> Mar 15 09:43:04 snoopy kernel: eth0: Abnormal interrupt, status 00002020.
> Mar 15 10:06:52 snoopy kernel: eth0: Abnormal interrupt, status 00000020.
> Mar 15 10:06:58 snoopy kernel: eth0: Abnormal interrupt, status 00002020.
>
> The card seems to be reliable apart from these messages. It could be
> that I was playing around with the network cable or something at the
> time... However, any messages "Abnormal interrupt" make me slightly
> nervous.
They are logged at the kernel debug level, but nobody seems to notice
this fact. Oh well. The messages are for debugging only and
informational. They occur whenever an Rx or Tx error occurs.
The latest version of 8139too hides this message behind RTL8139_DEBUG.
Jeff
--
Jeff Garzik | May you have warm words on a cold evening,
Building 1024 | a full mooon on a dark night,
MandrakeSoft | and a smooth road all the way to your door.
prev parent reply other threads:[~2001-03-16 13:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-15 19:35 Kernel 2.4.2 Ted Gervais
2001-03-15 19:56 ` John Jasen
2001-03-15 21:40 ` Guennadi Liakhovetski
2001-03-15 23:49 ` Kernel 2.4.2and 8139too Brian May
2001-03-16 13:06 ` Jeff Garzik [this message]
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=3AB20FF0.33ADDFDD@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=bam@snoopy.apana.org.au \
--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