mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gabi Davar <gabi@SHUNRA.co.il>
To: "'Thomas Foerster'" <puckwork@madz.net>
Cc: "Linux Kernel Mailing List (E-mail)" <linux-kernel@vger.kernel.org>
Subject: RE: eth0: Something Wicked happened! 2008.
Date: Thu, 15 Feb 2001 15:21:31 +0200	[thread overview]
Message-ID: <F1629832DE36D411858F00C04F24847A035902@SALVADOR> (raw)

Check out http://www.scyld.com/network/ethercard.html look under errata -
Via Rhine.

It seems your link either went down or had too many collisions. This caused
the driver to yell "something wicked happened".

-Gabi

> -----Original Message-----
> From: Thomas Foerster [mailto:puckwork@madz.net]
> Sent: Thursday, February 15, 2001 2:37 PM
> To: linux-kernel@vger.kernel.org
> Subject: eth0: Something Wicked happened! 2008.
> 
> 
> Hello,
> 
> yesterday i successfully set up Linux-2.2.18 on a new machine 
> (Pentium-III-667, D-Link 530TX (via-rhine) network-card, 256MB Ram).
> 
> The system is now running for about 1 day, and now i get 
> lot's of these messages :
> 
> eth0: Something Wicked happened! 2008.
> 
> This happened on another machine a few months ago (never 
> appeared again for months now).
> 
> What does this mean?? Is my NIC damaged??
> 
> Thanx a lot,
>   Thomas
> 
> -
> 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://www.tux.org/lkml/
> 

             reply	other threads:[~2001-02-15 13:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-15 13:21 Gabi Davar [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-02-15 12:36 Thomas Foerster

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=F1629832DE36D411858F00C04F24847A035902@SALVADOR \
    --to=gabi@shunra.co.il \
    --cc=linux-kernel@vger.kernel.org \
    --cc=puckwork@madz.net \
    /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®