From: Mike Galbraith <efault@gmx.de>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Linus Torvalds <torvalds@osdl.org>,
Chuck Ebbert <76306.1226@compuserve.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [patch] PM: suspend/resume debugging should depend on SOFTWARE_SUSPEND
Date: Sun, 19 Nov 2006 20:53:36 +0100 [thread overview]
Message-ID: <1163966016.5744.8.camel@Homer.simpson.net> (raw)
In-Reply-To: <200611191958.15152.rjw@sisk.pl>
On Sun, 2006-11-19 at 19:58 +0100, Rafael J. Wysocki wrote:
> On Sunday, 19 November 2006 18:52, Mike Galbraith wrote:
> > On Sun, 2006-11-19 at 09:33 -0800, Linus Torvalds wrote:
> > >
> > > On Sun, 19 Nov 2006, Chuck Ebbert wrote:
> > > >
> > > > When doing 'make oldconfig' we should ask about suspend/resume
> > > > debug features when SOFTWARE_SUSPEND is not enabled.
> > >
> > > That's wrong.
> > >
> > > I never use SOFTWARE_SUSPEND, and I think the whole concept is totally
> > > broken.
> > >
> > > Sane people use suspend-to-ram, and that's when you need the suspend and
> > > resume debugging.
> >
> > Here I am wishing I had the _opportunity_ to be sane. With my ATI X850
> > AGP card, I have no choices except swsusp or reboot.
>
> Have you tried s2ram (http://en.opensuse.org/S2ram)?
Cool. That shows potential. On an 2.6.19-rc6-rt4 kernel, it looked
like it _might_ have eventually gotten past boot. At one line of kernel
output every ~10 seconds though, I gave up. Virgin 2.6.19-rc6 went
panic with a black screen... have options, will tinker.
(i _was_ quite content with swsusp, but now i want it all;)
Thanks,
-Mike
next prev parent reply other threads:[~2006-11-19 19:51 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-19 8:18 [patch] PM: suspend/resume debugging should depend on SOFTWARE_SUSPEND Chuck Ebbert
2006-11-19 8:29 ` Pavel Machek
2006-11-19 17:33 ` Linus Torvalds
2006-11-19 17:44 ` Rafael J. Wysocki
2006-11-19 18:21 ` Linus Torvalds
2006-11-19 18:55 ` Rafael J. Wysocki
2006-11-19 19:54 ` Linus Torvalds
2006-11-19 21:25 ` Rafael J. Wysocki
2006-11-19 23:21 ` Linus Torvalds
2006-11-19 22:59 ` Romano Giannetti
2006-11-20 22:17 ` Theodore Tso
2006-11-21 2:02 ` Matthew Garrett
2006-11-23 13:28 ` Pavel Machek
2006-11-19 17:52 ` Mike Galbraith
2006-11-19 18:25 ` Linus Torvalds
2006-11-19 19:02 ` Mike Galbraith
2006-11-19 19:55 ` Linus Torvalds
2006-11-19 18:58 ` Rafael J. Wysocki
2006-11-19 19:53 ` Mike Galbraith [this message]
2006-11-23 13:39 ` Pavel Machek
2006-11-23 21:36 ` Mike Galbraith
2006-11-23 21:36 ` Rafael J. Wysocki
2006-11-24 6:39 ` Mike Galbraith
2006-11-24 18:08 ` Linus Torvalds
2006-11-25 0:22 ` Mike Galbraith
2006-11-25 14:11 ` Mike Galbraith
2006-11-25 17:12 ` Rafael J. Wysocki
2006-11-26 4:53 ` Mike Galbraith
2006-11-28 10:01 ` Mike Galbraith
2006-11-29 10:21 ` Mike Galbraith
2006-11-29 10:30 ` [rfc patch] " Mike Galbraith
2006-11-29 14:15 ` Pavel Machek
2006-11-29 19:49 ` Andrew Morton
2006-11-29 20:05 ` Mike Galbraith
2006-11-19 21:41 ` Nigel Cunningham
2006-11-19 22:04 ` Christer Weinigel
2006-12-03 21:40 ` Kyle Moffett
2006-12-04 10:50 ` Pavel Machek
2006-12-04 13:56 ` Henrique de Moraes Holschuh
2006-11-22 15:23 ` Adrian Bunk
2006-11-22 15:42 ` Alan
2006-11-24 23:40 ` Pavel Machek
2006-11-25 16:08 ` Alan
2006-11-25 17:18 ` Rafael J. Wysocki
2006-11-26 20:52 ` Pavel Machek
2006-11-22 23:05 ` Mark Lord
[not found] <fa.U3NcOE+DHLOUMSq6HkaGglGl7hQ@ifi.uio.no>
[not found] ` <fa.YMVQ6sabKF/IkEHUCoiQoxoHWZA@ifi.uio.no>
[not found] ` <fa.c5fVj98hBgqoUumwbA9jymiSXr8@ifi.uio.no>
[not found] ` <fa.zMBHTAXYfXNe2TVX89s3qsC2HRk@ifi.uio.no>
[not found] ` <fa.yA6cvuiGulIRQfqY+E9joR2nWog@ifi.uio.no>
[not found] ` <fa.bo0iOgKqELDD50VEZpxeUpzPsMg@ifi.uio.no>
2006-11-26 7:11 ` Robert Hancock
2006-11-26 10:13 ` Rafael J. Wysocki
2006-11-26 20:30 ` Robert Hancock
2006-11-27 13:51 ` Matthew Garrett
2006-12-03 12:49 ` Rafael J. Wysocki
2006-11-27 12:20 ` Stefan Seyfried
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=1163966016.5744.8.camel@Homer.simpson.net \
--to=efault@gmx.de \
--cc=76306.1226@compuserve.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=torvalds@osdl.org \
/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.