From: Anton Vorontsov <avorontsov@ru.mvista.com>
To: Martyn Welch <martyn.welch@ge.com>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Sandeep Gopalpet <Sandeep.Kumar@freescale.com>,
davem@davemloft.net
Subject: Re: Gianfar driver failing on MPC8641D based board
Date: Fri, 26 Feb 2010 17:35:32 +0300 [thread overview]
Message-ID: <20100226143532.GA31622@oksana.dev.rtsoft.ru> (raw)
In-Reply-To: <4B87B937.6010204@ge.com>
On Fri, Feb 26, 2010 at 12:06:15PM +0000, Martyn Welch wrote:
> Anton Vorontsov wrote:
> > On Thu, Feb 25, 2010 at 07:53:30PM -0500, Paul Gortmaker wrote:
> > [...]
> >
> >> I was able to reproduce it on an 8641D and bisected it down to this:
> >>
> >> -----------
> >> commit a3bc1f11e9b867a4f49505ecac486a33af248b2e
> >> Author: Anton Vorontsov <avorontsov@ru.mvista.com>
> >> Date: Tue Nov 10 14:11:10 2009 +0000
> >>
> >> gianfar: Revive SKB recycling
> >>
> >
> > Thanks for the bisect. I have a guess why tx hangs in
> > SMP case. Could anyone try the patch down below?
> >
>
> Yup, no problem. I'm afraid it doesn't resolve the problem for me.
Hm.. I found a p2020 board and I was able to reproduce the issue.
The patch down below fixed it completely for me... hm.
I'll look further, thanks!
> > [...]
> >
> >> ...which probably explains why you weren't seeing it on non-SMP.
> >> I'd imagine it would show up on any of the e500mc boards too.
> >>
> >
> > Yeah.. Pity, I don't have SMP boards anymore. I'll try
> > to get one though.
> >
> >
> > diff --git a/drivers/net/gianfar.c b/drivers/net/gianfar.c
> > index 8bd3c9f..3ff3bd0 100644
> > --- a/drivers/net/gianfar.c
> > +++ b/drivers/net/gianfar.c
> > @@ -2614,6 +2614,8 @@ static int gfar_poll(struct napi_struct *napi, int budget)
> > tx_queue = priv->tx_queue[rx_queue->qindex];
> >
> > tx_cleaned += gfar_clean_tx_ring(tx_queue);
> > + if (!tx_cleaned && !tx_queue->num_txbdfree)
> > + tx_cleaned += 1; /* don't complete napi */
> > rx_cleaned_per_queue = gfar_clean_rx_ring(rx_queue,
> > budget_per_queue);
> > rx_cleaned += rx_cleaned_per_queue;
> >
--
Anton Vorontsov
email: cbouatmailru@gmail.com
irc://irc.freenode.net/bd2
next prev parent reply other threads:[~2010-02-26 14:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-05 14:00 Gianfar driver failing on MPC8641D based board Martyn Welch
2010-02-25 10:31 ` Martyn Welch
2010-02-25 16:46 ` Martyn Welch
2010-02-25 16:51 ` Anton Vorontsov
2010-02-25 17:49 ` Anton Vorontsov
2010-02-26 0:53 ` Paul Gortmaker
2010-02-26 3:14 ` Anton Vorontsov
2010-02-26 4:58 ` Kumar Gopalpet-B05799
2010-02-26 12:06 ` Martyn Welch
2010-02-26 14:35 ` Anton Vorontsov [this message]
2010-02-26 14:52 ` Paul Gortmaker
2010-02-26 15:18 ` Martyn Welch
2010-02-26 15:34 ` Martyn Welch
2010-02-26 16:10 ` Anton Vorontsov
2010-02-26 16:27 ` Paul Gortmaker
2010-02-26 21:38 ` Anton Vorontsov
2010-02-26 22:12 ` Paul Gortmaker
2010-02-27 5:35 ` Kumar Gopalpet-B05799
2010-03-02 14:02 ` Anton Vorontsov
2010-03-01 13:07 ` Martyn Welch
2010-02-26 11:51 ` Martyn Welch
2010-02-25 18:27 ` Kumar Gala
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=20100226143532.GA31622@oksana.dev.rtsoft.ru \
--to=avorontsov@ru.mvista.com \
--cc=Sandeep.Kumar@freescale.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=martyn.welch@ge.com \
--cc=netdev@vger.kernel.org \
--cc=paul.gortmaker@windriver.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).