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, 25 Feb 2014 16:36:17 +0000	[thread overview]
Message-ID: <bug-75357-502-poCPXVeH75@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-75357-502@http.bugs.freedesktop.org/>


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

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

--- Comment #8 from oogway.droid@gmail.com ---
I can confirm that disabling ColorTiling2D had a positive impact.
There were no black screens on resuming the monitor from powersave mode.
I ran the system for about 14 hours. Then I turned ColorTiling2D back on,
and hit the issue within 5 minutes. The monitor power LED is on when resumed
and I can see the backlight. I tried switching to VT and still a black screen.
I do see (via ssh) the the lines you mention (in comment 7) in my xorg.0.log
when trying to switch VTs. Let me know if you want the full log, following is a
snippet from the log:
...............
[   122.925] (II) RADEON(0): Modeline "1280x1024"x0.0  108.00  1280 1328 1440
1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[   122.925] (II) RADEON(0): Modeline "1920x1080"x60.0  172.80  1920 2040 2248
2576  1080 1081 1084 1118 -hsync +vsync (67.1 kHz e)
[   323.946] (II) AIGLX: Suspending AIGLX clients for VT switch
[   382.915] (II) AIGLX: Resuming AIGLX clients after VT switch
[   382.963] (II) RADEON(0): EDID vendor "DEL", prod id 41055
[   382.963] (II) RADEON(0): Using hsync ranges from config file
[   382.963] (II) RADEON(0): Using vrefresh ranges from config file
[   382.963] (II) RADEON(0): Printing DDC gathered Modelines:
[   382.963] (II) RADEON(0): Modeline "1920x1080"x0.0  148.50  1920 2008 2052
2200  1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP)
......................
......................

And dmesg contains the previously mentioned error:
..........
[   15.485597] IPv6: ADDRCONF(NETDEV_CHANGE): wlp0s26f7u4: link becomes ready
[   95.056067] fuse init (API version 7.22)
[   95.070291] SELinux: initialized (dev fusectl, type fusectl), uses
genfs_contexts
[   95.096897] SELinux: initialized (dev fuse, type fuse), uses genfs_contexts
[  382.917539] radeon 0000:01:00.0: evergreen_surface_check_2d:277 texture
pitch 1920 invalid must be aligned with 512
[  382.917545] radeon 0000:01:00.0: evergreen_cs_track_validate_texture:826
texture invalid 0x1dfc3bc1 0x40000437 0x060a0000 0x00000000 0x80000000
0x800304da
[  382.917548] [drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream !
...........

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

[-- Attachment #1.2: Type: text/html, Size: 3122 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:[~2014-02-25 16: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 [this message]
2014-02-26  4:45 ` bugzilla-daemon
2015-05-23 22:08 ` bugzilla-daemon
2015-05-26  8:36 ` bugzilla-daemon
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-poCPXVeH75@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