From: Alex Deucher <alexdeucher@gmail.com>
To: Alex Chiang <achiang@hp.com>
Cc: Xiaotian Feng <xtfeng@gmail.com>,
rjw@sisk.pl, Dave Airlie <airlied@redhat.com>,
dri-devel@lists.sourceforge.net,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: radeon 4830 corruption after resume
Date: Tue, 15 Dec 2009 10:19:49 -0500 [thread overview]
Message-ID: <a728f9f90912150719x7db56ee7p589c0f4fc2594b2d@mail.gmail.com> (raw)
In-Reply-To: <20091215145737.GA8209@ldl.fc.hp.com>
On Tue, Dec 15, 2009 at 9:57 AM, Alex Chiang <achiang@hp.com> wrote:
> * Alex Deucher <alexdeucher@gmail.com>:
>>
>> As Dave asked previously, is this a regression? I.e., did s/r work at
>> some point in the past and if so when?
>
> I'm not sure, as I just received the machine a few days ago.
>
> I can try some older kernels, but part of my issue is not knowing
> how all the pieces fit together. How can I tell if I'm supposed
> to be bisecting the kernel or X or something else, given my
> symptoms?
First try s/r without X running and see if it works ok. Then try s/r
from a VT other than the one X is on. Finally, try s/r with the DRI
disabled (i.e., Option "DRI" "False" in the device section of your
config). Also for non-kms s/r, you may have to fiddle with vbetool on
resume to post your card. Report back with the results and we can go
from there.
Alex
prev parent reply other threads:[~2009-12-15 15:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-14 2:30 Alex Chiang
2009-12-14 2:52 ` Dave Airlie
2009-12-14 3:11 ` Alex Chiang
2009-12-14 5:28 ` Xiaotian Feng
2009-12-15 5:40 ` Alex Chiang
2009-12-15 14:52 ` Alex Deucher
2009-12-15 14:57 ` Alex Chiang
2009-12-15 15:19 ` Alex Deucher [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=a728f9f90912150719x7db56ee7p589c0f4fc2594b2d@mail.gmail.com \
--to=alexdeucher@gmail.com \
--cc=achiang@hp.com \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=xtfeng@gmail.com \
/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®