Red Hat Bugzilla – Bug 122841
memtest86+ broken on some motherboards
Last modified: 2014-03-16 22:45:06 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040506
Description of problem:
The rescue CD in yesterday's compose (as well as FC2test3, and
probably earlier) mentions `memtest86' (sp?) in the boot screen #2,
but entering that option fails because the memtest program is not
included in the rescue cd. Either the boot screen should be adjusted
or the memtest program included.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Boot off the rescue cd
2.Switch to screen #2
3.Enter the memtest86 option, that claims to be available when booting
from the CD
Actual Results: It claims there's no such option.
Expected Results: It would be nice to have memtest in the rescue cd,
instead of only in the CD1. Maybe even in boot.iso?
It's back in rescuecd as of yesterday, but it locks up my Athlon
1.4GHz with Asus A7V133 MoBo and 768MiB of memory just as it starts
and prints the initial screen. Can't Ctrl-Alt-Del, caps lock no
longer works. FWIW, memtest in FC1 worked, and so does memtest for
FC1 supplied by dag wieers'. I was going to test the FC2test3
memtest86 from CD1, but I found it to be missing there as well. Oops
FWIW, I tried it on other boxes, and it works. But on the 3 Athlons I
have access to (all identical to the description above), it locks up
AMD Athlon (0.18) 1410 Mhz
L1 Cache: 128K 8650MB/s
L2 Cache: 256K 2650MB/s
Memory : 768M 320MB/s
Chipset : VIA KT133/KT133A
then, in the middle of the screen:
136K e820-Std off
Tried v1.15 from rawhide?
memtest86+-1.15-1 hangs in exactly the same way :-(
I talked with upstream. He said this is a known issue and it will be
resolved in his next release.
Problem still present in 1.20-1.
Hi, I'm the developer of memtest86+. I just checked the code again,
and you're right, I forgot to remove the faulty code on v1.20 for the
KT133/133A. Only the KT266/333/400+ was removed. Next build (expected
soon) will correct this. Sorry.
Please try the latest rawhide version again.
Yay, it works!