All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martyn Welch <martyn.welch@ge.com>
To: avorontsov@ru.mvista.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	linuxppc-dev list <linuxppc-dev@ozlabs.org>,
	Sandeep Gopalpet <Sandeep.Kumar@freescale.com>,
	davem@davemloft.net
Subject: Re: Gianfar driver failing on MPC8641D based board
Date: Fri, 26 Feb 2010 11:51:00 +0000	[thread overview]
Message-ID: <4B87B5A4.2010106@ge.com> (raw)
In-Reply-To: <20100225165141.GA9686@oksana.dev.rtsoft.ru>

Anton Vorontsov wrote:
> On Thu, Feb 25, 2010 at 04:46:54PM +0000, Martyn Welch wrote:
> [...]
>   
>>> nfs: server 192.168.0.1 not responding, still trying
>>>   
>>>       
>> Further testing has shown that this isn't restricted to warm reboots, it
>> happens from cold as well. In addition, the exact timing of the failure
>> seems to vary, some boots have got further before failing.
>>     
>
> Unfortunately I don't have any 8641 boards near me, so I can't
> debug this myself. Though, I tested gianfar on MPC8568E-MDS with
> 2.6.33 kernel, and it seems to work just fine.
>
> I see you use SMP. Can you try to turn it off? If that will fix
> the issue, then it'll be a good data point.
>
> Meanwhile, I'll try SMP kernel on MPC8568 (UP), and let you
> know the results.
>
> Thanks

I removed the second core from the dts file rather than truly disabling
SMP in the kernel config. Doing this allowed the board to boot reliably.

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

WARNING: multiple messages have this Message-ID (diff)
From: Martyn Welch <martyn.welch@ge.com>
To: avorontsov@ru.mvista.com
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	Sandeep Gopalpet <Sandeep.Kumar@freescale.com>,
	davem@davemloft.net, Kumar Gala <galak@kernel.crashing.org>
Subject: Re: Gianfar driver failing on MPC8641D based board
Date: Fri, 26 Feb 2010 11:51:00 +0000	[thread overview]
Message-ID: <4B87B5A4.2010106@ge.com> (raw)
In-Reply-To: <20100225165141.GA9686@oksana.dev.rtsoft.ru>

Anton Vorontsov wrote:
> On Thu, Feb 25, 2010 at 04:46:54PM +0000, Martyn Welch wrote:
> [...]
>   
>>> nfs: server 192.168.0.1 not responding, still trying
>>>   
>>>       
>> Further testing has shown that this isn't restricted to warm reboots, it
>> happens from cold as well. In addition, the exact timing of the failure
>> seems to vary, some boots have got further before failing.
>>     
>
> Unfortunately I don't have any 8641 boards near me, so I can't
> debug this myself. Though, I tested gianfar on MPC8568E-MDS with
> 2.6.33 kernel, and it seems to work just fine.
>
> I see you use SMP. Can you try to turn it off? If that will fix
> the issue, then it'll be a good data point.
>
> Meanwhile, I'll try SMP kernel on MPC8568 (UP), and let you
> know the results.
>
> Thanks

I removed the second core from the dts file rather than truly disabling
SMP in the kernel config. Doing this allowed the board to boot reliably.

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


  parent reply	other threads:[~2010-02-26 11:50 UTC|newest]

Thread overview: 40+ 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:46     ` Martyn Welch
2010-02-25 16:51     ` Anton Vorontsov
2010-02-25 16:51       ` Anton Vorontsov
2010-02-25 17:49       ` Anton Vorontsov
2010-02-25 17:49         ` Anton Vorontsov
2010-02-26  0:53         ` Paul Gortmaker
2010-02-26  0:53           ` Paul Gortmaker
2010-02-26  3:14           ` Anton Vorontsov
2010-02-26  3:14             ` Anton Vorontsov
2010-02-26  4:58             ` Kumar Gopalpet-B05799
2010-02-26  4:58               ` Kumar Gopalpet-B05799
2010-02-26 12:06             ` Martyn Welch
2010-02-26 12:06               ` Martyn Welch
2010-02-26 14:35               ` Anton Vorontsov
2010-02-26 14:35                 ` Anton Vorontsov
2010-02-26 14:52                 ` Paul Gortmaker
2010-02-26 14:52                   ` Paul Gortmaker
2010-02-26 15:18                   ` Martyn Welch
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 16:27                           ` Paul Gortmaker
2010-02-26 21:38                           ` Anton Vorontsov
2010-02-26 21:38                             ` Anton Vorontsov
2010-02-26 22:12                             ` Paul Gortmaker
2010-02-26 22:12                               ` Paul Gortmaker
2010-02-27  5:35                             ` Kumar Gopalpet-B05799
2010-02-27  5:35                               ` Kumar Gopalpet-B05799
2010-03-02 14:02                               ` Anton Vorontsov
2010-03-02 14:02                                 ` Anton Vorontsov
2010-03-01 13:07                             ` Martyn Welch
2010-03-01 13:07                               ` Martyn Welch
2010-02-26 11:51       ` Martyn Welch [this message]
2010-02-26 11:51         ` Martyn Welch
2010-02-25 18:27     ` Kumar Gala
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=4B87B5A4.2010106@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 \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.