From: Andy Furniss <adf.lists@gmail.com>
To: Alex Deucher <alexdeucher@gmail.com>,
dri-devel@lists.freedesktop.org, deathsimple@vodafone.de
Cc: Alex Deucher <alexander.deucher@amd.com>,
matthias.graf@st.ovqu.de, bp@alien8.de, stable@vger.kernel.org
Subject: Re: [PATCH] drm/radeon: disable dpm on rv770 by default
Date: Sat, 19 Apr 2014 19:02:46 +0100 [thread overview]
Message-ID: <5352BA46.6060503@gmail.com> (raw)
In-Reply-To: <1397826491-18837-1-git-send-email-alexander.deucher@amd.com>
Alex Deucher wrote:
> There seem to be stability issues on a number of cards.
>
> bugs: https://bugs.freedesktop.org/show_bug.cgi?id=76286
> https://bugzilla.redhat.com/show_bug.cgi?id=1085785
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741619
Well TBH I don't know whether the following is useful info or not - it
could just be an unrelated waste of your time.
I have run my 4890 with dpm=1 from when it first appeared without issue
till recently.
As in the bug above I can't now use two screens - but the thing is, I
use a (getting old) LFS, I don't use the TV that much, but when I
noticed the issue I tried to bisect and I reached the commit after my
working start point.
It turned out that my working was the last kernel I compiled with GCC
4.6.3. I had upgraded to GCC 4.8.2 and no kernel built with that can
handle 2 screens without locking, no sysrq, no network but very rarely
may unlock for a short while (did a dmesg when this happened, nothing
unusual logged then it locked again).
I built my GCC 4.6.3 again and built the same recent kernel (I run drm
next or
fixes) and I have so far not been able to lock it with 2 screens.
Of course it could just be something on my LFS is too old for recent
GCC, or because I don't use TV much I am being lucky with 4.6.3.
I will when I get time build 4.8.2 again and see if dpm=0 works for me.
next prev parent reply other threads:[~2014-04-19 18:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-18 13:08 [PATCH] drm/radeon: disable dpm on rv770 by default Alex Deucher
2014-04-19 10:12 ` Christian König
2014-04-19 18:02 ` Andy Furniss [this message]
2014-04-20 1:14 ` Alex Deucher
2014-04-20 16:44 ` Andy Furniss
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=5352BA46.6060503@gmail.com \
--to=adf.lists@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=alexdeucher@gmail.com \
--cc=bp@alien8.de \
--cc=deathsimple@vodafone.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=matthias.graf@st.ovqu.de \
--cc=stable@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