From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ferenc Wagner Subject: Re: intermittent suspend problem again Date: Thu, 19 Nov 2009 13:00:00 +0100 Message-ID: <877htmragv.fsf@tac.ki.iif.hu> References: <87fx93pwv2.fsf@tac.ki.iif.hu> <200911141952.50030.rjw@sisk.pl> <87r5rwrkqs.fsf@tac.ki.iif.hu> <200911182313.14092.rjw@sisk.pl> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Ferenc Wagner's message of "Wed\, 18 Nov 2009 23\:55\:01 +0100" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-pm-bounces@lists.linux-foundation.org Errors-To: linux-pm-bounces@lists.linux-foundation.org To: "Rafael J. Wysocki" Cc: LKML , Jesse Barnes , yakui.zhao@intel.com, ACPI Devel Maling List , linux-pm@lists.linux-foundation.org, Andrew Morton List-Id: linux-pm@vger.kernel.org Ferenc Wagner writes: > "Rafael J. Wysocki" writes: > >> On Wednesday 18 November 2009, Ferenc Wagner wrote: >> >>> Ferenc Wagner writes: >>> >>> 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 for the tip, I'll check this too. While looking into this, I found a reproducible kernel panic: 1. boot with init=/bin/bash 2. mount /usr; swapon -a 3. plug in a USB pendrive 4. s2disk (machine goes to sleep) 5. power on, proceed with resuming, press Enter to cancel resume pause 6. ACPI: Hardware changed while hibernated, cannot resume! Kernel panic - not syncing: ACPI S4 hardware signature mismatch Does it make sense? -- Thanks, Feri.