Escalated to Bugzilla from IssueTracker
Please attach the test results (either the results rpm, or /var/hts/results.xml) - Thanks
Created attachment 146479 [details] results.xml from failed memory test - IBM
(In reply to comment #15) > Created an attachment (id=146469) [edit] > failed mem test - results.xml > This run failed stating that the bw_mem command was not found - this is one of the lmbench tools, and should be in /usr/bin. Please check this, and also, what version/revision of lmbench is installed, and where did you obtain it? - Thanks
Created attachment 146656 [details] esults-memory-bl3-9.xmldl
Spoke to IBM this morning. So, the problem happens only when the memory = 4G. If its more or less than that, the test passes. So my tests are not valid. Any updates on this? This is blocking IBM's cert on RHEL 5 System P. - Archana
Please try running the threaded_memtest directly, ala: > cd /usr/share/hts/tests/memory > make threaded_memtest > ./threaded_memtest -qpv -m100% -t10 Also try it with a slightly lower memory paramter: ./threaded_memtest -qpv -m95% -t10 - Thanks!
The problem is that the threaded_memtest binary is compiled as a 32-bit application. A work-around for this bug is to set -m64 prior to running the test, as in: > CFLAGS=" -m64 " > export CFLAGS > hts certify --test memory
Fixed R25: threaded_memtest compiles with -m64 on ppc64
----- Additional Comments From hien1.com 2007-02-09 17:24 EDT ------- I changed CFLAGS in Makefile, and it worked fine. Running 16GB memory test. it will take long time to run .Will post the results when done. This event sent from IssueTracker by araghavan issue 111840
----- Additional Comments From hien1.com 2007-02-10 12:49 EDT ------- HTS memory test passed with CFLAGS=-m64 This event sent from IssueTracker by araghavan issue 111840
changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ACCEPTED |CLOSED ------- Additional Comments From hien1.com 2007-02-15 14:58 EDT ------- Memory test fixed in HTS-5.0-25. This event sent from IssueTracker by araghavan issue 111840