From: Stephen Frost <sfrost@snowman.net>
To: Ion Badulescu <ionut@cs.columbia.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Starfire issues
Date: Sat, 14 Jul 2001 18:16:07 -0400 [thread overview]
Message-ID: <20010714181607.O11136@ns> (raw)
[-- Attachment #1: Type: text/plain, Size: 1493 bytes --]
Hello,
I've been having some trouble with a starfire I have in that it seems
to drop packets every once in a while for a little bit and then start
up again. Also getting strange kernel messages:
----
eth2: Increasing Tx FIFO threshold to 320 bytes
eth2: Something Wicked happened! 2049001.
eth2: Increasing Tx FIFO threshold to 336 bytes
eth2: Something Wicked happened! 2049001.
eth2: Increasing Tx FIFO threshold to 352 bytes
eth2: Something Wicked happened! 2048101.
eth2: Increasing Tx FIFO threshold to 368 bytes
eth2: Something Wicked happened! 2049001.
eth2: Increasing Tx FIFO threshold to 384 bytes
eth2: Something Wicked happened! 2049001.
eth2: Increasing Tx FIFO threshold to 400 bytes
eth2: Something Wicked happened! 2049001.
eth2: Increasing Tx FIFO threshold to 416 bytes
eth2: Something Wicked happened! 2049001.
eth2: Increasing Tx FIFO threshold to 432 bytes
eth2: Something Wicked happened! 2048101.
eth2: Increasing Tx FIFO threshold to 448 bytes
eth2: Something Wicked happened! 2049001.
eth2: Increasing Tx FIFO threshold to 464 bytes
eth2: Something Wicked happened! 2049001.
eth2: Increasing Tx FIFO threshold to 480 bytes
eth2: Something Wicked happened! 2049001.
eth2: Increasing Tx FIFO threshold to 496 bytes
eth2: Something Wicked happened! 2049001.
----
This happens on other interfaces, not just this one. The kernel being
used is stock 2.4.6-ac2. Would the patches you've posted to lkml help?
If so I can give them a shot...
Thanks!
Stephen
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next reply other threads:[~2001-07-14 22:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-14 22:16 Stephen Frost [this message]
2001-07-14 22:44 ` Ion Badulescu
2001-07-15 3:51 ` Ion Badulescu
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=20010714181607.O11136@ns \
--to=sfrost@snowman.net \
--cc=ionut@cs.columbia.edu \
--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®