Bug #511
closed[STM/PE][BUG][SMMSTORE] Coreboot doesn't boot if SMMSTOREv2 driver Kconfig option is enabled when using STM (STM/PE)
0%
Description
For some reason the SMMSTOREv2 looks to break SMMSTORE support in STM/PE during boot.
Coreboot: 4.21
HARDWARE: Gigabyte H61M-DS2 with Ivybridge processor
Payload: EDK2
SMMSTORE: SMMSTOREv2
A example with other guy using https://www.reddit.com/r/coreboot/comments/10rakni/comment/k444jz1/?context=3
- According with the reddit user crazyfox-ua " The same for me on T440p & X230t (both with edk2) - just blank screen. Disabled STM brings both laptops back to life. CB logs says nothing strange IMO (last record is "[DEBUG] Jumping to boot code at ".
Is necessary to test if others payloads is affected by this bug
Updated by Matt DeVillier about 1 year ago
was this combination previously working with the 4.20 tag?
Updated by Elias Souza about 1 year ago
Matt DeVillier wrote in #note-1:
was this combination previously working with the 4.20 tag?
Sadly no, it's not working in the 4.20, the first try is from 8 months past and continues to can't boot, just work if SMMSTOREv2 driver is not enabled and just SMMSTOREv1 is used.
Updated by Matt DeVillier about 1 year ago
Elias Souza wrote in #note-2:
Matt DeVillier wrote in #note-1:
was this combination previously working with the 4.20 tag?
Sadly no, it's not working in the 4.20, the first try is from 8 months past and continues to can't boot, just work if SMMSTOREv2 driver is not enabled and just SMMSTOREv1 is used.
have you tried just disabling SMMSTORE on the edk2 side? You can do that by removing the param passed to edk2 via the extra build params Kconfig.
Sounds like this will need to be debugged on a board with serial output to see what's breaking in edk2
Updated by Elias Souza about 1 year ago
Matt DeVillier wrote in #note-3:
Elias Souza wrote in #note-2:
Matt DeVillier wrote in #note-1:
was this combination previously working with the 4.20 tag?
Sadly no, it's not working in the 4.20, the first try is from 8 months past and continues to can't boot, just work if SMMSTOREv2 driver is not enabled and just SMMSTOREv1 is used.
have you tried just disabling SMMSTORE on the edk2 side? You can do that by removing the param passed to edk2 via the extra build params Kconfig.
Sounds like this will need to be debugged on a board with serial output to see what's breaking in edk2
Oh thanks i will try to remove -DSMMSTORE from edk2 build and post the result here, the most problem are that i don't have a specific hardware debugger for UART debugging,
In my country this is so hard to find
Updated by Patrick Rudolph about 1 year ago
Tested coreboot 17848b65c38c32fa9630925ca8a15203a0617788 with EDK2 92533b23fb93259b20661b6534109e9f59384e93 origin/uefipayload_202306 and SMMSTOREv2 works fine on Lenovo X220 (SandyBridge).
What's a STM/PE?
Updated by Elias Souza about 1 year ago
Patrick Rudolph wrote in #note-5:
Tested coreboot 17848b65c38c32fa9630925ca8a15203a0617788 with EDK2 92533b23fb93259b20661b6534109e9f59384e93 origin/uefipayload_202306 and SMMSTOREv2 works fine on Lenovo X220 (SandyBridge).
What's a STM/PE?
This Issue is about STM/PE a Supervisor/Hypervisor for SMM System Management Mode, if you can test too can be good too, please if are possible, just enable STM option in Menuconfig and enable STM/PE Hypervisor
Updated by Elias Souza about 1 year ago
- Subject changed from [STM/PE][BUG][SMMSTORE] Coreboot doesn't boot if SMMSTOREv2 driver Kconfig option is enabled to [STM/PE][BUG][SMMSTORE] Coreboot doesn't boot if SMMSTOREv2 driver Kconfig option is enabled when using STM (STM/PE)
Updated by Patrick Rudolph about 1 year ago
The STM was never tested on production environments and might not work with other SMM "services" like SMMSTORE.
I would assume that you need to compile the SMMSTORE code into the stm.bin, however that's not the case right now.
Updated by Eugene Myers about 1 year ago
In this instance, the STM is not active. The only thing coreboot does for the STM is setup some data structures and move the STM binary into the MSEG. The operating system has to start the STM. If coreboot is crashing when STM and SMMSTOREV2 are configured at the same time, this means that there is a collision in the TSEG layout. We need a coreboot trace to ferret this out.
Updated by Eugene Myers 12 months ago
See CB:78889 for a resolution for this issue.
Updated by Martin Roth 12 months ago
- Status changed from Needs Testing to Resolved