On Sat, Oct 07, 2006 at 10:29:25PM +0200, Rafael J. Wysocki wrote: > On Saturday, 7 October 2006 22:16, Stefan Seyfried wrote: > > the additional printf() after the suspend_to_ram() seems to "fix" it. At > > least it did not crash on me for ~30 suspend cycles now. > > However, i'd rather like to understand what the real problem is instead > > of engaging in such cargo cult programming ;-) > > It evidently adds some tiny delay here ...
yes, maybe. However, i am running memtest on the machine over night, maybe it is just a broken memory module :-) > > > Anyway, have you tried to replace suspend_to_ram(snapshot_fd) in s2ram_do > > > with a noop and see what happens? > > > > Then it does not segfault. > > Hm, I'm still wondering if s2both has the same problem ... I tried for ~10 cycles and it had no problem. -- Stefan Seyfried | "Please, just tell people QA / R&D Team Mobile Devices | to use KDE." SUSE LINUX Products GmbH, Nürnberg | -- Linus Torvalds ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Suspend-devel mailing list Suspend-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/suspend-devel
