From: Jeff Garzik <jgarzik@pobox.com>
To: jmerkey <jmerkey@utah-nac.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.9 Adaptec 4 Port Starfire Sickness
Date: Sun, 03 Apr 2005 03:26:32 -0400 [thread overview]
Message-ID: <424F9AA8.3020401@pobox.com> (raw)
In-Reply-To: <424F73F8.8020108@utah-nac.org>
jmerkey wrote:
> With linux 2.6.9 running at 192 MB/S network loading and protocol
> splitting drivers routing packets out of
> a 2.6.9 device at full 100 mb/s (12.5 MB/S) simultaneously over 4 ports,
> the adaptec starfire driver goes into
> constant Tx FIFO reconfiguration mode and after 3-4 days of constantly
> resetting the Tx FIFO window and
> generating a deluge of messages such as:
>
> ethX: PCI bus congestion, resetting Tx FIFO window to X bytes
>
> pouring into the system log file at a rate of a dozen per minute. After
> several days, the PCI bus totally locks up
> and hangs the system. Need a config option to allow the starfire to
> disable this feature. At very
> high bus loading rates, the starfire card will completely lock the bus
> after 3-4 days
> of constant Tx FIFO reconfiguration at very high data rates with
> protocol splitting and routing.
The feature doesn't need disabling; just modify the driver to stop the
flapping.
Jeff
next prev parent reply other threads:[~2005-04-03 7:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-03 4:41 Linux 2.6.9 Adaptec 4 Port Starfire Sickness jmerkey
2005-04-03 5:47 ` Willy Tarreau
2005-04-03 6:58 ` jmerkey
2005-04-03 7:38 ` Willy Tarreau
2005-04-03 7:21 ` jmerkey
2005-04-03 7:26 ` Jeff Garzik [this message]
2005-04-03 7:07 ` jmerkey
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=424F9AA8.3020401@pobox.com \
--to=jgarzik@pobox.com \
--cc=jmerkey@utah-nac.org \
--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