dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 75357] Barts (HD6850): Failure in evergreen_surface_check_2d
Date: Tue, 26 May 2015 08:36:08 +0000	[thread overview]
Message-ID: <bug-75357-502-jNivA3CZhd@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-75357-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1726 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=75357

--- Comment #11 from Michel Dänzer <michel@daenzer.net> ---
(In reply to Nix from comment #10)
> FWIW, I have just started seeing behaviour very similar to this, also with an
> HD6850, though it is probably a distinct bug because all the software
> versions involved are very different.

So it would probably be better to file your own report.


> This happened after closely-adjoined upgrades of the kernel (from 3.19 to
> 4.0.3), the X server (from 1.15.1, yes, I know, it's because of the security
> holes I finally upgraded, to 1.17.1), the ATI driver (from 7.3.0-26 to
> 7.5.0.68, all "git describe" output from the unmodified trunk), Mesa (from
> 10.2.6 to 10.5.5), and LLVM (from 3.3 to 3.5.2), so the fault could, alas, in
> theory lie in any or all of these.

It would be great if you could narrow that down a bit. The r600g driver doesn't
use LLVM, so that's probably not it. I agree it's most likely between Mesa or
the kernel, or maybe xf86-video-ati.


> Glamor is not in use.

Have you tried glamor to see if it happens with that as well?

Does

    Option "ColorTiling2D" "off"

in /etc/X11/xorg.conf or the environment variable R600_DEBUG=no2d (or even
R600_DEBUG=notiling) for chromium work around the problem?


> dpm is, and has been working flawlessly thank you very much, cutting my
> desktop's power consumption from 130W to 90W :) over the last year that's
> saved at least the price of the beer I owe you for the dpm work, Michel :)

Sounds great, but I haven't done any DPM work, I think that beer would have to
go to Alex. :)

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2742 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2015-05-26  8:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-22  8:11 [Bug 75357] New: Barts (HD6850): Failure in evergreen_surface_check_2d bugzilla-daemon
2014-02-22  8:13 ` [Bug 75357] " bugzilla-daemon
2014-02-22  8:18 ` bugzilla-daemon
2014-02-22  8:22 ` bugzilla-daemon
2014-02-22  8:24 ` bugzilla-daemon
2014-02-24  6:06 ` bugzilla-daemon
2014-02-24 14:18 ` bugzilla-daemon
2014-02-25  7:04 ` bugzilla-daemon
2014-02-25 16:36 ` bugzilla-daemon
2014-02-26  4:45 ` bugzilla-daemon
2015-05-23 22:08 ` bugzilla-daemon
2015-05-26  8:36 ` bugzilla-daemon [this message]
2015-05-26  9:53 ` bugzilla-daemon
2015-07-06  8:27 ` bugzilla-daemon
2015-07-06  8:50 ` bugzilla-daemon

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=bug-75357-502-jNivA3CZhd@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.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