From: "Christian Hoffmann" <email@christianhoffmann.info>
To: 'Benjamin Herrenschmidt' <benh@kernel.crashing.org>,
'Christian Hoffmann' <chrmhoffmann@gmail.com>
Cc: 'Stuffed Crust' <pizza@shaftnet.org>,
"'Rafael J. Wysocki'" <rjw@sisk.pl>,
linux-fbdev-devel@lists.sourceforge.net,
'Christian Hoffmann' <Christian.Hoffmann@wallstreetsystems.com>,
'Andrew Morton' <akpm@osdl.org>,
'LKML' <linux-kernel@vger.kernel.org>,
'Pavel Machek' <pavel@ucw.cz>
Subject: RE: [Linux-fbdev-devel] Fwd: [Suspend-devel] resume not working onacer ferrari 4005 with radeonfb enabled
Date: Fri, 17 Nov 2006 23:02:34 +0100 [thread overview]
Message-ID: <000701c70a94$1d9c2b40$6700a8c0@r2d2> (raw)
In-Reply-To: <1163800768.5826.21.camel@localhost.localdomain>
> -----Original Message-----
> From: Benjamin Herrenschmidt [mailto:benh@kernel.crashing.org]
> Sent: Friday, November 17, 2006 10:59 PM
> To: Christian Hoffmann
> Cc: Stuffed Crust; Rafael J. Wysocki;
> linux-fbdev-devel@lists.sourceforge.net; Christian Hoffmann;
> Andrew Morton; LKML; Pavel Machek
> Subject: Re: [Linux-fbdev-devel] Fwd: [Suspend-devel] resume
> not working onacer ferrari 4005 with radeonfb enabled
>
>
> > When I comment out the rinfo->asleep = 0; line, the machine comes
> > back. So it seems that rinfo struct is still corrupted somehow.
>
> No, I don't think the rinfo is corrupted, I think the chip is
> in a state the driver can't cope with. Possibly related to
> some PCI-Express specific bits or to the memory map.
>
> At this point, we'll need to do register dumps.
Sorry, but how do I do that?
Chris
BTW: yes, it's a PCI-express card.
--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.430 / Virus Database: 268.14.6/536 - Release Date: 11/16/2006
3:51 PM
next prev parent reply other threads:[~2006-11-17 22:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-13 22:08 Fwd: [Suspend-devel] resume not working on acer ferrari 4005 with radeonfb enabled 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-17 22:02 ` Christian Hoffmann [this message]
2006-11-17 22:34 ` Fwd: [Suspend-devel] resume not working onacer " Benjamin Herrenschmidt
2006-11-14 22:36 ` [Linux-fbdev-devel] Fwd: [Suspend-devel] resume not working on acer " Rafael J. Wysocki
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='000701c70a94$1d9c2b40$6700a8c0@r2d2' \
--to=email@christianhoffmann.info \
--cc=Christian.Hoffmann@wallstreetsystems.com \
--cc=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--cc=chrmhoffmann@gmail.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=pizza@shaftnet.org \
--cc=rjw@sisk.pl \
/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).