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:	Tue, 19 Feb 2008 11:11:16 +0100
From:	Pavel Machek <pavel@....cz>
To:	David Brownell <david-b@...bell.net>
Cc:	Ingo Molnar <mingo@...e.hu>, rjw@...k.pl,
	linux-pm@...ts.linux-foundation.org, linux-kernel@...r.kernel.org,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [patch] suspend/resume self-test

On Mon 2008-02-18 12:16:24, David Brownell wrote:
> On Monday 18 February 2008, Ingo Molnar wrote:
> > 
> > * David Brownell <david-b@...bell.net> wrote:
> > 
> > > > >   - Includes a command line parameter, which needs work yet ... it
> > > > >     currently turns this test off, but it should also let the target
> > > > >     state be specified (and maybe even default to "no test").
> > > 
> > > I think "no test" should be the default; STR working sanely on x86 is 
> > > unfortunately too much a surprise.  Someone more active in PM testing 
> > > should update that.
> > 
> > All i'm asking for is to make the self-test easily accessible. Not for 
> > it to blow up in the face of users who do not ask for it.
> 
> I'm all for that, but also I don't want to see it blow up regularly
> in the face of people who just enable all the selftest options.  The
> other tests have a much better expectation of working "by default".

> > And, at least to me, there seems to be a rather apparent correlation 
> > between "suspend/resume regressions caught as early as possible" and the 
> > future, desired state of: "STR working sanely on x86" ;-)
> 
> Thing is, this will catch not just regressions ... but cases where
> STR never worked in the first place.  Video problems, etc.  Also
> various system startup races, as in the PCMCIA and MMC/SD/SDIO
> cases I noted.

David is right here. At minimum, s2ram needs acpi_sleep=... options to
tell it how to set up the video. That is not issue for you, but it
means we should not be doing it by default.
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
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