Bug 65608
Summary: | VM oops in 2.4.18-3 | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Need Real Name <mb/redhat> |
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
Status: | CLOSED NOTABUG | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.3 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | athlon | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2002-05-28 16:45:39 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: |
Description
Need Real Name
2002-05-28 14:26:26 UTC
If you don't trust your memory, the memtest86 program (search on www.freshmeat.net for it if needed) is a pretty good tester of ram chips. It had passed a few passes of memtest86 before being put into production. I'll re-run it (we have had RAM go dodgy in the past), but it is ECC RAM, so (to quote Alan Cox): memtest86 will give fairly honest answers on ECC RAM. It'll see errors that ECC didnt correct or were caused by chipset/cache/wiring capacitance etc. Those are the same errors the kernel will see Well you could also try to see if the "ecc" kernel module (included in all RH's recent kernels) detects ECC faults... it's supposed to report ECC soft-failures to syslog Ahhh! memtest86 3.0 has ECC "stuff" in it. Bingo. My bad. |