From: Pavel Machek <pavel@ucw.cz>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Ingo Molnar <mingo@elte.hu>,
pm list <linux-pm@lists.linux-foundation.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Alan Stern <stern@rowland.harvard.edu>,
Andrew Morton <akpm@linux-foundation.org>,
Len Brown <lenb@kernel.org>, LKML <linux-kernel@vger.kernel.org>,
Greg KH <gregkh@suse.de>, David Brownell <david-b@pacbell.net>
Subject: Re: [PATCH 0/4] PM: Do not destroy/create devices while suspended (rev. 2)
Date: Thu, 3 Jan 2008 11:56:15 +0100 [thread overview]
Message-ID: <20080103105615.GC1732@elf.ucw.cz> (raw)
In-Reply-To: <200801021428.25164.rjw@sisk.pl>
Hi!
> > > > That way any suspend breakage would be detectable (and bisectable)
> > > > in automated testing - if the resume does not come back after 10-20
> > > > seconds then the test failed.
> > >
> > > Yes, but please note that some systems require user space
> > > manipulations of the graphics adapter for suspend to work and to
> > > detect a breakage of such a system you need to boot it into X and use
> > > s2ram to suspend.
> >
> > yeah, i wouldnt expect graphics mode to come back without quirks. But it
> > should still work fine over the network, right? (which is my main mode
> > of testing anyway)
>
> Well, if the graphics is sufficiently broken, it won't resume at
> all.
Actually, no. Unless you try to boot the bios, it should come up
without graphics.
Hmm... first framebuffer access may kill the machine at that
point... so disable framebuffer...? ;-).
vga=1 and no acpi_sleep options usually does the trick for me. That
should work everywhere, independend of graphics options, AFAICT.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2008-01-03 10:56 UTC|newest]
Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-01 23:32 [PATCH 0/4] PM: Do not destroy/create devices while suspended (rev. 2) Rafael J. Wysocki
2008-01-01 23:32 ` Rafael J. Wysocki
2008-01-01 23:34 ` [PATCH 1/4] PM: Introduce destroy_suspended_device() Rafael J. Wysocki
2008-01-01 23:34 ` Rafael J. Wysocki
2008-01-02 13:33 ` Rafael J. Wysocki
2008-01-02 13:33 ` Rafael J. Wysocki
2008-01-02 16:41 ` Alan Stern
2008-01-02 16:50 ` Rafael J. Wysocki
2008-01-04 22:05 ` Rafael J. Wysocki
2008-01-04 22:05 ` Rafael J. Wysocki
2008-01-04 23:29 ` [RFC][PATCH] PM: Acquire device locks on suspend (was: Re: [PATCH 1/4] PM: Introduce destroy_suspended_device()) Rafael J. Wysocki
2008-01-04 23:29 ` Rafael J. Wysocki
2008-01-05 3:11 ` [PATCH 1/4] PM: Introduce destroy_suspended_device() Alan Stern
2008-01-05 11:55 ` Rafael J. Wysocki
2008-01-05 11:55 ` Rafael J. Wysocki
2008-01-05 3:11 ` Alan Stern
2008-01-02 16:50 ` Rafael J. Wysocki
2008-01-02 16:41 ` Alan Stern
2008-01-01 23:40 ` [PATCH 2/4] PM: Do not destroy/create devices while suspended in msr.c (rev. 2) Rafael J. Wysocki
2008-01-01 23:40 ` Rafael J. Wysocki
2008-01-01 23:40 ` [PATCH 3/4] PM: Do not destroy/create devices while suspended in mce_64.c Rafael J. Wysocki
2008-01-01 23:40 ` Rafael J. Wysocki
2008-01-01 23:42 ` [PATCH 4/4] PM: Do not destroy/create devices while suspended in cpuid.c Rafael J. Wysocki
2008-01-01 23:42 ` Rafael J. Wysocki
2008-01-02 10:52 ` [PATCH 0/4] PM: Do not destroy/create devices while suspended (rev. 2) Ingo Molnar
2008-01-02 10:52 ` Ingo Molnar
2008-01-02 10:52 ` Ingo Molnar
2008-01-02 12:56 ` Rafael J. Wysocki
2008-01-02 12:56 ` Rafael J. Wysocki
2008-01-02 12:56 ` Rafael J. Wysocki
2008-01-02 13:15 ` Ingo Molnar
2008-01-02 13:28 ` Rafael J. Wysocki
2008-01-03 10:56 ` Pavel Machek [this message]
2008-01-03 10:56 ` Pavel Machek
2008-01-02 13:28 ` Rafael J. Wysocki
2008-01-02 14:55 ` Kay Sievers
2008-01-02 14:55 ` Kay Sievers
2008-01-02 16:01 ` Ingo Molnar
2008-01-02 17:54 ` David Brownell
2008-01-02 17:54 ` David Brownell
2008-01-02 18:05 ` Alessandro Zummo
2008-01-02 18:05 ` Alessandro Zummo
2008-01-02 18:12 ` David Brownell
2008-01-02 18:12 ` David Brownell
2008-01-02 18:12 ` David Brownell
2008-01-02 18:34 ` Alessandro Zummo
2008-01-02 18:34 ` Alessandro Zummo
2008-01-02 18:34 ` Alessandro Zummo
2008-01-02 18:05 ` Alessandro Zummo
2008-01-02 20:14 ` Ingo Molnar
2008-01-02 20:29 ` David Brownell
2008-01-02 20:29 ` David Brownell
2008-01-02 20:14 ` Ingo Molnar
2008-01-02 17:54 ` David Brownell
2008-01-02 16:01 ` Ingo Molnar
2008-01-02 17:26 ` David Brownell
2008-01-02 17:26 ` David Brownell
2008-01-02 17:26 ` David Brownell
2008-01-02 20:17 ` Ingo Molnar
2008-01-02 20:17 ` Ingo Molnar
2008-01-02 13:15 ` Ingo Molnar
2008-01-12 0:46 ` Andrew Morton
2008-01-12 0:46 ` Andrew Morton
2008-01-12 0:49 ` Andrew Morton
2008-01-12 0:49 ` Andrew Morton
2008-01-12 0:56 ` Greg KH
2008-01-12 0:56 ` Greg KH
2008-01-12 3:11 ` Alan Stern
2008-01-12 3:11 ` Alan Stern
2008-01-12 3:15 ` Andi Kleen
2008-01-12 3:15 ` Andi Kleen
2008-01-12 3:21 ` Andrew Morton
2008-01-12 3:21 ` Andrew Morton
2008-01-12 4:29 ` Greg KH
2008-01-12 4:29 ` Greg KH
2008-01-12 11:25 ` Rafael J. Wysocki
2008-01-12 11:25 ` Rafael J. Wysocki
2008-01-12 3:11 ` Alan Stern
2008-01-12 11:20 ` Rafael J. Wysocki
2008-01-12 11:20 ` Rafael J. Wysocki
2008-01-12 0:49 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2008-01-01 23:32 Rafael J. Wysocki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080103105615.GC1732@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@linux-foundation.org \
--cc=david-b@pacbell.net \
--cc=gregkh@suse.de \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=mingo@elte.hu \
--cc=rjw@sisk.pl \
--cc=stern@rowland.harvard.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.