netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Peter <dn.tlp@gmx.net>
To: netdev@oss.sgi.com
Cc: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2004@gmx.net>
Subject: forcedeth received irq with unknown events
Date: Thu, 29 Apr 2004 14:30:06 +0200	[thread overview]
Message-ID: <20040429143006.4f8b5df0.dn.tlp@gmx.net> (raw)

Hi there!

Since i plugged the DSL-Modem directly to my onboard nForce2 network
card (it's a Shuttle AN35-400 Mobo), i constantly get the following
messages in my syslog:

Apr 29 14:15:02 server kernel: eth0: received irq with unknown events
0x1. Please report
Apr 29 14:15:33 server last message repeated 28 times
Apr 29 14:15:55 server last message repeated 23 times

The message seems to be displaying more frequently the more traffic is
on the link.

Formerly, the nForce2 board was connected to a 100mbps switch to my LAN
and i didn't get any of these messages.

If you need any more info to get this fixed, just reply!

Great work with the driver!
Simon

             reply	other threads:[~2004-04-29 12:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-29 12:30 Simon Peter [this message]
2004-04-29 13:24 ` forcedeth received irq with unknown events Carl-Daniel Hailfinger
2004-04-30 11:43   ` Carl-Daniel Hailfinger

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=20040429143006.4f8b5df0.dn.tlp@gmx.net \
    --to=dn.tlp@gmx.net \
    --cc=c-d.hailfinger.kernel.2004@gmx.net \
    --cc=netdev@oss.sgi.com \
    /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).