memtest86 on the opteron
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): 1055040745.27939.3.camel@camp4.serpentine.com.suse.lists.linux.kernel
Quoted 8 lines · Bryan O'Sullivan
Quoted 2 lines · Pavel Machek
Well, as opteron is i386-compatible, you should be able to simply use i386 memtest...
It doesn't work. Crashes and reboots the system shortly after it starts. The serial console support appears to have bit-rotted, too, so I've not been able to capture an output screen to diagnose the problem.
The problem is the CPUID handling in memtest86. It does not expect the 15 model number on AMD systems. Someone did a patch for it, but I don't remember where they put it. Anyways should be easy to fix again given the source.
-Andi
Quoted 7 lines · Andi Kleen
Quoted 5 lines · Bryan O'Sullivan
Quoted 2 lines · Pavel Machek
Well, as opteron is i386-compatible, you should be able to simply use i386 memtest...
Quoted 9 lines
Quoted 3 lines
It doesn't work. Crashes and reboots the system shortly after it starts. The serial console support appears to have bit-rotted, too, so I've not been able to capture an output screen to diagnose the problem.
The problem is the CPUID handling in memtest86. It does not expect the 15 model number on AMD systems. Someone did a patch for it, but I don't remember where they put it. Anyways should be easy to fix again given the source.
If you find the patch I am interested in it. Please CC me.
I am guessing that a normal 32bit compiled memtest86 wont be able to test beyond 4GB of RAM on AMD64?
Warren
Quoted 18 lines · Warren Togami
Quoted 7 lines · Andi Kleen
Quoted 5 lines · Bryan O'Sullivan
Quoted 2 lines · Pavel Machek
Well, as opteron is i386-compatible, you should be able to simply use i386 memtest...
Quoted 9 lines
Quoted 3 lines
It doesn't work. Crashes and reboots the system shortly after it starts. The serial console support appears to have bit-rotted, too, so I've not been able to capture an output screen to diagnose the problem.
The problem is the CPUID handling in memtest86. It does not expect the 15 model number on AMD systems. Someone did a patch for it, but I don't remember where they put it. Anyways should be easy to fix again given the source.
Quoted 4 lines
If you find the patch I am interested in it. Please CC me.
I am guessing that a normal 32bit compiled memtest86 wont be able to test beyond 4GB of RAM on AMD64?
memtest86 has PAE support so it should be able to test everything. I have tested with 6GB of RAM on an old PIII.
Beyond the cpuid thing. There is a bug in the probing of how much memory is cached. Last time I was playing with it I just disabled that section of code.
If nothing else ping me a few times because I will need this shortly. If it really does not work. And I am familiar with the code so I will certainly get it fixed.
Eric