From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 91268] R6xx freezes with kernel 3.17 and up
Date: Wed, 08 Jul 2015 12:15:00 +0000 [thread overview]
Message-ID: <bug-91268-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 3457 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=91268
Bug ID: 91268
Summary: R6xx freezes with kernel 3.17 and up
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel@lists.freedesktop.org
Reporter: kap3tan@gmail.com
Something was introduced in kernel 3.17 which makes my GPU to freeze while
playing games. When it happens screen freeze for a few seconds, then it goes
blank for a few seconds, then it comes back with strange artifacts on the
screen, system is basically unresponsive, the only thing you can do is a hard
reset.
With kernels below 3.17 this doesn't happen.
Mesa version also doesn't matter.
Basically same everything, just booting with different kernel makes a
difference.
3.16 is good and 3.17 is bad (also every other kernel above 3.17)
With kernel 3.16 I can play games for days/weeks and bug will not happen.
With 3.17 it can happen anywhere between 15 minutes and few hours.
I did a bisect and it produced this :
git bisect start '--' 'drivers/gpu/drm/radeon'
# good: [19583ca584d6f574384e17fe7613dfaeadcdc4a6] Linux 3.16
git bisect good 19583ca584d6f574384e17fe7613dfaeadcdc4a6
# bad: [bfe01a5ba2490f299e1d2d5508cbbbadd897bbe9] Linux 3.17
git bisect bad bfe01a5ba2490f299e1d2d5508cbbbadd897bbe9
# bad: [03f62abd112d5150b6ce8957fa85d4f6e85e357f] drm/radeon: split PT setup in
more functions
git bisect bad 03f62abd112d5150b6ce8957fa85d4f6e85e357f
# bad: [391bfec33cd4e103274f197924d41ef648b849de] drm/radeon: remove visible
vram size limit on bo allocation (v4)
git bisect bad 391bfec33cd4e103274f197924d41ef648b849de
# good: [da9976206c15178eeae1b4445c9266125bf35b0a] drm/radeon: enable display
scaling on all connectors (v2)
git bisect good da9976206c15178eeae1b4445c9266125bf35b0a
# good: [380670aebfca998bb67b9cf05fc7f28ebeac4b18] drm/radeon: Demote 'BO
allocation size too large' message to debug only
git bisect good 380670aebfca998bb67b9cf05fc7f28ebeac4b18
# bad: [02376d8282b88f07d0716da6155094c8760b1a13] drm/radeon: Allow
write-combined CPU mappings of BOs in GTT (v2)
git bisect bad 02376d8282b88f07d0716da6155094c8760b1a13
# good: [77497f2735ad6e29c55475e15e9790dbfa2c2ef8] drm/radeon: Pass GART page
flags to radeon_gart_set_page() explicitly
git bisect good 77497f2735ad6e29c55475e15e9790dbfa2c2ef8
# first bad commit: [02376d8282b88f07d0716da6155094c8760b1a13] drm/radeon:
Allow write-combined CPU mappings of BOs in GTT (v2)
commit 02376d8282b88f07d0716da6155094c8760b1a13
Author: Michel Dänzer <michel.daenzer@amd.com>
Date: Thu Jul 17 19:01:08 2014 +0900
drm/radeon: Allow write-combined CPU mappings of BOs in GTT (v2)
v2: fix rebase onto drm-fixes
Signed-off-by: Michel Dänzer <michel.daenzer@amd.com>
Reviewed-by: Christian König <christian.koenig@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Currently I'm running kernel with commit before the first bad one :
$ git reset --hard 77497f2735ad6e29c55475e15e9790dbfa2c2ef8
HEAD is now at 77497f2 drm/radeon: Pass GART page flags to
radeon_gart_set_page() explicitly
to test it more thoroughly and see if hang will occur.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 4982 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
next reply other threads:[~2015-07-08 12:15 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-08 12:15 bugzilla-daemon [this message]
2015-07-11 19:20 ` [Bug 91268] R6xx freezes with kernel 3.17 and up bugzilla-daemon
2015-07-12 2:20 ` bugzilla-daemon
2015-07-12 12:37 ` bugzilla-daemon
2015-07-13 14:19 ` bugzilla-daemon
2015-07-13 15:30 ` bugzilla-daemon
2015-07-15 3:30 ` bugzilla-daemon
2015-07-15 12:27 ` bugzilla-daemon
2015-07-15 12:29 ` bugzilla-daemon
2015-07-16 3:52 ` bugzilla-daemon
2015-07-16 13:12 ` bugzilla-daemon
2015-07-16 13:56 ` bugzilla-daemon
2015-07-16 13:58 ` bugzilla-daemon
2015-07-16 14:37 ` bugzilla-daemon
2015-07-16 14:43 ` bugzilla-daemon
2015-07-16 14:49 ` bugzilla-daemon
2015-07-16 15:03 ` bugzilla-daemon
2015-07-16 16:15 ` bugzilla-daemon
2015-07-17 3:06 ` bugzilla-daemon
2015-07-17 3:30 ` bugzilla-daemon
2015-07-24 19:38 ` bugzilla-daemon
2015-07-24 19:42 ` bugzilla-daemon
2015-08-04 10:00 ` bugzilla-daemon
2015-08-04 14:33 ` bugzilla-daemon
2015-10-29 20:34 ` bugzilla-daemon
2015-11-26 8:17 ` bugzilla-daemon
2016-01-29 2:42 ` bugzilla-daemon
2016-03-22 15:54 ` 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-91268-502@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