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

--
Felix Held
c/o cyberkombinat23
Steinstraße 23
76133 Karlsruhe
Germany

[email protected]

Ust-ID: DE301814366
_______________________________________________
coreboot mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to