On Wed, Mar 23, 2011 at 11:11 PM, Rafael J. Wysocki <rjw@xxxxxxx> wrote: > On Wednesday, March 23, 2011, richard -rw- weinberger wrote: >> 2011/3/23 Rafael J. Wysocki <rjw@xxxxxxx>: >> > On Wednesday, March 23, 2011, richard -rw- weinberger wrote: >> >> Hi, >> >> >> >> I'm facing a very strange problem on my netbook (Lenovo Ideapad S10) >> >> running Linux 2.6.37.4. >> >> After resuming from s2disk some files are corrupted. >> >> But when I reboot my netbook everything seems good again. >> >> >> >> When I saw the problem the first time the ls command segfaulted always. >> >> I did a reboot and it worked again. >> >> >> >> A few days later zypper crashed. After a reboot it worked again. >> >> And today ssh crashed. I looked a bit closer and saw it crashed >> >> somewhere within libcrypto. >> >> So I made copy libcrypto and rebooted. >> >> After the reboot ssh worked again but libcrypto and the copy of it hat >> >> a different sha1 sum! >> >> WTF?! >> >> >> >> Is this a known issue? >> > >> > No. >> > >> >> dmesgs and config are attached. >> >> >> >> The used distribution is openSUSE 11.4 with suspend-0.80.20100129-7.1 >> >> (default from suse). >> >> I'm using ext3 as root filesystem. >> >> What else do you need? >> > >> > Whatever you can do to narrow down the problem. At the moment I only know >> > that it's there. >> >> I can reproduce the problem now. >> After ~20 suspend and resume iterations aide finds corrupted files in /lib/. >> It's always a very basic lib like libcrypto, libglib which is used all >> the time on my system. > > Those files are never intentionally modified, right? > >> Maybe it's an issue like this one? >> https://lkml.org/lkml/2010/12/2/339 > > It might have if that patch hadn't been merged before 2.6.37. > > Is the system 32-bit or 64-bit? It's a 32-bit system. cmp shows that the corrupted files differ in many bytes (not scattered). The corrupted bytes are always 0 or 252. > Rafael > -- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > -- Thanks, //richard _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
