Bug#820167: syslinux-efi: Kernel does not boot on Gigabyte MP30-AR0 system (APM X-Gene 1)

[Ronald Maas <ronaldjmaas@gmail.com>]

Most distributions based on kernel 4.X are able to boot successfully,
including Debian Testing and Linaro Debian 16.03

But Debian 8.0.4 is the latest release version - so would be nice to
have it working too

On Mon, May 23, 2016 at 10:29 AM, Geert Stappers <stappers@stappers.nl> wrote:
> severity -1 normal
> stop
>
> On Mon, May 23, 2016 at 07:44:22AM -0700, Ronald Maas wrote:
>>
>> EFI stub: Booting Linux Kernel...
>
> [0]
>
>
>> L3c Cache: 8MB
>> [    0.000000] Initializing cgroup subsys cpuset
>> [    0.000000] Initializing cgroup subsys cpu
>> [    0.000000] Initializing cgroup subsys cpuacct
>> [    0.000000] Linux version 3.16.0-4-arm64 (debian-kernel@lists.debian.org) (gcc version 4.8.4 (Debian/Linaro  4.8.4-1) ) #1 SMP Debian 3.16.7-ckt25-1 (2016-03-06)
>> [    0.000000] CPU: AArch64 Processor [500f0001] revision 1
>> [    0.000000] Early serial console at MMIO32 0x1c020000 (options '')
>> [    0.000000] bootconsole [uart0] enabled
>> [    0.000000] Unable to handle kernel paging request at virtual address 3fffe2e000
>
> I think that is the problem.
>
>
>> [    0.000000] pgd = ffffffc00007d000
>> [    0.000000] [3fffe2e000] *pgd=000000008007f003, *pmd=0000000000000000
>> [    0.000000] Internal error: Oops: 96000045 [#1] SMP
>
> That 'Oops' might be a symptom.
>
>
> Where this is an interresting problem, it is no syslinux nor a d-i problem. IMHO.
>
> Most likely is this BR about a mismatch between bootloader in (Flash)ROM and kernel.
>
>
> Knowing the bootloader is recently installed ( "flashed" )
> is it wise to use a newer kernel. So no 3.X, but 4.X.
>
> Hope this helps.
>
>
> Groeten
> Geert Stappers
>
> Footnotes
> [0] an "EFI stub", unlikely syslinux-efi, which is not for arm64 ...
>     see https://packages.debian.org/sid/all/syslinux-efi/filelist for file list
>
> --
> Leven en laten leven