From: Christian Ullrich <chris@chrullrich.de>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.1: Abnormal interrupt from RTL8139
Date: Mon, 12 Feb 2001 06:57:20 +0100 [thread overview]
Message-ID: <20010212065720.A1120@christian.chrullrich.de> (raw)
In-Reply-To: <20010208093854.A1122@christian.chrullrich.de> <3A874CB4.717C101C@mandrakesoft.com>
In-Reply-To: <3A874CB4.717C101C@mandrakesoft.com>; from jgarzik@mandrakesoft.com on Sun, Feb 11, 2001 at 09:38:44PM -0500
* Jeff Garzik wrote on Sunday, 2001-02-11:
> Christian Ullrich wrote:
> > I'm getting some of these messages in syslog:
> > Feb 6 07:38:35 christian kernel: eth0: Abnormal interrupt, status 00000010.
> > Feb 6 07:38:35 christian kernel: eth0: Abnormal interrupt, status 00000010.
> > Feb 6 07:38:35 christian kernel: eth0: Abnormal interrupt, status 00000020.
> > Feb 7 17:32:53 christian kernel: eth0: Abnormal interrupt, status 00000041.
> [...]
> > I have not observed any effects related to these messages.
>
> Those messages are logged at the debugging level... if they bother you,
> don't log kern.debug...
Well, doing something related to debugging implies that there _is_
something to debug. But since I don't have any problems and not
more than a few messages like these, thanks for your help.
--
Christian Ullrich Registrierter Linux-User #125183
"Sie können nach R'ed'mond fliegen -- aber Sie werden sterben"
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://vger.kernel.org/lkml/
next prev parent reply other threads:[~2001-02-12 17:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-08 8:38 Christian Ullrich
2001-02-12 2:38 ` Jeff Garzik
2001-02-12 5:57 ` Christian Ullrich [this message]
2001-02-12 17:51 ` Fernando Fuganti
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=20010212065720.A1120@christian.chrullrich.de \
--to=chris@chrullrich.de \
--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®