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

[persmule]

Hi all,

The logs generated via "#cbmem -c" and "#inteltool -a" are attached
accordingly.

Best regards.

Persmule


在 2017年01月16日 18:32, Kyösti Mälkki 写道:
> On Mon, Jan 16, 2017 at 12:04 PM, Persmule <persmule at gmail.com> 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
>>
>>
>> --
>> coreboot mailing list: coreboot at coreboot.org
>> https://www.coreboot.org/mailman/listinfo/coreboot
>>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: cbmem.log
Type: text/x-log
Size: 71407 bytes
Desc: not available
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20170116/7102bb96/attachment-0002.log>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: inteltool.log
Type: text/x-log
Size: 147723 bytes
Desc: not available
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20170116/7102bb96/attachment-0003.log>