Bug 556560
Summary: | ext4 gives ext4_mb_generate_buddy after resume from hibernate | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Bingo <right.ho> |
Component: | kernel | Assignee: | Eric Sandeen <esandeen> |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | low | ||
Version: | 12 | CC: | anton, dougsland, esandeen, gansalmon, itamar, jonathan, kernel-maint, lowe, mishu |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-12-04 00:11:34 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
Bingo
2010-01-18 17:57:16 UTC
I have mixed up the "Actual results:" and "Expected results:" above. Can I edit to correct it? All mount options are default. Sorry for not seeing this sooner. Do you still have this problem with the 2.6.32 kernels in F12? Thanks, -Eric Don't know, because I switched to jfs because of this problem. I will try ext4 again and update this bug. Thanks, I appreciate it! If it's related to hibernate, it could maybe be some form of memory corruption ... but just guessing here. -Eric If you mean malfunctioning RAM modules, I had tested my RAM using memtest86 for 12 hours during the days when I had this problem. So I guess chances of malfunctioning RAM modules are pretty slim. If you mean some kernel memory corruption, I don't know about that. Confirmed in FC13 with kernel 2.6.33.4-95.fc13.x86_64 For those hitting the problem: Just to test a theory, could you try doing "hdparm -W" on your disk(s) to check the write cache status? If it's 1 (on), then prior to hibernate, can you try hdparm -W 0 on the disk(s) and see if the problem persists? I'm wondering if it's possible that data in the drive's write cache got lost when the system powered down, if it wasn't properly flushed during hibernate. You'll want to do hdparm -W 1 later to turn them back on if that was the original state. Thanks, -Eric For those hitting it, are you using intel i915 video? https://bugzilla.kernel.org/show_bug.cgi?id=13811 Bug 13811 - [GM965/KMS/UXA] memory corruption on resume from hibernate -Eric Yes, I see this bug on a Dell Latitude E5400 laptop with GM45/KMS/UXA. It would be interesting to hibernate from text mode / runlevel 3 with the video driver blacklisted/unloaded, and see if the problem goes away, I suppose. If I do the following: - F13 boot on runlevel 3 with "nomodeset 3" on grub line - from root prompt run "modprobe -r i915" - run pm-hibernate then I don't see anymore the messages from comment 1 and all is fine. Great, thanks for the report. Here and on the kernel.org bug, this seems to be the case for most, if not all, people. Looks like this is an i915 bug. Last kernel update for F13 (kernel-2.6.33.6-147.fc13) does not fix this bug even that there was some hope - see this changelog from kernel: * Fri Jul 02 2010 Dave Airlie <airlied> 2.6.33.5-140 - attempt to fix hibernate on Intel GPUs (kernel.org #13811) This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |