April 18, 2018 3:54 PM, "Kyösti Mälkki" <kyosti.mal...@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. Nicola
x201_config
Description: Binary data
x201_log
Description: Binary data
-- coreboot mailing list: coreboot@coreboot.org https://mail.coreboot.org/mailman/listinfo/coreboot
