lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sun, 03 Jun 2007 23:20:41 +0200
From:	Olaf Dietsche <olaf+list.linux-acpi@...fdietsche.de>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
Cc:	linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org,
	pm list <linux-pm@...ts.linux-foundation.org>
Subject: Re: [2.6.22-rc3][ACPI?] Resume from s2r doesn't work.

"Rafael J. Wysocki" <rjw@...k.pl> writes:

> Second, you can use PM_TRACE (Documentation/power/s2ram.txt) to find the
> place where it really fails.

First I augmented my minimal config kernel with some TRACE_RESUME()s:

--- a/kernel/power/main.c	2007-05-27 23:48:05.000000000 +0200
+++ b/kernel/power/main.c	2007-06-03 22:28:46.000000000 +0200
@@ -223,6 +223,7 @@
 	pr_debug("PM: Finishing wakeup.\n");
 	suspend_finish(state);
  Unlock:
+	TRACE_RESUME(error);
 	mutex_unlock(&pm_mutex);
 	return error;
 }
@@ -303,6 +304,7 @@
 		error = enter_state(state);
 	else
 		error = -EINVAL;
+	TRACE_RESUME(error);
 	return error ? error : n;
 }
 
With this test script:

#! /bin/sh

sync
echo 1 >/sys/power/pm_trace
echo mem >/sys/power/state
shutdown -rn now

I got alternating
  hash matches drivers/base/power/resume.c:58
and
  hash matches kernel/power/main.c:307

> First, you can check if the patch
>
> http://www.sisk.pl/kernel/hibernation_and_suspend/2.6.22-rc3/patches/20-ACPI-preserve-the-ebx-value-in-acpi_copy_wakeup_routine.patch

Then I applied this patch, but it doesn't change anything.

But either way the script never reaches "shutdown -rn now". So, it
seems, that my laptop does a full resume every other reboot, but it
never returns to userspace.

> Also, please read Documentation/power/basic-pm-debugging.txt .

Regards, Olaf.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ