Red Hat Bugzilla – Bug 770443
Data corruption: resume from hibernate (Lenovo G470) always ends up with EXT4 fs errors
Last modified: 2012-05-14 13:58:48 EDT
+++ This bug was initially created as a clone of Bug #658391 +++
Description of problem:
After I resume from hibernation, on my F16 laptop, I always end up with programs that do not work - which ends up with me forcing to reboot the laptop, only to find out it's due to FS consistency issues on the EXT4 LV.
Let me know what more details you need from me to diagnose this.
Version-Release number of selected component (if applicable):
Always, I think.
Steps to Reproduce:
--- Additional comment from firstname.lastname@example.org on 2011-02-18 18:23:42 EST ---
Same thing on x200s.
EXT4-fs error (device dm-1): ext4_mb_generate_buddy: EXT4-fs: group 6: 7851 blocks in bitmap, 7822 in gd
JBD: Spotted dirty metadata buffer (dev = dm-1, blocknr = 0). There's a risk of filesystem corruption in case of system crash.
--- Additional comment from email@example.com on 2011-06-17 01:19:33 EDT ---
Since updating to kernel-18.104.22.168-92.fc14.x86_64 I consistently get file system corruption on my ext3 root file system after resuming from hibernation.
Does the laptop have i915 graphics hardware? If so, can you check if booting with i915.modeset=0 kernel parameter workaround the problem.
If you find yourself needing to reinstall anyway, testing other filesystems (maybe ext3, maybe xfs to be even further from ext4) might be interesting.
Turning off the hard drive write cache before hibernate might also be interesting, if possible.
(Is this bug cloned because you hit it on ext4 not ext3, I guess? Still, testing ext3 or xfs on the same hardware might be interesting)
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.
[Mass hibernate bug update]
Dave Airlied has found an issue causing some corruption in the i915 fbdev after a resume from hibernate. I have included his patch in this scratch build:
This will probably not solve all of the issues being tracked at the moment, but it is worth testing when the build completes. If this seems to clear up the issues you see with hibernate, please report your results in the bug.