linux-kernel - Re: PROBLEM: "BUG:" when resuming from suspend-to-ram

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200702280105.35015.rjw@sisk.pl>
Date:	Wed, 28 Feb 2007 01:05:34 +0100
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Kristian Grønfeldt Sørensen <kriller@....dk>
Cc:	Linux kernel mailing list <linux-kernel@...r.kernel.org>
Subject: Re: PROBLEM: "BUG:" when resuming from suspend-to-ram

On Wednesday, 28 February 2007 00:12, Kristian Grønfeldt Sørensen wrote:
> On Tue, 2007-02-27 at 23:34 +0100, Rafael J. Wysocki wrote:
> > On Tuesday, 27 February 2007 23:23, Kristian Grønfeldt Sørensen wrote:
> > > On Tue, 2007-02-27 at 23:04 +0100, Rafael J. Wysocki wrote:
> > > > Hi,
> > > > 
> > > > On Tuesday, 27 February 2007 19:45, Kristian Grønfeldt Sørensen wrote:
> > > > > Hi.
> > > > > 
> > > > > PROBLEM: "BUG:" when resumimg from suspend-to-ram 
> > > > > 	
> > > > > My laptop have a problem with resuming from suspend-to-ram. 
> > > > > It does not occur every time - most of the time, resume works without
> > > > > any problem.at all.
> > > > > 
> > > > > After it occurs, the laptop refuses to go into suspend-to-ram mode until
> > > > > next reboot.
> > > > 
> > > > What do you mean by "refuses"?  
> > > 
> > > As in it does not suspend when i close the lid. It just stays on.
> > 
> > Hm, it doesn't seem to attempt to suspend.  Can you just do
> > "echo mem > /sys/power/state" when it's in that state and see what happens?
> 
> Hmmm. That works. (except for video restore - forgot to save
> vbe-state :-( )

Please see: http://en.opensuse.org/s2ram

> Resume also worked. 

Well, this means that at some point your lid switch driver explodes and doesn't
work any more (the oops trace you've sent suggests something like this).  The
problem seems to be ACPI-related.

Greetings,
Rafael
-
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/