From: Al Boldi <a1426z@gawab.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch] PM: suspend/resume debugging should depend on
Date: Sat, 25 Nov 2006 20:40:45 +0300 [thread overview]
Message-ID: <200611252040.45048.a1426z@gawab.com> (raw)
In-Reply-To: <20061124224130.GA4782@ucw.cz>
Pavel Machek wrote:
> 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.
Ok, but it's normally well understood that when debugging, you should try to
reduce the number of elements to a bare minimum for the problem to surface.
Are you saying that the ACPI STR spec requires a display-card to be attached?
If not, then all efforts should go into fixing STR with a bare minimum
.config without even a display adapter.
Thanks!
--
Al
prev parent reply other threads:[~2006-11-25 17:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-19 18:30 Al Boldi
2006-11-24 22:41 ` Pavel Machek
2006-11-25 17:40 ` Al Boldi [this message]
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=200611252040.45048.a1426z@gawab.com \
--to=a1426z@gawab.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®