Description of problem: If I try to hibernate my system, my neighbouring partition located on the same physical media as swap is corrupted so data are lost. Both swap and neighbouring partition are configured as lvm logical volumes on luks encrypted partition located on one physical SDHC card. Version-Release number of selected component (if applicable): Kernel used: kernel-2.6.31.9-174.fc12.i686 Pm-utils: pm-utils-1.2.5-6.fc12.i686 Hardware: Acer Aspire One, 1GB Physical RAM Swap size: 1.5GB How reproducible: Hibernate fails and during the next reboot, partition is damaged. Steps to Reproduce: 1. hibernate 2. and the problem pops up 3. Actual results: Corrupted partition (unrecoverable). Expected results: No corruption. Additional info: With the same setup I tried to hibernate two times - in both cases with the same result. Swap device: /dev/mapper/vg_SDHC0p1-lv_swap (no swap space was occupied before hibernation) Second (neighbouring) partition: /dev/mapper/vg_SDHC0p1-lv_p1 (mounted as /var) /etc/crypttab: luks-215cce6f-6627-4d73-b989-b830b2ceb577 UUID=215cce6f-6627-4d73-b989-b830b2ceb577 none luks-SDHC0p1 /dev/mmcblk0p1 none /etc/fstab: UUID=ed7ba3ed-f250-4d15-9d61-ea89de5a469a /boot ext3 noatime,nodiratime,commit=300,data=writeback,nobh,nouser_xattr 1 2 /dev/mapper/vg_txpn-lv_root / ext4 noatime,nodiratime,commit=360,data=writeback,nobh,nouser_xattr 1 1 /dev/mapper/vg_SDHC0p1-lv_p1 /var ext4 defaults,noatime,nodiratime,commit=360,data=writeback,nobh 1 1 /dev/mapper/vg_SDHC0p1-lv_swap swap swap defaults 0 0 tmpfs /dev/shm tmpfs defaults 0 0 devpts /dev/pts devpts gid=5,mode=620 0 0 #devpts options modified by setup update to fix #515521 ugly way sysfs /sys sysfs defaults 0 0 proc /proc proc defaults 0 0 tmp /tmp tmpfs defaults 0 0 vartmp /var/tmp tmpfs defaults 0 0 -------------- Dmesg logs: sd 1:0:0:0: [sda] Starting disk ata2.00: ACPI cmd ef/03:0c:00:00:00:a0 filtered out ata2.00: ACPI cmd ef/03:42:00:00:00:a0 filtered out ata2.00: configured for UDMA/66 PM: writing image. PM: Free swap pages: 383998 Read-error on swap-device (253:3:16) PM: Saving image data pages (101745 pages) ... ^H^H^H^H 0% Read-error on swap-device (253:3:24) Read-error on swap-device (253:3:32) Read-error on swap-device (253:3:40) Read-error on swap-device (253:3:48) Read-error on swap-device (253:3:56) Read-error on swap-device (253:3:64) Read-error on swap-device (253:3:72) Read-error on swap-device (253:3:80) Read-error on swap-device (253:3:88) Read-error on swap-device (253:3:96) Read-error on swap-device (253:3:104) Read-error on swap-device (253:3:112) Read-error on swap-device (253:3:120) Read-error on swap-device (253:3:128) Read-error on swap-device (253:3:136) Read-error on swap-device (253:3:144) Read-error on swap-device (253:3:152) Read-error on swap-device (253:3:160) Read-error on swap-device (253:3:168) Read-error on swap-device (253:3:176) Read-error on swap-device (253:3:184) Read-error on swap-device (253:3:192) Read-error on swap-device (253:3:200) Read-error on swap-device (253:3:208) Read-error on swap-device (253:3:216) Read-error on swap-device (253:3:224) Read-error on swap-device (253:3:232) Read-error on swap-device (253:3:240) Read-error on swap-device (253:3:248) Read-error on swap-device (253:3:256) Read-error on swap-device (253:3:264) Read-error on swap-device (253:3:272) Read-error on swap-device (253:3:280) Read-error on swap-device (253:3:288) Read-error on swap-device (253:3:296) Read-error on swap-device (253:3:304) Read-error on swap-device (253:3:312) Read-error on swap-device (253:3:320) Read-error on swap-device (253:3:328) Read-error on swap-device (253:3:336) Read-error on swap-device (253:3:344) Read-error on swap-device (253:3:352) Read-error on swap-device (253:3:360) Read-error on swap-device (253:3:368) Read-error on swap-device (253:3:376) Read-error on swap-device (253:3:384) Read-error on swap-device (253:3:392) Read-error on swap-device (253:3:400) mmc0: new SDHC card at address 8fe4 bio too big device mmcblk0p1 (8 > 0) Read-error on swap-device (253:3:408) mmcblk1: mmc0:8fe4 SD08G 7.60 GiB mmcblk1: p1 PM: Wrote 406980 kbytes in 0.45 seconds (904.40 MB/s) Restarting tasks ... done. PM: Basic memory bitmaps freed r8169: eth0: link down ADDRCONF(NETDEV_UP): eth0: link is not ready ADDRCONF(NETDEV_UP): wlan0: link is not ready wpa_supplicant[1322]: segfault at 407b05c ip 0807fec2 sp bfd015e0 error 4 in wpa_supplicant[8048000+65000] CPU0 attaching NULL sched-domain. CPU1 attaching NULL sched-domain. CPU0 attaching sched-domain: domain 0: span 0-1 level SIBLING groups: 0 1 CPU1 attaching sched-domain: domain 0: span 0-1 level SIBLING groups: 1 0 PS: I also tried to have swap on luks on lvm before and lvm was corrupted as well.
by the way my SDHC card does not contain faulty sectors: [root@txpn ~]# mkswap -c /dev/mapper/vg_SDHC0p1-lv_swap mkswap: /dev/mapper/vg_SDHC0p1-lv_swap: warning: don't erase bootbits sectors on whole disk. Use -f to force. Setting up swapspace version 1, size = 1535996 KiB no label, UUID=1b4ee84e-d060-4139-a2e6-87a98a40dc67 [root@txpn ~]#
I just confirm I tried to hibernate again with the new kernel - kernel-2.6.31.12-174.2.3.fc12.i686 but I had the same problem again. Dmesg looks the same. I also noticed one strange thing in dmesg: First we have message: PM: Saving image data pages (101745 pages) Then we have those read errors and then we have mmc0: new SDHC card at address 8fe4 And in final PM: Wrote 406980 kbytes in 0.45 seconds (904.40 MB/s) So if I'm interpretting it correctly - does it mean SDHC card is "disconnected" before hibernation data are written to swap located on SDHC? (However dmesg does not say when it is "disconnected", it only says new card is discovered... "mmc0: new SDHC card at address 8fe4" Is this the cause of the problem? Thank you.
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.