Bug 114555
| Summary: | kernel BUG at vmscan.c:545! | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Lachlan Paterson <lachlan> |
| Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
| Status: | CLOSED DUPLICATE | QA Contact: | Brian Brock <bbrock> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 9 | CC: | lachlan, riel |
| 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: | 2006-02-21 19:00:59 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
Lachlan Paterson
2004-01-29 15:38:37 UTC
*** This bug has been marked as a duplicate of 73733 *** Your kernel is tainted with the proprietary kernel module. We do not support any system which has had any 3rd party kernel module loaded into the running kernel since boot time. You would have to remove all 3rd party kernel modules from your system, then reboot into a clean Red Hat supplied binary kernel, and then reproduce this problem with out using the "nvidia" proprietary module, nor any other 3rd party kernel modules loaded since boot time. Also, unloading a module that was previously unloaded does not work around this. You must not load any unsupported kernel module after the kernel boots. If you can reproduce the problem under these conditions, feel free to update the report with additional details. Ok, thanks, I will try. I have removed the nvidia kernel, and the crashes still happen. This thread documents that: http://www.nvnews.net/vbulletin/showthread.php?s=&threadid=24356 I am not sure what is still tainting my kernel. It must be a sound module. I will try find out and remove whatever is there. Nevermind... I found the problem. I have memory errors. I ran memtest86 to check the memory and I have errors during test#5. In the memtest docs it says this: "There have been numerous reports of errors in only tests 5 and 8 on Athlon systems. Often the memory works in a different system or the vendor insists that it is good. In these cases the memory is not necessarily bad but is not able to operate reliably at Athlon speeds. Sometimes more conservative memory timings on the motherboard will correct these errors. In other cases the only option is to replace the memory with better quality, higher speed memory. Don't buy cheap memory and expect it to work with an Athlon! On occasion test 5/8 errors will occur even with name brand memory and a quality motherboard. These errors are legitimate and should be corrected." ...so there you go. Changed to 'CLOSED' state since 'RESOLVED' has been deprecated. |