public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian Macy <bmacy@macykids.net>
To: linux-kernel@vger.kernel.org
Subject: 2.6.0 and Starfire NIC
Date: Tue, 30 Dec 2003 08:48:13 -0800	[thread overview]
Message-ID: <3FF1AC4D.9040002@macykids.net> (raw)

When switching to 2.6.0 my Starfire NIC fails to function with an 
entertaining message:
Dec 23 16:36:45 job kernel: eth0: Something Wicked happened! 0x02018101.
Dec 23 16:36:45 job kernel: eth0: Something Wicked happened! 0x02010001.

I don't know if this is related but in 2.4 I get PCI bus congestion for 
the starfire adapter:
eth0: PCI bus congestion, increasing Tx FIFO threshold to 80 bytes
eth0: PCI bus congestion, increasing Tx FIFO threshold to 96 bytes
eth0: PCI bus congestion, increasing Tx FIFO threshold to 112 bytes
eth0: PCI bus congestion, increasing Tx FIFO threshold to 128 bytes
eth0: PCI bus congestion, increasing Tx FIFO threshold to 144 bytes
eth0: PCI bus congestion, increasing Tx FIFO threshold to 160 bytes


Brian Macy


             reply	other threads:[~2003-12-30 16:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-30 16:48 Brian Macy [this message]
2003-12-30 16:52 ` 2.6.0 and Starfire NIC William Lee Irwin III
2004-01-05 20:44 ` Ion Badulescu
2004-01-05 21:17   ` Brian Macy

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=3FF1AC4D.9040002@macykids.net \
    --to=bmacy@macykids.net \
    --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