Tested it both with microcode and without microcode. It doesent changes the behaviour.
Am 09.07.19 um 11:43 schrieb Felix Held:
Hi!
Since I didn't see that being mentioned in the bug reports: Is this with or without microcode updates being applied in coreboot? If the crashes only happens without those being applied, it's not a coreboot problem.
Maybe we should add a "-no_ucode" or simply a "-tainted" to the bios version reported if no microcode updates are applied in coreboot to make sure that we're not debugging some non-coreboot issue there. Haven't really looked into it, but might be non-trivial to implement though, since there are quite a few way how to not apply or apply microcode updates and this doesn't depend on just one configuration switch.
Regards Felix