On Saturday 28 November 2009, Ferenc Wagner wrote: > "Rafael J. Wysocki" <rjw@xxxxxxx> writes: > > > On Wednesday 18 November 2009, Ferenc Wagner wrote: > > > >> Ferenc Wagner <wferi@xxxxxxx> writes: > >> > >>> Since I've instrumented s2disk and the hibernation path, no freeze > >>> happened during hibernating the machine. > >> > >> Not until I removed the delays from hibernation_platform_enter(), which > >> were put there previously to get step-by-step feedback. Removing them > >> again resulted in a freeze in short course, maybe just two hibernations > >> later. The instrumentation shows it stuck in dpm_suspend_start(PMSG_HIBERNATE). > >> Does it mean that some device driver is at fault? > > > > A driver or one of the platform hooks. > > > >> I'll check if it always fails at the same point (although tracing into > >> dpm_suspend_start isn't pure fun because of the multitude of devices it > >> loops over). Is there any way to get printk output from that phase? > > > > Compile with CONFIG_PM_VERBOSE (it does mean exactly that). > > The last message now was: > > e100: 0000:02:08.0: hibernate, may wakeup > > Looks like hibernating the e100 driver is unstable. Can you verify that by trying to hibernate without the e100 driver? 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