public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Tino Keitel <tino.keitel@tikei.de>
Cc: netdev@vger.kernel.org
Subject: Re: BQL support in gianfar causes network hickup
Date: Sat, 24 Nov 2012 15:43:36 -0800	[thread overview]
Message-ID: <1353800616.2590.4562.camel@edumazet-glaptop> (raw)
In-Reply-To: <loom.20121124T213422-650@post.gmane.org>

On Sat, 2012-11-24 at 20:42 +0000, Tino Keitel wrote:
> Paul Gortmaker <paul.gortmaker <at> windriver.com> writes:
> 
> > 
> > On 12-11-23 10:58 AM, Keitel, Tino (ALC NetworX GmbH) wrote:
> > > Hi,
> > > 
> > > commit d8a0f1b0af67679bba886784de10d8c21acc4e0e causes the following
> > > trace on a Freescale RDB8313 board:
> > 
> > Thanks for the report.
> > 
> > > 
> > > NETDEV WATCHDOG: eth1 (fsl-gianfar): transmit queue 0 timed out
> > > ------------[ cut here ]------------
> > > WARNING:
> > > at /home/keitelt1/src/git/linux-stable/net/sched/sch_generic.c:255
> > > Modules linked in:
> > > NIP: c02448b0 LR: c02448b0 CTR: c01c19b8
> > > REGS: c7ffbe40 TRAP: 0700   Not tainted  (3.7.0-rc6-rt18)
> >                                             ^^^^^^^^^^^^^^^
> > I almost overlooked the above.  It would have been nice to
> > see more explicit information on what kernel you are running.
> > I say that because the above concerns me.  For several reasons.
> > 
> > 1) it looks to be not mainline, but preempt_rt
> > 2) There is no RT on 3.7 yet, so I'm assuming this is a custom
> >    forward port of the 250 odd RT patches.  (The RT is 3.6.7-rt18,
> >    i.e. based on the 3.6 gregKH stable tree.)
> 
> Sorry for the confusion. This was a 3.7.0-rc6 tree, and I forgot git clean after
> trying the rt-patches and git reset --hard v3.7.0-rc6, so the localversion file
> for -rt was still present, and the kernel was named 3.7.0-rc6-rt18. If I got
> this right, this should be a normal kernel with just the version file modified.
> 
> I tried kernel 3.3, which doesnt have the issue. I tried 3.4, 3.6.7 and 3.7-rc6,
> which all show the kernel trace and ptp client misbehaviour. I tried 3.4, 3.6.7,
> 3.7-rc6 and 3.6.5-rt18 with the patch I posted, and they were ok.
> 
> The patch I posted is for 3.7-rc6.
> 

Hmm, I wonder if BQL makes a particular bug showing more often.

I see gianfar uses a very small watchdog_timeo of 1 second, while many
drivers use 5 seconds.

What happens if you change this to 5 seconds ?

diff --git a/drivers/net/ethernet/freescale/gianfar.c b/drivers/net/ethernet/freescale/gianfar.c
index 19ac096..3a994f9 100644
--- a/drivers/net/ethernet/freescale/gianfar.c
+++ b/drivers/net/ethernet/freescale/gianfar.c
@@ -101,7 +101,7 @@
 
 #include "gianfar.h"
 
-#define TX_TIMEOUT      (1*HZ)
+#define TX_TIMEOUT      (5*HZ)
 
 const char gfar_driver_version[] = "1.3";
 

  reply	other threads:[~2012-11-24 23:43 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-23 15:58 BQL support in gianfar causes network hickup Keitel, Tino (ALC NetworX GmbH)
2012-11-23 16:34 ` Paul Gortmaker
2012-11-23 19:42   ` Francois Romieu
2012-11-24 20:42   ` Tino Keitel
2012-11-24 23:43     ` Eric Dumazet [this message]
2012-11-26 10:01       ` Tino Keitel
2012-11-26 16:34         ` Eric Dumazet
2012-11-26 17:08           ` Keitel, Tino (ALC NetworX GmbH)
2012-11-26 17:17             ` Eric Dumazet
2012-11-27  9:36               ` Keitel, Tino (ALC NetworX GmbH)
2012-11-27 12:36                 ` Eric Dumazet
2012-11-27 12:42                   ` Keitel, Tino (ALC NetworX GmbH)
2012-11-27 13:32                     ` Eric Dumazet
2012-11-27 13:49                       ` Eric Dumazet
2013-02-05 13:00                       ` Keitel, Tino (ALC NetworX GmbH)
2013-02-06  1:55                         ` Paul Gortmaker
2013-02-06 15:20                           ` Keitel, Tino (ALC NetworX GmbH)
2013-04-29 13:14                             ` Claudiu Manoil
2013-04-29 13:20                               ` Tino Keitel
2013-05-27 12:47                                 ` Tino Keitel
2013-02-07 21:05                         ` Paul Gortmaker

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=1353800616.2590.4562.camel@edumazet-glaptop \
    --to=eric.dumazet@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=tino.keitel@tikei.de \
    /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