Bug 839700
Summary: | kernel: bad_page | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Alon Levy <alevy> |
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 17 | CC: | dblechte, gansalmon, itamar, jforbes, jonathan, kernel-maint, madhu.chinakonda |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-01-08 15:48:05 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Alon Levy
2012-07-12 15:15:05 UTC
Just to rule it out, can you give memtest86 a run for while ? (In reply to comment #1) > Just to rule it out, can you give memtest86 a run for while ? Ran it for 30 minutes, no problems. Are you still having an issue with this using newer 3.5.3 kernels? x86_64 garlic:~ alon$ dmesg | grep "Bad page" | wc -l 0 Looks like none. I don't remember seeing it. Just note that a) I'm running 3.6.0-0.rc4.git2.3.fc18.x86_64 b) it's a release build I created from the latest kernel fedpkg of above version. |