Native ram init panics linux kernel on samsung lumpy with CELERON 867 cpu.

[Persmule]

Hi all,

Recently I bought a second hand samsung lumpy
(https://www.chromium.org/chromium-os/developer-information-for-chrome-os-dev...)
with CELERON 867 cpu, and tried to build a coreboot image with seabios
in order to use this chromebook as an ordinary PC laptop running GNU/Linux.

It seems that native ram init works on lumpies with core i5 cpu, but on
mine, coreboot built with native ram init can run payloads with no
problem, but linux kernel will panic with outputs showed on the attached
photo (related to processors' synchronization?). Now I have to use Intel
FSP to perform ram init, on which linux
kernel (and GNU/Linux) works fine.

Config files for FSP and native ram init are also attached.

Best regards.

Persmule

[Kyösti Mälkki]

On Mon, Jan 16, 2017 at 12:04 PM, Persmule  wrote:
> Hi all,
>
> Recently I bought a second hand samsung lumpy
> (https://www.chromium.org/chromium-os/developer-information-for-chrome-os-
> devices/samsung-sandy-bridge)
> with CELERON 867 cpu, and tried to build a coreboot image with seabios
> in order to use this chromebook as an ordinary PC laptop running GNU/Linux.
>
> It seems that native ram init works on lumpies with core i5 cpu, but on
> mine, coreboot built with native ram init can run payloads with no
> problem, but linux kernel will panic with outputs showed on the attached
> photo (related to processors' synchronization?). Now I have to use Intel
> FSP to perform ram init, on which linux
> kernel (and GNU/Linux) works fine.

Just to clarify, the raminit blob for samsung/lumpy is not technically
Intel FSP, but different (MRC) blob created at Google.
> Config files for FSP and native ram init are also attached.

Please send output of cbmem -c and inteltool -a once system has booted with
raminit blob.
> Best regards.
>
> Persmule