Re: cubietruck boot panic

[Robert Swindells <rjs%fdy2.co.uk@localhost>]

Matt Thomas wrote:
>On Jun 28, 2014, at 10:59 AM, Robert Swindells <rjs%fdy2.co.uk@localhost> 
>wrote:
>
>> 
>> Matt Thomas wrote:
>>> On Jun 28, 2014, at 10:34 AM, Robert Swindells <rjs%fdy2.co.uk@localhost> 
>>> wrote:
>>> 
>>>> 
>>>> Martin Husemann wrote:
>>>>> On Sat, Jun 07, 2014 at 04:43:16PM +0100, Robert Swindells wrote:
>>>>>> 
>>>>>> I'm getting a panic in arm32_kernel_vm_init() on a cubietruck with a
>>>>>> current kernel loaded using u-boot.
>>>>> 
>>>>> FWIW, a big endian kernel of -current as of a few hours ago and no verbose
>>>>> arm init just worked fine for me.
>>>> 
>>>> It still panics in the same place for me without verbose init arm or
>>>> built big endian.
>>>> 
>>>> How are you loading it ?
>>>> 
>>>> The panic looks correct to me. My reading of the source is that this
>>>> is due to __HAVE_MM_MD_DIRECT_MAPPED_PHYS being defined, it doesn't
>>>> compile without this though.
>>> 
>>> That's fine.  There's code to deal with that.
>> 
>> So why doesn't it work ?
>
>Sure it's a cubie truck and not a cubie baord 2? 

Yes, it is a cubietruck, it has 2GB of RAM.

The panic is from when the kernel is being mapped and it has done all
the 1M sections and is switching to smaller chunks for what is left.
Should it be doing this if all RAM is already mapped ?

I'm building with tools from 5 June, do I need the binutils changes
you made a couple of days ago ?