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]
Message-Id: <1180740714.9412.73.camel@nigel.suspend2.net>
Date:	Sat, 02 Jun 2007 09:31:54 +1000
From:	Nigel Cunningham <nigel@...el.suspend2.net>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
Cc:	Olaf Dietsche <olaf+list.linux-acpi@...fdietsche.de>,
	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.

Hi.

On Sat, 2007-06-02 at 00:37 +0200, Rafael J. Wysocki wrote:
> On Saturday, 2 June 2007 00:17, Olaf Dietsche wrote:
> > "Rafael J. Wysocki" <rjw@...k.pl> writes:
> > 
> > > On Friday, 1 June 2007 23:12, Olaf Dietsche wrote:
> > >> "Rafael J. Wysocki" <rjw@...k.pl> writes:
> > >> 
> > >> > On Friday, 1 June 2007 22:27, Olaf Dietsche wrote:
> > >> >> When I resume, everything seems to come up (fan becomes busy, disk and
> > >> >> dvd spin up for a short time),
> > >> >
> > >> > Hmm, what about the screen?
> > >> 
> > >> When the laptop is dead, screen remains black.
> > >> 
> > >> When I skip acpi_enter_sleep_state(), the screen works like everything
> > >> else.
> > >
> > > I think you should try s2ram (http://en.opensuse.org/s2ram) as the first step.
> > 
> > It doesn't work. I tried all options "s2ram -f (-s, -p, -m, -r, -a 1, -a 2,
> > -a 3)" one after the other.
> > 
> > Since the screen (or any other device) works without problems, when I
> > skip acpi_enter_sleep_state(), I don't think it's screen related.
> 
> No, it might be, actually.  If you skip acpi_enter_sleep_state(), your machine
> doesn't really suspend, so in fact you only confirm that your drivers implement
> .suspend() and .resume() hooks correctly.

Actually, you don't even confirm that. Chips that would be powered down
by entering the sleep state will not be powered down in this scenario,
so failures to properly reinitialise them in resume routines won't be
noticed.

Regards,

Nige

Download attachment "signature.asc" of type "application/pgp-signature" (190 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ