public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: "Keitel, Tino (ALC NetworX GmbH)" <Tino.Keitel@alcnetworx.de>
Cc: Tino Keitel <tino.keitel@tikei.de>,
	Paul Gortmaker <paul.gortmaker@windriver.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: BQL support in gianfar causes network hickup
Date: Tue, 27 Nov 2012 04:36:56 -0800	[thread overview]
Message-ID: <1354019816.7553.1585.camel@edumazet-glaptop> (raw)
In-Reply-To: <9AA65D849A88EB44B5D9B6A8BA098E23040A60D6EE70@Exchange1.lawo.de>

On Tue, 2012-11-27 at 10:36 +0100, Keitel, Tino (ALC NetworX GmbH)
wrote:
> On Mo, 2012-11-26 at 09:17 -0800, Eric Dumazet wrote:
> > On Mon, 2012-11-26 at 18:08 +0100, Keitel, Tino (ALC NetworX GmbH)
> > wrote:
> > > On Mo, 2012-11-26 at 08:34 -0800, Eric Dumazet wrote:
> > > > On Mon, 2012-11-26 at 11:01 +0100, Tino Keitel wrote:
> > > > > On Sat, Nov 24, 2012 at 15:43:36 -0800, Eric Dumazet wrote:
> > > > > 
> > > > > [...]
> > > > > 
> > > > > > 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 ?
> > > > > 
> > > > > I still got the trace and a failing ptp client.
> > > > > 
> > > > 
> > > > Thanks. Is this bug easy to trigger ?
> > > > 
> > > > I suspect a core issue and a race, likely to happen on your (non x86)
> > > > hardware
> > > > 
> > > > Could you add the following debugging patch ?
> > > 
> > > No visible difference:
> > 
> > OK it seems you trigger the problem fast !
> > 
> > Please try the following as well :
> 
> Hi,
> 
> yes, it can be triggered within 2 minutes.
> 
> The patch makes no difference:

Can you reproduce the problem using a single cpu ?

  reply	other threads:[~2012-11-27 12:36 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
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 [this message]
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=1354019816.7553.1585.camel@edumazet-glaptop \
    --to=eric.dumazet@gmail.com \
    --cc=Tino.Keitel@alcnetworx.de \
    --cc=netdev@vger.kernel.org \
    --cc=paul.gortmaker@windriver.com \
    --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