[ltp] Re: Linux-Thinkpad digest, Vol 1 #1148 - 11 msgs

Tim Nordell linux-thinkpad@linux-thinkpad.org
Sun, 22 Jan 2006 06:24:08 -0600


=46elix,
	I had also submitted a kernel bug report about this same problem a few mon=
ths=20
back.  It would be a trivial fix, but I didn't push for it to be fixed (as =
it=20
didn't matter much to me).  If you'd like to reopen the bug, it's bug #4321=
=20
on bugzilla.kernel.org.  http://bugzilla.kernel.org/show_bug.cgi?id=3D4321 =
=2E  I=20
had discovered this nearly a year ago, March 3rd 2005.

						- Tim Nordell

On Sunday 22 January 2006 05:01, linux-thinkpad-request@linux-thinkpad.org=
=20
wrote:
> Date: Sat, 21 Jan 2006 15:23:27 +0100
> From: "Felix E. Klee" <felix.klee@inka.de>
> To: linux-thinkpad@linux-thinkpad.org
> Subject: [ltp] vlock + suspend to RAM fails
> Reply-To: linux-thinkpad@linux-thinkpad.org
>
> Suspend to RAM trouble:
>
> * When my T41's screen is locked with "vlock -a", then I cannot suspend
> =A0 =A0to RAM anymore ("echo mem > /sys/power/state" triggered by an ACPI=
 lid
> =A0 =A0event).
>
> * Furthermore, when I unlock the system after a failed suspend to RAM
> =A0 =A0attempt, then I cannot do a suspend to RAM anymore, until after a
> =A0 =A0reboot.
>
> * What's also interesting is that, after a failed attempt, when I shut
> =A0 =A0down the system it goes into Suspend to RAM and I have to wake it =
up
> =A0 =A0by pressing the FN key in order to finish up the shutdown. =A0I've=
 not
> =A0 =A0researched this problem properly, though.
>
> Can anyone reproduce the problem? =A0What may be the cause?
>
> My OS: Slackware 10.2
>
> --
> Felix E. Klee