netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Matt Carlson <mcarlson@broadcom.com>
Cc: Roger Heflin <rogerheflin@gmail.com>,
	Peter Zijlstra <peterz@infradead.org>,
	LKML <linux-kernel@vger.kernel.org>,
	netdev <netdev@vger.kernel.org>
Subject: Re: WARNING: at net/sched/sch_generic.c:219 dev_watchdog+0xfe/0x17e() with tg3 network
Date: Tue, 25 Nov 2008 06:31:28 +0100	[thread overview]
Message-ID: <20081125053128.GA32426@1wt.eu> (raw)
In-Reply-To: <20081125015223.GA9151@xw6200.broadcom.net>

On Mon, Nov 24, 2008 at 05:52:23PM -0800, Matt Carlson wrote:
(...)
> > tg3: eth0: transmit timed out, resetting
> > tg3: DEBUG: MAC_TX_STATUS[0000000b] MAC_RX_STATUS[00000006]
> > tg3: DEBUG: RDMAC_STATUS[00000000] WDMAC_STATUS[00000008]
> > tg3: tg3_stop_block timed out, ofs=1400 enable_bit=2
> > tg3: tg3_stop_block timed out, ofs=c00 enable_bit=2
> > tg3: tg3_stop_block timed out, ofs=4c00 enable_bit=2
> > tg3: eth0: Link is down.
> > tg3: eth0: Link is up at 100 Mbps, full duplex.
> > tg3: eth0: Flow control is on for TX and on for RX.
> > 
> > The ease with which I reproduce it here clearly indicates that this is
> > related to the switch, probably just the fact that it is at 100 Mbps.
> > Unfortunately this evening I must go, but I still have one 100 Mbps
> > switch somewhere at home, I'll reproduce the same test ASAP in order
> > to bisect the issue.
> > 
> > Regards,
> > Willy
> 
> Does turning off flow control help at all?

I have not tested but I will. I hope to be able to trigger the problem
on other similar switches, because I'm only once a week connected to
the culprit...

Regards,
Willy


  reply	other threads:[~2008-11-25  5:31 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <491954E1.2050002@gmail.com>
2008-11-11 11:31 ` WARNING: at net/sched/sch_generic.c:219 dev_watchdog+0xfe/0x17e() with tg3 network Peter Zijlstra
2008-11-15  4:01   ` Roger Heflin
2008-11-18  6:50     ` Willy Tarreau
2008-11-20  3:11       ` Matt Carlson
2008-11-20  5:37         ` Willy Tarreau
2008-11-20 18:43           ` Matt Carlson
2008-11-20 21:26             ` Willy Tarreau
2008-11-20 21:53               ` Matt Carlson
2008-11-21 17:55                 ` Willy Tarreau
2008-11-24 13:27                 ` Willy Tarreau
2008-11-24 21:52                   ` Willy Tarreau
2008-11-25  1:52                     ` Matt Carlson
2008-11-25  5:31                       ` Willy Tarreau [this message]
2008-11-25 17:54                         ` Matt Carlson
2008-11-26 21:12                           ` Willy Tarreau
2008-11-26 22:54                             ` Matt Carlson
2008-11-27  5:16                               ` Willy Tarreau
2008-11-27 10:06                                 ` Frantisek Hanzlik
2008-11-27 20:33                                   ` Willy Tarreau
2008-12-02 22:55                               ` Willy Tarreau
2008-11-20  3:00     ` Matt Carlson
2008-11-20 10:07       ` Roger Heflin
2008-11-20 17:11         ` Matt Carlson
2008-11-21  9:34           ` Roger Heflin

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=20081125053128.GA32426@1wt.eu \
    --to=w@1wt.eu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcarlson@broadcom.com \
    --cc=netdev@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=rogerheflin@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).