On 6/11/21 4:18 AM, Nico Huber wrote:
0xfefe0000..0xfeffffff is a range used for cache- as-ram (CAR) which is a mode where the processor cache is used as RAM before the actual DRAM is available.
Thank you Nico for the insight! On 6/11/21 5:05 AM, Angel Pons wrote:
They look a lot like what https://review.coreboot.org/28443 fixed. You could check if commit dfaff4d18a711f764c9198f488435fdc553dcea2 exists on 4.8.1 (if it does not, there's your problem).
I manually applied the linked patch to my local coreboot-4.8.1 and no longer see those mce messages. Thank you Angel! On 6/11/21 5:25 AM, Paul Menzel wrote:
There is a draft merge/pull request for coreboot 4.13: *(BRICKS T430because OPTION_TABLE) WiP: build xx30 boards against coreboot 4.13 #944* [3].
Yeah, that worries me. So I'll stay away from that until I understand the subject matter a bit deeper. On 6/11/21 5:26 AM, Simon Newton wrote:
Ill port a heads build with> 4.11 for Sven (and myself, as I have the same issue) and see if that resolves.
That might still be worthwhile, but if you just want to get rid of the mce errors the patch linked by Angel does the trick.
Cheers, /Sven PS: I'll stay around and learn. Thanks everyone! -- public key: https://www.svensemmler.org/2A632C537D744BC7.asc fingerprint: DA59 75C9 ABC4 0C83 3B2F 620B 2A63 2C53 7D74 4BC7
OpenPGP_signature
Description: OpenPGP digital signature
_______________________________________________ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
