F17 may corrupt user data when hibernating/resuming?

[hostace]

After suspend/resume I see this in dmesg:

Apr 26 09:48:53 raistlin kernel: [ 4370.667931] EXT4-fs error (device dm-1) in ext4_new_inode:941: IO failure
Apr 26 09:50:18 raistlin kernel: [ 4454.833845] EXT4-fs error (device dm-1) in ext4_new_inode:941: IO failure
Apr 26 09:50:19 raistlin kernel: [ 4456.732290] EXT4-fs error (device dm-1) in ext4_new_inode:941: IO failure
Apr 26 09:51:06 raistlin kernel: [ 4503.110715] EXT4-fs error (device dm-1) in ext4_new_inode:941: IO failure
Apr 26 09:51:06 raistlin kernel: [ 4503.565660] EXT4-fs error (device dm-1) in ext4_new_inode:941: IO failure
Apr 26 09:51:12 raistlin kernel: [ 4508.913964] EXT4-fs error (device dm-1) in ext4_new_inode:941: IO failure
Apr 26 09:51:48 raistlin kernel: [ 4545.544151] EXT4-fs error (device dm-1) in ext4_new_inode:941: IO failure

kernel is 3.3.6-3.fc17.x86_64. All tested F17 kernels also corrupts my EXT4 filesystem. Can I recompile my kernel from srpms for resolving this issue?

[AdamW]

Hibernate, or suspend? The two are rather different. And are you sure it's not a hardware failure?

[hostace]

Yes, I'm sure. Only hybernate. I'mfound closed bugs in Fedora with samr problems. Now I'm filed bugreport 823871. Now I'm testing my HDD with smart an burn-in tests. In Windows, FC15 and other Linux distributions with older kernels I have no this issue at all. In 2 hour I will file additional requested info for that bugreport. It's something with 3.x kernel only. see additional bug 822071, It's same problem (i think, bug 823871 and 822071 is duplicate).

---------- Post added at 09:10 PM ---------- Previous post was at 09:06 PM ----------

And I think, this is must be a release blocker bug due release criteria

All known bugs that can cause corruption of user data must be fixed or documented at Common F17 bugs

[lklaus]

Well, I'm using suspend and hibernate regularly, and do not have any problems. So, probably something that's connected to your hardware, as the older bugs had problems only with intel VGA hardware

Klaus

[hostace]

Yes, It's Intel harware. But it's popular hardware. And it's not VGA. See details at https://bugzilla.redhat.com/show_bug.cgi?id=744275

[lklaus]

Ok, then this is a different bug than I was seeing with different hardware long time ago...

[AdamW]

Please mark your bug as blocking https://bugzilla.redhat.com/show_bug.cgi?id=781749 , thanks!

[hostace]

I'm commentwd, but I don't know how I can mark this bug as release blocker. I was attached requested info for my original bug too late, because I was reproduced this bug yesterday and my filesystem completely crashed and system was reinstalled, because old installation was unbootable after updating it via yum due to errors in package unpacking.

[george_toolan]

What kind of a netbook is this?

[hostace]

It's Acer Aspire One AOD 260. I think, problem persists with other Acer netbooks such as AOD250/270 and other netbooks wiith N10/ICH7.

[lklaus]

This really is interesting, I also have a
System: AOD260 V1.08_Vodafone
My last system boot now is nearly 14 days away, and I'm using the system every day, and do hibernate every day. What I'm doing differently, though, is not using lvm, as per my experience with a AAO110 and F14 (where this did happen also). And then, on a netbook, I don't think I need LVM anyway...

Klaus

[hostace]

I'm using XEN virtual machines with LVM for my work. O'k. Are you using power save options?

root@raistlin raistlin]# cat /etc/rc.d/rc.local
#!/bin/bash
hdparm -B 128 /dev/sda
echo 1 > /sys/module/snd_hda_intel/parameters/power_save
for i in `ls /sys/bus/usb/devices/*/power/level` ; do echo "auto" > $i ; done
for i in `ls /sys/class/scsi_host/host*/link_power_management_policy` ; do echo "min_power" > $i ; done
for i in `ls /sys/bus/pci/devices/*/power/control` ; do echo "auto" > $i ; done
[root@raistlin raistlin]#

Show me your output from lspci ? Difference is important.

---------- Post added at 10:14 PM ---------- Previous post was at 10:12 PM ----------

Are your RAM is DDR2 (my netbook with DDR3) and may be some difference in BIOS versions (I have Insyde H2O V 3.16 DDR3)

---------- Post added at 10:18 PM ---------- Previous post was at 10:14 PM ----------

Also you can see https://bugzilla.redhat.com/show_bug.cgi?id=781749 for details.

I suspect, that it is problem - hardware independent and on low-level programming. May be it's acpi quirks. Tomorrow I will try to reproduce this bug without ACPI.

[lklaus]

Yes, i'm using (different) power saving options:

echo 10 > /sys/module/snd_hda_intel/parameters/power_save
while read a b; do
echo $a > $b
done < /home/klaus/Configs/doit
ifconfig em1 down
#cpupower frequency-set -g powersave
cpupower frequency-set -u 1.5GHz
echo 1500000 >/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo 1500000 >/sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq

echo disable > /sys/firmware/acpi/interrupts/gpe01


with the input:
1 /sys/module/snd_hda_intel/parameters/power_save
min_power /sys/class/scsi_host/host0/link_power_management_policy
auto /sys/bus/usb/devices/1-6/power/control
auto /sys/bus/usb/devices/5-1/power/control
auto /sys/bus/pci/devices/0000:00:1c.0/power/control
auto /sys/bus/pci/devices/0000:00:1c.1/power/control
auto /sys/bus/pci/devices/0000:00:1b.0/power/control
auto /sys/bus/pci/devices/0000:00:00.0/power/control
auto /sys/bus/pci/devices/0000:00:02.0/power/control
auto /sys/bus/pci/devices/0000:00:1d.0/power/control
auto /sys/bus/pci/devices/0000:00:1d.1/power/control
auto /sys/bus/pci/devices/0000:00:1d.2/power/control
auto /sys/bus/pci/devices/0000:00:1d.7/power/control
auto /sys/bus/pci/devices/0000:00:1f.2/power/control
auto /sys/bus/pci/devices/0000:00:1f.3/power/control
auto /sys/bus/pci/devices/0000:01:00.0/power/control
auto /sys/bus/pci/devices/0000:02:00.0/power/control
auto /sys/bus/pci/devices/0000:00:1d.3/power/control


lspci:
klaus@acer:~$ lspci
00:00.0 Host bridge: Intel Corporation N10 Family DMI Bridge
00:02.0 VGA compatible controller: Intel Corporation N10 Family Integrated Graphics Controller
00:02.1 Display controller: Intel Corporation N10 Family Integrated Graphics Controller
00:1b.0 Audio device: Intel Corporation N10/ICH 7 Family High Definition Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 2 (rev 02)
00:1d.0 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #3 (rev 02)
00:1d.3 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #4 (rev 02)
00:1d.7 USB Controller: Intel Corporation N10/ICH 7 Family USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
00:1f.0 ISA bridge: Intel Corporation NM10 Family LPC Controller (rev 02)
00:1f.2 SATA controller: Intel Corporation N10/ICH7 Family SATA AHCI Controller (rev 02)
00:1f.3 SMBus: Intel Corporation N10/ICH 7 Family SMBus Controller (rev 02)
01:00.0 Ethernet controller: Atheros Communications AR8132 Fast Ethernet (rev c0)
02:00.0 Network controller: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller (rev 01)


I do not really know what kind of RAM I have...

[AdamW]

hostace: it sounds like you mess with your systems' configuration rather a lot - power saving options, hacking around in /etc/fstab. With this kind of bug it helps if you can reproduce it from a _clean_ install with no manual tweaks, otherwise we're more or less hunting for a needle in a haystack.

The bug would be quite unlikely to be taken as a blocker as we don't support hibernation at all (I actually proposed disabling it for F17, though probably a good thing we didn't, seeing the flak Ubuntu took for doing that). Under the criteria we should 'document' it, but really, the best way to do that that I can see would be a big health warning that hibernation is fundamentally dicey and you probably shouldn't ever do it on a system with data you care a lot about.

[lklaus]

Well, I, for one, actually use it since F14 on my netbooks, even though I had to shortly switch over to ubuntu because of the Intel VGA bug. But my newer Acer works flawlessly with hibernation since f16, and I really depend on it. Actually, I also can't find that many entries defining its usage as "dicey". Any distribution I try to install on my netbook will be tested for hibernation...

Klaus