On Saturday 14 November 2009, Ferenc Wagner wrote: > "Rafael J. Wysocki" <rjw@xxxxxxx> writes: > > > On Friday 13 November 2009, Ferenc Wagner wrote: > >> "Rafael J. Wysocki" <rjw@xxxxxxx> writes: > >> > >>> Yes, echo "core" to /sys/power/pm_test before executing s2disk. > >> > >> It snapshots the system and returns, producing the same console output > >> as s2ram (is this the expected behaviour?) I ran this several times in > >> a loop, and experienced no problems at all. Maybe it depends on the > >> amount of memory used... I saw a freeze saying "99% done" (ie. not > >> 100%), btw. > > > > The number is not always accurate because of rounding errors. I think we can > > safely assume that it always happens after the entire image has been written. > > Probably, "done" isn't output otherwise. > > >> Are other pm_test values meaningful with s2disk? Is this > >> handled explicitly in s2disk, or does simply the kernel act as if it was > >> resumed instead of providing the system image after SNAPSHOT_CREATE_IMAGE? > > > > The latter. > > Ok, I found the code. Are other pm_test values meaningful, or possibly > harmful? They are supposed to work as for suspend. > I think I tried freezer, which resulted in a seemingly perfect > suspend, but the machine didn't try to resume afterwards, but booted > normally instead... So this sounds like there's a bug (will check). > >>> On Wednesday 11 November 2009, Ferenc Wagner wrote: > >>> > >>>> I already did the test for STR (see > >>>> http://bugs.freedesktop.org/show_bug.cgi?id=22126#c3), but will redo > >>>> with the current kernel tonight. > >>> > >>> OK, thanks. > >> > >> No change on this front, FWIW. But rc7 is out now, I'll test again. > > > > Not sure if that's going to work, but yes please test it. > > The KMS related STR freeze (evaluating the _PTS method) is still there. > I'm continuing testing s2disk with the platform method under rc7 (with > some instrumentation added). > > Btw, s2ram -f works fine otherwise (no KMS), and my machine is not in > the whitelist. I'm not sure whether the KMS problem disqualifies it No, it doesn't. > (shall I report it to suspend-devel?), Yes, please. > but it can be identified by: > sys_vendor = "IBM" > sys_product = "1834S5G" > sys_version = "ThinkPad R50e" > bios_version = "1WET90WW (2.10 )" Thanks, Rafael -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
