public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <mbligh@aracnet.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Wierd error messages from starfire driver
Date: Mon, 04 Nov 2002 15:54:29 -0800	[thread overview]
Message-ID: <1040010000.1036454069@flay> (raw)

I've been getting these for ever, and they don't seem to
do any harm ... but they're rather worrying, and I'm curious
as to whath they are.

I suspect the "Increasing Tx FIFO threshold" is just being
unnecessarily verbose ... but the "Something Wicked happened!"
error doesn't look too happy ... any clues as to what this is?

Thanks,

Martin.

Increasing Tx FIFO threshold to 80 bytes
eth0: Increasing Tx FIFO threshold to 96 bytes
eth0: Something Wicked happened! 2049101.
eth0: Increasing Tx FIFO threshold to 112 bytes
eth0: Increasing Tx FIFO threshold to 128 bytes
eth0: Something Wicked happened! 204b101.
eth0: Increasing Tx FIFO threshold to 144 bytes
eth0: Increasing Tx FIFO threshold to 160 bytes
eth0: Something Wicked happened! 2049001.
eth0: Increasing Tx FIFO threshold to 176 bytes
eth0: Increasing Tx FIFO threshold to 192 bytes
eth0: Increasing Tx FIFO threshold to 208 bytes
eth0: Something Wicked happened! 2049101.
eth0: Increasing Tx FIFO threshold to 224 bytes
eth0: Increasing Tx FIFO threshold to 240 bytes
eth0: Something Wicked happened! 2049101.
eth0: Increasing Tx FIFO threshold to 256 bytes
eth0: Increasing Tx FIFO threshold to 272 bytes
eth0: Something Wicked happened! 2049101.
eth0: Increasing Tx FIFO threshold to 288 bytes
eth0: Increasing Tx FIFO threshold to 304 bytes
eth0: Something Wicked happened! 2049101.
eth0: Increasing Tx FIFO threshold to 320 bytes
eth0: Increasing Tx FIFO threshold to 336 bytes
eth0: Increasing Tx FIFO threshold to 352 bytes
eth0: Something Wicked happened! 2049101.
eth0: Increasing Tx FIFO threshold to 368 bytes
eth0: Increasing Tx FIFO threshold to 384 bytes
eth0: Increasing Tx FIFO threshold to 400 bytes
eth0: Something Wicked happened! 2049101.
eth0: Increasing Tx FIFO threshold to 416 bytes
eth0: Increasing Tx FIFO threshold to 432 bytes
eth0: Increasing Tx FIFO threshold to 448 bytes
eth0: Increasing Tx FIFO threshold to 464 bytes
eth0: Something Wicked happened! 2049101.
eth0: Increasing Tx FIFO threshold to 480 bytes
eth0: Increasing Tx FIFO threshold to 496 bytes


                 reply	other threads:[~2002-11-04 23:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1040010000.1036454069@flay \
    --to=mbligh@aracnet.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