From: Ed Tomlinson <edt@aei.ca>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Maling list - DRI developers <dri-devel@lists.freedesktop.org>,
Dave Airlie <airlied@linux.ie>
Subject: Re: [BUG] 3.14-rc6 problems with an R7 260X
Date: Sun, 23 Mar 2014 16:08:37 -0400 [thread overview]
Message-ID: <1707205.THdbAVLWUB@grover> (raw)
In-Reply-To: <33204379.FfpmvHoDUX@grover>
On Monday 10 March 2014 13:29:41 Ed Tomlinson wrote:
> On Monday 10 March 2014 12:38:42 Alex Deucher wrote:
> > On Mon, Mar 10, 2014 at 11:47 AM, Ed Tomlinson <edt@aei.ca> wrote:
> > > Hi,
> > >
> > > I recently added a R7 260X to my system. While the card works with 3.13 its supposed work much better with 14-rc.
> > > This is not the case. My system is unstable without radeon.dpm=0 which was the default in .13. Here are some extracts
> > > from the logs of the latest fun with dpm enabled:
>
> omitted
>
> > > The above type of errors repeat hundreds of times and eventually the display freezes (this box does not have a serial console and it did not check with ssh)
> > >
> > > When X started I did notice some corruption. There are sets of two rectangles about of a height of 2 or 3 mm, width of 25m or so with a second
> > > about a cm below. The often occurs in chomium especially when scrolling. Runing the unigine-sanctuary or unigine-tropics demo/benchmark
> > > programs also produce the above problems and eventually stall.
> > >
> > > The problem is reproducible - I am not that familiar with gpu problems though, what else will help debug this?
> > >
> >
> > Please file a bug at https://bugs.freedesktop.org (Product: DRI,
> > Component: DRM/Radeon) and attach your dmesg output and xorg log.
>
> Filed as bug 75992
>
> Let me know if you want me to test anything or if more info is needed.
This still occurrs with rc7. With dpm enabled X is not usable. It stalls, sometimes with nasty screen corruption, after a few minute. With dpm disabled
its much better (not perfect though).
Ed Tomlinson
next prev parent reply other threads:[~2014-03-23 20:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-10 15:47 [BUG] 3.14-rc6 problems with an R7 260X Ed Tomlinson
2014-03-10 16:38 ` Alex Deucher
2014-03-10 17:29 ` Ed Tomlinson
2014-03-23 20:00 ` Ed Tomlinson
2014-03-23 20:08 ` Ed Tomlinson [this message]
2014-04-14 12:53 ` Ed Tomlinson
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=1707205.THdbAVLWUB@grover \
--to=edt@aei.ca \
--cc=airlied@linux.ie \
--cc=alexdeucher@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--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