linux-kernel - Re: [patch] PM: suspend/resume debugging should depend on

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]

Message-ID: <20061124224130.GA4782@ucw.cz>
Date:	Fri, 24 Nov 2006 22:41:30 +0000
From:	Pavel Machek <pavel@....cz>
To:	Al Boldi <a1426z@...ab.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [patch] PM: suspend/resume debugging should depend on

On Sun 19-11-06 21:30:11, Al Boldi wrote:
> 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.
> 
> You make it sound like suspend-to-ram is dependent on a correct display 
> adapter to work; it doesn't even work on a machine without a display 
> adapter.
> 
> see http://bugzilla.kernel.org/show_bug.cgi?id=7037

Well, on 'normal' machines, video card is the most common problem.

							Pavel

-- 
Thanks for all the (sleeping) penguins.
-
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/