[Arm-dev] kernel 4.11.0-22.el7.2.aarch64 does not boot on ThunderX

[Itaru Kitayama]

Vadim,

At this moment, I don't need to try to this specific latest CentOS kernel as I said
in previous replied to Jim, v4.13 boots on the HW, but thanks for your suggestion.
I've been booting up the HW with slightly at different address like below:

earlycon=pl011,0x87e025000000

this give me lots of boot messages.

Itaru

On 2017/10/11 23:28, Vadim Lomovtsev wrote:
> Hi Itaru,
> 
> On Tue, Oct 10, 2017 at 05:30:39PM +0900, Itaru Kitayama wrote:
>> Hi,
>>
>> In our attempt upgrading from 4.5.0-25.el7.aarch64 to the 4.11-based kernel
>> we see the latter does not boot on ThunderX.
>>
>> Here's the HW details:
>>
>> http://b2b.gigabyte.com/ARM-Server/R150-T62-rev-100#support-manual
>>
>> The BIOS release is T43. (According Red Hat, they've been testing fine their
>> 1 socket GIGABYTE server with their RHEL 7 kernels.)
>>
>> I am wondering what ThunderX platform CentOS has been using for testing, and
>> the list happens to have the above HW.
>>
>> The boot process seems to be stuck as soon as system prints our EFI stub messages.
>> No messages from the kernel.
> 
> Could you please try to run kernel with earlycon option?
> Append kernel command line with something like "earlycon=pl011,0x87e024000000"
> and check kernel output.
> This could give us some hint of what is going on there.
> 
> WBR,
> Vadim
> 
>>
>> Is the CentOS Alt architecture group going to release a 4.12 or .13 kernel soon?
>>
>> Itaru
>> _______________________________________________
>> Arm-dev mailing list
>> Arm-dev at centos.org
>> https://lists.centos.org/mailman/listinfo/arm-dev
> _______________________________________________
> Arm-dev mailing list
> Arm-dev at centos.org
> https://lists.centos.org/mailman/listinfo/arm-dev
>