From: Matthias Hentges <mailinglisten@hentges.net>
To: Matthew Garrett <mgarrett@chiark.greenend.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: pci-resume patch from 2.6.7-rc2 breakes S3 resume on some machines
Date: Sat, 20 Nov 2004 04:36:00 +0100 [thread overview]
Message-ID: <1100921760.3561.1.camel@mhcln03> (raw)
In-Reply-To: <E1CVLDU-0005jG-00@chiark.greenend.org.uk>
Am Samstag, den 20.11.2004, 02:43 +0000 schrieb Matthew Garrett:
> Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
>
> >> Sorry, that's beyond my abilities. That's why I'm posting here. I'm not
> >> even sure that it's the radeon which is acting up here.
> >
> > Have you tried with radeonfb in your kernel config ?
>
> In the general case, it's harder to resume systems using framebuffers
> than systems that don't. The contortions that are necessary for non-fb
> systems tend to break fb systems (you end up with userspace and the
> kernel both trying to get the graphics hardware back into a sane state),
> so in an ideal world resume would work without any framebuffer support.
Trying to resume with radeonfb or X (DRI or fglrx) causes the machine
to freeze upon a resume.
--
Matthias Hentges
Cologne / Germany
[www.hentges.net] -> PGP welcome, HTML tolerated
ICQ: 97 26 97 4 -> No files, no URL's
My OS: Debian SID. Geek by Nature, Linux by Choice
next prev parent reply other threads:[~2004-11-20 3:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-18 21:05 pci-resume patch from 2.6.7-rc2 breakes S3 resume on some machines Matthias Hentges
2004-11-19 11:55 ` Pavel Machek
2004-11-19 13:56 ` Matthias Hentges
2004-11-19 23:06 ` Benjamin Herrenschmidt
2004-11-20 2:43 ` Matthew Garrett
2004-11-20 3:36 ` Matthias Hentges [this message]
2004-11-20 7:34 ` Benjamin Herrenschmidt
2004-11-20 8:01 ` Matthias Hentges
2004-11-20 22:27 ` Benjamin Herrenschmidt
2004-11-21 8:50 ` Matthias Hentges
2004-11-21 21:39 ` Benjamin Herrenschmidt
2004-11-22 4:34 ` Matthias Hentges
2004-11-22 4:52 ` Benjamin Herrenschmidt
2004-11-20 7:33 ` Benjamin Herrenschmidt
2004-11-20 22:29 ` Pavel Machek
2004-11-19 11:56 ` Pavel Machek
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=1100921760.3561.1.camel@mhcln03 \
--to=mailinglisten@hentges.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mgarrett@chiark.greenend.org.uk \
/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