From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 68571] GPU lockup on AMD Radeon HD6850 with DPM=1
Date: Sat, 29 Mar 2014 10:39:23 +0000 [thread overview]
Message-ID: <bug-68571-2300-0Z6xogRAAO@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-68571-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=68571
--- Comment #35 from kilobug@kilobug.org ---
So, I finally could perform some tests. Two notes first :
1. Meanwhile I upgraded to Mesa 10.1.0.
2. The patch seemed to be already included in the drm-fixes-3.14 branch, so I
just tested with the latest version of that branch.
Now the tests themselves :
1. With dpm=0 and hyperz enabled, the drm-fixes-3.14 branch is stable.
2. With dpm=1 and hyperz enabled on Mesa 10.1, both the drm-fixes-3.14 and the
vanilla 3.13 would freeze at boot (when loading the display manager, lightdm).
3. With dpm=1 and hyperz disabled, they would work for a while, but as
initially described on this bug, after a while they freeze or lockup. The most
secure way I found to trigger a freeze is to play a HD movie using the "gl"
output of mplayer, with that, it freezes in a few minutes.
@Mihai : I'm uploading my build of the drm-fixes branch (which I wrongly named
drmnext, but it's really the drm-fixes branch... sorry, but I didn't rebuild it
just to fix the name...) on http://kilobug.net/debian it's for Debian not for
Ubuntu but it *should* work on Ubuntu too.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2014-03-29 10:39 UTC|newest]
Thread overview: 84+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-11 15:04 [Bug 68571] New: GPU lockup on AMD Radeon HD6850 with DPM=1 bugzilla-daemon
2014-01-11 15:05 ` [Bug 68571] " bugzilla-daemon
2014-01-11 15:53 ` bugzilla-daemon
2014-01-11 15:59 ` bugzilla-daemon
2014-01-12 19:38 ` bugzilla-daemon
2014-01-12 19:39 ` bugzilla-daemon
2014-01-12 19:42 ` bugzilla-daemon
2014-01-12 19:44 ` bugzilla-daemon
2014-01-12 19:45 ` bugzilla-daemon
2014-01-13 17:37 ` bugzilla-daemon
2014-01-15 20:30 ` bugzilla-daemon
2014-01-15 20:31 ` bugzilla-daemon
2014-01-15 21:14 ` bugzilla-daemon
2014-01-16 19:17 ` bugzilla-daemon
2014-01-30 8:50 ` bugzilla-daemon
2014-01-31 0:44 ` bugzilla-daemon
2014-01-31 10:55 ` bugzilla-daemon
2014-01-31 11:09 ` bugzilla-daemon
2014-02-01 15:16 ` bugzilla-daemon
2014-02-01 15:20 ` bugzilla-daemon
2014-02-01 15:21 ` bugzilla-daemon
2014-02-01 15:24 ` bugzilla-daemon
2014-02-01 15:31 ` bugzilla-daemon
2014-02-01 16:38 ` bugzilla-daemon
2014-02-01 20:18 ` bugzilla-daemon
2014-02-02 13:26 ` bugzilla-daemon
2014-02-08 20:54 ` bugzilla-daemon
2014-02-09 23:43 ` bugzilla-daemon
2014-02-10 22:00 ` bugzilla-daemon
2014-02-10 22:23 ` bugzilla-daemon
2014-02-10 22:30 ` bugzilla-daemon
2014-02-11 18:21 ` bugzilla-daemon
2014-03-06 21:33 ` bugzilla-daemon
2014-03-06 23:04 ` bugzilla-daemon
2014-03-07 18:11 ` bugzilla-daemon
2014-03-29 10:39 ` bugzilla-daemon [this message]
2014-03-30 16:57 ` bugzilla-daemon
2014-04-12 8:37 ` bugzilla-daemon
2014-05-04 11:41 ` bugzilla-daemon
2014-05-08 9:39 ` bugzilla-daemon
2014-06-17 5:41 ` bugzilla-daemon
2014-06-19 14:07 ` bugzilla-daemon
2014-06-21 8:18 ` bugzilla-daemon
2014-06-23 21:22 ` bugzilla-daemon
2014-06-23 21:44 ` bugzilla-daemon
2014-06-26 14:26 ` bugzilla-daemon
2014-06-26 14:30 ` bugzilla-daemon
2014-06-26 14:33 ` bugzilla-daemon
2014-06-29 19:11 ` bugzilla-daemon
2014-06-30 22:00 ` bugzilla-daemon
2014-07-01 0:10 ` bugzilla-daemon
2014-07-01 16:09 ` bugzilla-daemon
2014-07-01 16:16 ` bugzilla-daemon
2014-07-01 16:56 ` bugzilla-daemon
2014-07-01 16:57 ` bugzilla-daemon
2014-07-02 18:11 ` bugzilla-daemon
2014-07-02 18:21 ` bugzilla-daemon
2014-07-02 18:28 ` bugzilla-daemon
2014-07-02 18:28 ` bugzilla-daemon
2014-07-02 20:26 ` bugzilla-daemon
2014-07-02 20:28 ` bugzilla-daemon
2014-07-03 7:51 ` bugzilla-daemon
2014-07-03 7:54 ` bugzilla-daemon
2014-07-03 8:10 ` bugzilla-daemon
2014-07-03 20:50 ` bugzilla-daemon
2014-07-05 8:36 ` bugzilla-daemon
2014-07-05 11:46 ` bugzilla-daemon
2014-07-05 11:47 ` bugzilla-daemon
2014-08-02 7:23 ` bugzilla-daemon
2014-08-02 7:24 ` bugzilla-daemon
2014-11-05 2:17 ` bugzilla-daemon
2014-11-05 2:18 ` bugzilla-daemon
2014-11-05 2:19 ` bugzilla-daemon
2015-05-08 13:25 ` bugzilla-daemon
2015-05-08 13:27 ` bugzilla-daemon
2015-05-08 13:33 ` bugzilla-daemon
2015-05-08 13:35 ` bugzilla-daemon
2016-03-26 12:10 ` bugzilla-daemon
2016-09-20 1:27 ` bugzilla-daemon
2016-09-20 1:45 ` bugzilla-daemon
2016-09-20 3:05 ` bugzilla-daemon
2016-09-20 4:54 ` bugzilla-daemon
2016-09-20 5:05 ` bugzilla-daemon
2016-09-20 6:15 ` 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-68571-2300-0Z6xogRAAO@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.