public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Andrew Morton <akpm@digeo.com>
Cc: Matt Rickard <mjr318@psu.edu>, linux-kernel@vger.kernel.org
Subject: Re: Oops with 3c59x module (3com 3c595 NIC)
Date: Sat, 07 Dec 2002 18:16:33 -0500	[thread overview]
Message-ID: <3DF28151.40706@pobox.com> (raw)
In-Reply-To: <3DF2738A.2447599@digeo.com>

Andrew Morton wrote:
> That's a transmit underrun - data is not being fed into the NIC
> across the PCI bus fast enough.  Possibly something has gone
> wrong with the busmastering logic on the mainboard, or the NIC.
> 
> The driver will reset the transmitter when this happens, as per the
> manual.  There's not much else we can do.


pci-skeleton.c and several of Don's drivers actually do do something 
else on TxUnderrun, twiddle DMA burst settings:

         if ((intr_status & TxUnderrun)
                 && (np->tx_config & TxThresholdField) != 
TxThresholdField) {
                 long ioaddr = dev->base_addr;
                 np->tx_config += TxThresholdInc;
                 writel(np->tx_config, ioaddr + TxMode);
                 np->stats.tx_fifo_errors++;
         }

I wonder how feasible it is to do that on 3c59x hardware?


  reply	other threads:[~2002-12-07 23:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-07 21:43 Oops with 3c59x module (3com 3c595 NIC) Matt Rickard
2002-12-07 22:17 ` Andrew Morton
2002-12-07 23:16   ` Jeff Garzik [this message]
2002-12-07 23:46     ` Andrew Morton
2002-12-08 12:30     ` Henning P. Schmiedehausen
2002-12-08 19:49       ` Jeff Garzik
2002-12-08 19:13 ` Matt Rickard

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=3DF28151.40706@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjr318@psu.edu \
    /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