[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200611232236.58444.rjw@sisk.pl>
Date: Thu, 23 Nov 2006 22:36:56 +0100
From: "Rafael J. Wysocki" <rjw@...k.pl>
To: Mike Galbraith <efault@....de>
Cc: Pavel Machek <pavel@...e.cz>, 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 Thursday, 23 November 2006 22:36, Mike Galbraith wrote:
> On Thu, 2006-11-23 at 13:39 +0000, Pavel Machek wrote:
> > Hi!
> >
> > > > > > 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.
> >
> > Try that -rt kernel, but turn off dyntick/hires timers. Also try
> > hitting keyboard while resuming.
>
> Hmm, I'll try that. Interesting (read odd from my perspective) that the
> rt kernel gets much further. This is pretty hard to look at.
Is your system an i386?
-
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