From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linux-fbdev-devel@lists.sourceforge.net,
LKML <linux-kernel@vger.kernel.org>,
Christian@ogre.sisk.pl, Hoffmann@albercik.sisk.pl,
Christian.Hoffmann@wallstreetsystems.com
Subject: Fwd: [Suspend-devel] resume not working on acer ferrari 4005 with radeonfb enabled
Date: Sat, 11 Nov 2006 00:31:15 +0100 [thread overview]
Message-ID: <200611110031.16173.rjw@sisk.pl> (raw)
Hi,
We've just got the appended report. Could you please have a look at this?
Greetings,
Rafael
---------- Forwarded Message ----------
Subject: [Suspend-devel] resume not working on acer ferrari 4005 with radeonfb enabled
Date: Friday, 10 November 2006 20:44
From: "Christian Hoffmann" <Christian.Hoffmann@wallstreetsystems.com>
To: suspend-devel@lists.sourceforge.net
Hello,
when I have radeonfb enabled, my laptop (X700 ati mobility) doesnt resume
anymore. Screen stays black and nothing works anymore, no capslock light, no
ctrl alt sysreq b etc. I tried all kind of things vbetool, passing
acpi_sleep=s3_bios,s3_mode to the kernel. Nothing seems to work.
You can see dmesg output and lspci -vv output here
http://christianhoffmann.de/temp/radeon.log
http://christianhoffmann.de/temp/lspci.log
Thanks a lot for any input.
Chris
PS: I use kernel 2.18.1 + patch for radeonfb from
http://bugzilla.kernel.org/attachment.cgi?id=9408&action=view
next reply other threads:[~2006-11-10 23:31 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-10 23:31 Rafael J. Wysocki [this message]
2006-11-11 1:49 ` Fwd: [Suspend-devel] resume not working on acer ferrari 4005 with radeonfb enabled Benjamin Herrenschmidt
2006-11-11 2:02 ` Andrew Morton
2006-11-11 13:45 ` [Linux-fbdev-devel] " Stuffed Crust
-- strict thread matches above, loose matches on Subject: below --
2006-11-11 10:17 Christian Hoffmann
2006-11-11 11:36 Christian Hoffmann
2006-11-11 22:49 ` Benjamin Herrenschmidt
2006-11-12 12:13 ` Pavel Machek
2006-11-12 12:28 ` Rafael J. Wysocki
2006-11-11 14:27 Christian Hoffmann
2006-11-11 23:02 Christian Hoffmann
2006-11-13 10:51 Christian Hoffmann
2006-11-13 14:06 ` Rafael J. Wysocki
2006-11-13 17:07 ` Pavel Machek
2006-11-13 22:08 Christian Hoffmann
2006-11-13 23:08 ` Rafael J. Wysocki
2006-11-14 18:51 ` Christian Hoffmann
2006-11-14 21:47 ` Christian Hoffmann
2006-11-14 22:07 ` Benjamin Herrenschmidt
2006-11-15 0:54 ` Christian Hoffmann
2006-11-15 1:48 ` Benjamin Herrenschmidt
2006-11-15 10:09 ` Rafael J. Wysocki
2006-11-16 22:17 ` Christian Hoffmann
2006-11-16 22:44 ` Rafael J. Wysocki
2006-11-17 5:27 ` [Linux-fbdev-devel] " Stuffed Crust
2006-11-17 6:17 ` Benjamin Herrenschmidt
2006-11-17 14:36 ` [Linux-fbdev-devel] " Stuffed Crust
2006-11-17 21:57 ` Benjamin Herrenschmidt
2006-11-17 6:07 ` [Linux-fbdev-devel] " Stuffed Crust
2006-11-17 15:41 ` Stuffed Crust
2006-11-17 20:33 ` Christian Hoffmann
2006-11-17 21:59 ` Benjamin Herrenschmidt
2006-11-14 22:56 ` Pavel Machek
2006-11-14 22:57 ` [Linux-fbdev-devel] " Rafael J. Wysocki
2006-11-14 23:12 ` 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=200611110031.16173.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=Christian.Hoffmann@wallstreetsystems.com \
--cc=Christian@ogre.sisk.pl \
--cc=Hoffmann@albercik.sisk.pl \
--cc=benh@kernel.crashing.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).