From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Rafael J. Wysocki" Subject: Re: [linux-pm] intermittent suspend problem again Date: Wed, 18 Nov 2009 23:13:14 +0100 Message-ID: <200911182313.14092.rjw@sisk.pl> References: <87fx93pwv2.fsf@tac.ki.iif.hu> <200911141952.50030.rjw@sisk.pl> <87r5rwrkqs.fsf@tac.ki.iif.hu> Mime-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Return-path: Received: from ogre.sisk.pl ([217.79.144.158]:44653 "EHLO ogre.sisk.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750772AbZKRWL6 (ORCPT ); Wed, 18 Nov 2009 17:11:58 -0500 In-Reply-To: <87r5rwrkqs.fsf@tac.ki.iif.hu> Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: Ferenc Wagner Cc: linux-pm@lists.linux-foundation.org, Jesse Barnes , Andrew Morton , yakui.zhao@intel.com, LKML , ACPI Devel Maling List , Len Brown On Wednesday 18 November 2009, Ferenc Wagner wrote: > Ferenc Wagner 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). > Side question: If I run s2disk from the init=/bin/bash prompt, the > instrumentation in acpi_enter_sleep_state_prep in drivers/acpi/acpica/hwsleep.c > fires before the "Snapshotting system" phase, but it does not fire if I > hibernate from the full running desktop. (That instrumentation was put > there to investigate the KMS-triggered STR freeze.) What could explain > this? It looks like it uses the "shutdown" method when run with init=/bin/bash, but I don't know why exactly. Thanks, Rafael