All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John Z. Bohach" <jzb@aexorsyst.com>
To: "PaNiC" <panic@klippanlan.net>, <linux-kernel@vger.kernel.org>
Subject: Re: Problem: NIC transmit timeouts
Date: Mon, 6 Mar 2006 09:33:57 -0800	[thread overview]
Message-ID: <200603060933.57036.jzb@aexorsyst.com> (raw)
In-Reply-To: <001501c64119$6d8e7bc0$072011ac@majestix>

On Monday 06 March 2006 04:28, PaNiC wrote:
> 1. The problem is that the outbound interface in a Sun Enterprise 250
> running maquerade gets transmit timeouts frequently.
>
> 2. I get the error "NETDEV WATCHDOG: eth0: transmit timed out" and a
> couple of seconds later the     interface jumps back up again. This

I can't say what the cause of your particular NETDEV WATCHDOG timeout may
be, but I had the same problem, and I root-caused it to the host bus <--> PCI bridge
configuration.  In particular, the multi-transaction timeout register in the bridge
wasn't programmed, and heavy PCI traffic would cause aborts.  Also, the
ICH configuration register had to be programmed according to the manufacturer's
recommendations.

This was on Intel h/w, and the registers to which I refer are
proprietary, so its a bit difficult to know what values to program where,
but it might give you a place to start.  On the other hand, some people have
reported issues with their device driver causing some timeouts, but your symptoms
seem to more closely resemble what I was seeing than those folks who had
s/w issues.

Regards,
John


  reply	other threads:[~2006-03-06 17:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-06 12:28 Problem: NIC transmit timeouts PaNiC
2006-03-06 17:33 ` John Z. Bohach [this message]
2006-03-07 12:08   ` PaNiC
2006-03-07 16:48     ` John Z. Bohach

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=200603060933.57036.jzb@aexorsyst.com \
    --to=jzb@aexorsyst.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=panic@klippanlan.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.