From: Martyn Welch <martyn.welch@gefanuc.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: Booting 2.6.29-rc3 on mpc8661d_hpcn failing
Date: Mon, 02 Feb 2009 16:20:14 +0000 [thread overview]
Message-ID: <49871D3E.80809@gefanuc.com> (raw)
In-Reply-To: <D06DAB0F-1477-4CA6-A06D-0F7B62939C86@kernel.crashing.org>
Kumar Gala wrote:
>
> On Feb 2, 2009, at 10:00 AM, Martyn Welch wrote:
>
>> Kumar Gala wrote:
>>> On Feb 2, 2009, at 3:36 AM, Martyn Welch wrote:
>>>> Becky Bruce wrote:
>>>>> On Jan 30, 2009, at 8:42 AM, Kumar Gala wrote:
>>>>>>
>>>>>> On Jan 30, 2009, at 6:31 AM, Martyn Welch wrote:
>>>>>>
>>>>>>> Hi Guys,
>>>>>>>
>>>>>>> It seems that 2.6.29-rc3 is not booting on the MPC8641 HPCN. I
>>>>>>> have just updated u-boot to the latest git to see if that
>>>>>>> improved matters, however I get stuck at the following. Any ideas?
>>>>>>
>>>>>> did you update your .dtb as well?
>>>>
>>>> Yup, just double checked it. SOC mapped at ffe00000. If I use the
>>>> wrong DTB I don't get any serial output...
>>>>
>>>>> We've changed the memory map for that board in the latest u-boot,
>>>>> which is why you need a new .dtb. If this still failing, let me
>>>>> know, and I'll give it a try on my board and see what's up since
>>>>> this is probably my fault :)
>>>>
>>>> It appears the same problem is affecting our sbc610 as well, the
>>>> location of the SOC hasn't changed on that board.
>>>>
>>>> Martyn
>>> Hm.. maybe try a git-bisect between 2.6.28 and 2.6.29-rc3?
>>
>> That's was today's "little" task. I was just in the process of writing
>> an email :-)
>>
>> It got me to the following commit:
>>
>> commit 64b3d0e8122b422e879b23d42f9e0e8efbbf9744
>> Author: Benjamin Herrenschmidt <benh@kernel.crashing.org>
>>
>> powerpc/mm: Rework usage of _PAGE_COHERENT/NO_CACHE/GUARDED
>>
>> I tried reverting it, but as I had kinda thought, that really didn't
>> help.
>>
>> I'm just recompiling to check that I didn't screw-up during the
>> bisection.
>
Nope, didn't screw-up...
> Hmm.
>
> take a look at this thread.
>
> http://ozlabs.org/pipermail/linuxppc-dev/2009-January/067437.html
>
...and that confirms that this issue has well and truly left this newbies comfort zone ;-)
Martyn
--
Martyn Welch MEng MPhil MIET (Principal Software Engineer) T:+44(0)1327322748
GE Fanuc Intelligent Platforms Ltd, |Registered in England and Wales
Tove Valley Business Park, Towcester, |(3828642) at 100 Barbirolli Square,
Northants, NN12 6PF, UK T:+44(0)1327359444 |Manchester,M2 3AB VAT:GB 729849476
next prev parent reply other threads:[~2009-02-02 16:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-30 12:31 Booting 2.6.29-rc3 on mpc8661d_hpcn failing Martyn Welch
2009-01-30 13:17 ` Martyn Welch
2009-01-30 14:42 ` Kumar Gala
2009-01-30 16:47 ` Becky Bruce
2009-02-02 9:36 ` Martyn Welch
2009-02-02 15:45 ` Kumar Gala
2009-02-02 16:00 ` Martyn Welch
2009-02-02 16:11 ` Kumar Gala
2009-02-02 16:20 ` Martyn Welch [this message]
2009-02-02 20:49 ` Benjamin Herrenschmidt
2009-02-03 12:22 ` Martyn Welch
2009-02-03 15:50 ` Martyn Welch
2009-02-04 0:47 ` Benjamin Herrenschmidt
2009-02-04 12:22 ` Martyn Welch
2009-02-10 15:40 ` Kumar Gala
2009-02-10 20:58 ` 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=49871D3E.80809@gefanuc.com \
--to=martyn.welch@gefanuc.com \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.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.