Dear Max,
Am 22.04.20 um 23:11 schrieb Max Zim:
I discovered the issue with Memtest86+ stuck on my Thinkpad x230 on the
very first tests. Always on the same point, 52%. Every release since 4.8
works this way, coreboot 4.7 works fine. Is this a known bug?
Thank you for your report. I cannot remember hearing/reading about that.
Your report is lacking some details, so it’s unclear if it’s a
regression in Memtest86+ or coreboot. It’d be great if you could answer
the questions below.
1. How do you build the Memtest86+ payload?
2. What version do you choose? I believe there is *Stable* and *Master*?
3. How do you start the Memtest86+ payload? I assume you have it as
secondary payload, and select it from some primary payload
(`fallback/payload` in CBFS)? Which one do you use?
4. Payloads are actually interchangeable between coreboot versions. If
you add the Memtest86+ payload, which works with coreboot 4.7 to
coreboot master, does it still work?
Something like:
$ build/cbfstool path/to/coreboot-v4.7.rom extract -n
img/memtest -f memtest-v4.7
And then for the master:
$ build/cbfstool path/to/coreboot-master.rom add-payload -n
img/mtest-v4.7 -f memtest-v4.7 -c lzma
That way, we can figure out if it’s a regression in coreboot or
Memtest86+.
Kind regards,
Paul
_______________________________________________
coreboot mailing list -- [email protected]
To unsubscribe send an email to [email protected]
