[coreboot] [RFH] Status of the Lenovo X201

Nicola Corna nicola at corna.info
Wed Apr 25 12:51:41 CEST 2018

April 18, 2018 3:54 PM, "Kyösti Mälkki" <kyosti.malkki at gmail.com> wrote:

> Having romstage stack smashed seems irrelevant for the no-boot issue.
> That nehalem raminit code, struct raminfo, seems to eat a lot of stack
> and an error message for that case was added with commit 2c3fd49. You
> could try parent of that commit, but rumour is lenovo/x201 was a
> no-boot case long time before that.

I'll do some tests to find which commit caused the no-boot.

> I can see int15h messages interleaved with SMP init, that looks odd to
> me. Also, did the log really end inside 0:1f.0 PCI finalize or was
> usbdebug logging just interrupted for some reason at that point?

The log really ends there.

> Try current master with default config instead of a one derived from
> last reported board_status. There has been lot of changes on
> framebuffer kconfig settings. And we probably need the .config you
> used to assess what's happening there.

I've tried with the current master on a fresh config, but the result is
the same. Attached you can find the log and the .config.

If needed I can do some tests on this PC.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: x201_config
Type: application/octet-stream
Size: 22166 bytes
Desc: not available
URL: <http://mail.coreboot.org/pipermail/coreboot/attachments/20180425/ebdfab9f/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: x201_log
Type: application/octet-stream
Size: 56866 bytes
Desc: not available
URL: <http://mail.coreboot.org/pipermail/coreboot/attachments/20180425/ebdfab9f/attachment-0003.obj>

More information about the coreboot mailing list