[coreboot] Re: Memtest86+ stuck
On 23/04/2020 12:45, Paul Menzel wrote: It’d be great, if you could bisect the commit 2182c5b is the first "good" commit. ___ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
[coreboot] Re: Memtest86+ stuck
On 23/04/2020 13:06, Krystian Hebel wrote: Please try to apply the patch I did some time ago [1]. Unfortunately it does not work for me. I applied patch manually, switched back to the Stable Memtest86+ and ran `make clean && make`; memory test hanged at the same point. Checked twice. ___ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
[coreboot] Re: Memtest86+ stuck
On 23/04/2020 12:07, Paul Menzel wrote: Ok, so you are using SeaBIOS as primary payload. Correct. So, coreboot master with Memtest86+ Stable does *not* work. coreboot master with Memtest86+ Master *does* work? Correct. ___ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
[coreboot] Re: Memtest86+ stuck
On 23/04/2020 09:24, Paul Menzel wrote: 1. How do you build the Memtest86+ payload? 2. What version do you choose? I believe there is *Stable* and *Master*? I just checked the box in the nconfig menu, so it should be Stable as defined in the coreboot's automated build flow. 3. How do you start the Memtest86+ payload? I'm pressing ESC and choose Memtest86+ from the payloads menu. I also checked the Debian's Memtest86+. It stuck on both "good" and "bad" coreboot. If you add the Memtest86+ payload, which works with coreboot 4.7 to coreboot master, does it still work? Yes. Workaround previously suggested by Lars Hochstetter also works. I also rebuilt coreboot with Memtest86+ from master, it also works fine while Debian's Memtest86+ still stuck. ___ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
[coreboot] Memtest86+ stuck
Hello, 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? ___ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
