public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Petersohn <jkp@sgi.com>
To: linux-kernel@vger.kernel.org
Subject: protocol is buggy?
Date: Tue, 25 Sep 2001 12:42:35 -0500 (CDT)	[thread overview]
Message-ID: <XFMail.20010925124235.jkp@sgi.com> (raw)

Hi all,

getting the following in dmesg. Don't know if it's iptables related or
not. The ethernet card in question is a Intel EtherPRO 100 with the
stock 2.4.8 driver. Everything is working great, but I'm mostly
curious why these messages appear. A search in Google or LKM 
didn't turn anything immidiately, but I might have missed something.

protocol 0008 is buggy, dev eth1
protocol 0008 is buggy, dev eth1
protocol 0008 is buggy, dev eth1
protocol 0008 is buggy, dev eth1
NET: 16 messages suppressed.
protocol 0008 is buggy, dev eth1

/proc/pci:
  Bus  0, device  19, function  0:
    Ethernet controller: Intel Corporation 82557 [Ethernet Pro 100] (rev 2).
      IRQ 5.
      Master Capable.  Latency=64.  Min Gnt=8.Max Lat=56.
      Prefetchable 32 bit memory at 0xe4100000 [0xe4100fff].
      I/O at 0x7400 [0x741f].
      Non-prefetchable 32 bit memory at 0xe4000000 [0xe40fffff].

The card in question is the "public/internet" side of the firewall.
There are two additional interfaces, eth0 (private ethernet) and eth2,
a radio LAN.

Thanks,

Jens Petersohn
-- 
      Apple OS X Public Beta is not intended for use in the operation of
      nuclear facilities, aircraft navigation or communication systems,
      air traffic control systems, life support machines or other equipment
      in which the failure of the Apple Software could lead to death,
      personal injury, or severe physical or environmental damage.


             reply	other threads:[~2001-09-25 17:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-25 17:42 Jens Petersohn [this message]
2001-09-25 22:05 ` protocol is buggy? Arnaldo Carvalho de Melo

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=XFMail.20010925124235.jkp@sgi.com \
    --to=jkp@sgi.com \
    --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