Bug 196688 - rhr2.0-3 MEMORY2 test hangs on RHEL3 with more than 4GB.
rhr2.0-3 MEMORY2 test hangs on RHEL3 with more than 4GB.
Status: CLOSED WONTFIX
Product: Red Hat Ready Certification Tests
Classification: Retired
Component: rhr2-tests (Show other bugs)
2
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Greg Nichols
Will Woods
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2006-06-26 10:32 EDT by Gregory Feiner
Modified: 2008-07-17 18:03 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-07-17 18:03:24 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
RHEL3 U6 X86, 8GB of RAM installed. MEM2 never completes. (418.36 KB, application/octet-stream)
2006-06-26 10:32 EDT, Gregory Feiner
no flags Details
RHEL3 U7 x86_64, 8GB RAM. MEM2 completes normally (457.63 KB, application/octet-stream)
2006-06-26 10:33 EDT, Gregory Feiner
no flags Details
RHEL 3 U7 x86, 2GB RAM. MEM2 completes normally (640.51 KB, application/octet-stream)
2006-06-26 10:36 EDT, Gregory Feiner
no flags Details
RHEL3 U7 x86, 4GB RAM. MEM2 completes normally (653.47 KB, application/octet-stream)
2006-06-26 10:37 EDT, Gregory Feiner
no flags Details
RHEL3 U7 x86, 8GB RAM. MEM2 never completes. (661.39 KB, application/octet-stream)
2006-06-26 10:38 EDT, Gregory Feiner
no flags Details
RHEL3 U7 x86, 12GB RAM. MEM2 never completes (429.73 KB, application/octet-stream)
2006-06-26 10:39 EDT, Gregory Feiner
no flags Details
RHEL3 U7 x86. 32GB RAM. MEM2 never completes. (472.29 KB, application/octet-stream)
2006-06-26 10:40 EDT, Gregory Feiner
no flags Details

  None (edit)
Description Gregory Feiner 2006-06-26 10:32:26 EDT
Description of problem:
Memory2 test on the rhr2.0-3 kit never finishes if system has more that 4GB of 
RAM installed.  This only happens on RHEL3 x86. I have reproduced this on U7 
and U6.  This did not happen with the previous kit.  MEM2 works fine with the 
same amount of RAM on RHEL4.

Version-Release number of selected component (if applicable): 2.0-3


How reproducible: Every time.


Steps to Reproduce:
1. Install RHEL 3 U6 or U7 (x86) on a system that will have more than 4GB of 
RAM free after the OS is running.
2. Install the 2.0-3 kit and run MEMORY2.
  
Actual results:  MEM2 stops updating the output.log file after a couple hours 
and never completes (I waited as much as 3 days). You have to ctrl-C to get 
out of the test. At which point you end up with a result of "ERROR".


Expected results:  Test should complete on it's own.

Additional info: Several test logs with varying amounts of RAM are attached.
Comment 1 Gregory Feiner 2006-06-26 10:32:28 EDT
Created attachment 131543 [details]
RHEL3 U6 X86, 8GB of RAM installed. MEM2 never completes.
Comment 2 Gregory Feiner 2006-06-26 10:33:29 EDT
Created attachment 131544 [details]
RHEL3 U7 x86_64, 8GB RAM. MEM2 completes normally
Comment 3 Gregory Feiner 2006-06-26 10:36:37 EDT
Created attachment 131545 [details]
RHEL 3 U7 x86, 2GB RAM.  MEM2 completes normally
Comment 4 Gregory Feiner 2006-06-26 10:37:25 EDT
Created attachment 131546 [details]
RHEL3 U7 x86, 4GB RAM. MEM2 completes normally
Comment 5 Gregory Feiner 2006-06-26 10:38:15 EDT
Created attachment 131547 [details]
RHEL3 U7 x86, 8GB RAM. MEM2 never completes.
Comment 6 Gregory Feiner 2006-06-26 10:39:58 EDT
Created attachment 131548 [details]
RHEL3 U7 x86, 12GB RAM. MEM2 never completes
Comment 7 Gregory Feiner 2006-06-26 10:40:39 EDT
Created attachment 131549 [details]
RHEL3 U7 x86. 32GB RAM. MEM2 never completes.
Comment 12 Rob Landry 2008-07-17 18:03:24 EDT
rhr2 has been deprecated, closing these remaining bugs as WONTFIX.  Future bugs
against the "hts" test suite should be opened agains the "Red Hat Hardware
Certification Program" product selecting either "Test Suite (harness)" or "Test
Suite (tests)" components.

Note You need to log in before you can comment on or make changes to this bug.