From: Martyn Welch <martyn.welch@ge.com>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linuxppc-dev list <linuxppc-dev@ozlabs.org>,
Sandeep Gopalpet <Sandeep.Kumar@freescale.com>,
avorontsov@ru.mvista.com, davem@davemloft.net
Subject: Re: Gianfar driver failing on MPC8641D based board
Date: Fri, 26 Feb 2010 15:34:07 +0000 [thread overview]
Message-ID: <4B87E9EF.3010604@ge.com> (raw)
In-Reply-To: <4B87E662.3080106@ge.com>
Martyn Welch wrote:
> Paul Gortmaker wrote:
>
>> On 10-02-26 09:35 AM, Anton Vorontsov wrote:
>>
>>
>>> 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.
>>>
>>>
>> Interesting. I just tested the patch on the sbc8641d, and it
>> still has the issue with your patch applied. I'm using NFSroot
>> just like Martyn was and it still appears bound up on that
>> gianfar tx lock. I'll see if I can get a SysRq backtrace in
>> case that will help you see how it manages to get there...
>>
>>
>
> I've got a p2020ds here as well, so I'll give NFSroot on that a try with
> your patch.
>
Out of 10 boot attempts, 7 failed.
Martyn
--
Martyn Welch (Principal Software Engineer) | Registered in England and
GE Intelligent Platforms | Wales (3828642) at 100
T +44(0)127322748 | Barbirolli Square, Manchester,
E martyn.welch@ge.com | M2 3AB VAT:GB 927559189
next prev parent reply other threads:[~2010-02-26 15:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4B6C2488.3060403@ge.com>
2010-02-25 10:31 ` Gianfar driver failing on MPC8641D based board 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
2010-02-26 14:52 ` Paul Gortmaker
2010-02-26 15:18 ` Martyn Welch
2010-02-26 15:34 ` Martyn Welch [this message]
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=4B87E9EF.3010604@ge.com \
--to=martyn.welch@ge.com \
--cc=Sandeep.Kumar@freescale.com \
--cc=avorontsov@ru.mvista.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--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