Actions
Bug #276
openSPI flash console output causes `SMM Handler caused a stack overflow`
Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
07/19/2020
Due date:
% Done:
0%
Estimated time:
Affected versions:
Needs backport to:
Affected hardware:
Affected OS:
Description
On the Lenovo T60 (Type 2007 with dedicated ATI/AMD graphics device), coreboot built with SPI Flash console output (CONFIG_CONSOLE_SPI_FLASH=y
) fails to boot due to a stack overflow:
FMAP: area COREBOOT found @ 60200 (1703424 bytes)
CBFS: Locating 'fallback/dsdt.aml'
CBFS: Found @ offset 39300 size 3138
FMAP: area COREBOOT found @ 60200 (1703424 bytes)
CBFS: Locating 'fallback/slic'
CBFS: 'fallback/slic' not found.
ACPI: Writing ACPI tables at bfb51000.
ACPI: * FACS
ACPI: * DSDT
FMAP: area CONSOLE found @ 0 (131072 bytes)
coreboot-4.12-1529-gaba8103093 Sun Jul 19 07:24:18 UTC 2020 smm starting (log level: 7)...
canary 0x0 != 0xbfeffc00
SMM Handler caused a stack overflow
Updated by Filip LewiĆski 3 months ago
Paul Menzel wrote:
On the Lenovo T60 (Type 2007 with dedicated ATI/AMD graphics device), coreboot built with SPI Flash console output (
CONFIG_CONSOLE_SPI_FLASH=y
) fails to boot due to a stack overflow:FMAP: area COREBOOT found @ 60200 (1703424 bytes) CBFS: Locating 'fallback/dsdt.aml' CBFS: Found @ offset 39300 size 3138 FMAP: area COREBOOT found @ 60200 (1703424 bytes) CBFS: Locating 'fallback/slic' CBFS: 'fallback/slic' not found. ACPI: Writing ACPI tables at bfb51000. ACPI: * FACS ACPI: * DSDT FMAP: area CONSOLE found @ 0 (131072 bytes) coreboot-4.12-1529-gaba8103093 Sun Jul 19 07:24:18 UTC 2020 smm starting (log level: 7)... canary 0x0 != 0xbfeffc00 SMM Handler caused a stack overflow
I've experienced the same with coreboot+EDK2(MrChromeBox) on a Thinkpad T400. If you still have trouble booting the platform, I've somehow managed to bypass it by rebuilding with 64bit mode enabled.
Updated by Arthur Heymans 3 months ago
config SMM_MODULE_STACK_SIZE
hex
default 0x800 if ARCH_RAMSTAGE_X86_64
default 0x400
So just bumping this to always use 0x800 might be a solution
Actions