Bug 178887
| Summary: | MEMORY2 test segfaults | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] Red Hat Ready Certification Tests | Reporter: | Rainer Koenig <Rainer.Koenig> | ||||||||||||
| Component: | rhr2-tests | Assignee: | Will Woods <wwoods> | ||||||||||||
| Status: | CLOSED ERRATA | QA Contact: | Rob Landry <rlandry> | ||||||||||||
| Severity: | medium | Docs Contact: | |||||||||||||
| Priority: | medium | ||||||||||||||
| Version: | 2 | CC: | djuran, richardl | ||||||||||||
| Target Milestone: | --- | ||||||||||||||
| Target Release: | --- | ||||||||||||||
| Hardware: | All | ||||||||||||||
| OS: | Linux | ||||||||||||||
| Whiteboard: | |||||||||||||||
| Fixed In Version: | RHBA-2006-0273 | Doc Type: | Bug Fix | ||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||
| Clone Of: | Environment: | ||||||||||||||
| Last Closed: | 2006-05-08 16:23:21 UTC | Type: | --- | ||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||
| Documentation: | --- | CRM: | |||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||
| Embargoed: | |||||||||||||||
| Attachments: |
|
||||||||||||||
|
Description
Rainer Koenig
2006-01-25 08:25:30 UTC
Created attachment 123653 [details]
hardware.log for CELSIUS M440
Created attachment 123654 [details]
output.log for CELSIUS M440
Created attachment 123655 [details]
hardware.log for CELSIUS R630
Created attachment 123656 [details]
output.log for CELSIUS R630
I did another test on the CELSIUS M440, this time with only 4 GB of RAM. Then MEMORY2 works without segfault. Could it be a problem with the 4 GB boundary? Rainer, with your own Memory Test utility that you ran on the R630, was it run on the same version of RHEL that the MEMORY2 test failed on? Hi, I'm afraid there is a sort of misunderstanding. Our memory test tool doesn't run on Linux, its a sort of DOS tool that we boot from CD. Its capable also for configurations above 4 GB and I guess based on the memtest86 that you find with some other Linux distributions. Regards Rainer Thanks for the clarification. Our MEMORY2 test checks that Linux can access every addressable segment of memory. I think we can rule out bad memory given your report above. Thus, I see two possibilities: - A bug in the MEMORY2 test - A bug related to how RHEL and the hardware interact We will investigate. Any additional insight you may have on the issue would be helpful. Created attachment 123683 [details]
updated lmbench package for RHEL4 - not signed, not for public consumption
This is probably due to a bug in lmbench - on certain arches, attempting to run lat_mem_rd with >=2048MB RAM causes it to segfault. I've attached an updated lmbench package above, which should fix this bug. Could you try upgrading lmbench with this package, and then run MEMORY2 again? I tried that update of lmbench on my M440 machine with 8 GB. This time no errors. The R630 is still busy with the old memory test, if its completed I'll do the test there as well. But so far it looks like the problem is solved. Thanks for the bug report! Feel free to use the new package for submitting test results. We will work on issuing an errata for this package. Hi. I also used the new lmbench RPM and did not see the Seg Fault. It looks like this is fixed. Thanks. According to comment comment 7 in Bug 182713, this problem affects at least the i386 architecture as well. /David An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2006-0273.html |