[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1163966016.5744.8.camel@Homer.simpson.net>
Date: Sun, 19 Nov 2006 20:53:36 +0100
From: Mike Galbraith <efault@....de>
To: "Rafael J. Wysocki" <rjw@...k.pl>
Cc: Linus Torvalds <torvalds@...l.org>,
Chuck Ebbert <76306.1226@...puserve.com>,
linux-kernel <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...l.org>
Subject: Re: [patch] PM: suspend/resume debugging should depend on
SOFTWARE_SUSPEND
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
-
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