From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 91268] R6xx freezes with kernel 3.17 and up Date: Wed, 08 Jul 2015 12:15:00 +0000 Message-ID: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1542814759==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 83B196EAFC for ; Wed, 8 Jul 2015 05:15:00 -0700 (PDT) List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1542814759== Content-Type: multipart/alternative; boundary="1436357700.cBDdAA0.24456"; charset="UTF-8" --1436357700.cBDdAA0.24456 Date: Wed, 8 Jul 2015 12:15:00 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable https://bugs.freedesktop.org/show_bug.cgi?id=3D91268 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 ha= rd 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 setu= p 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 displ= ay 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 pa= ge 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=C3=A4nzer 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=C3=A4nzer Reviewed-by: Christian K=C3=B6nig Signed-off-by: Alex Deucher 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. --=20 You are receiving this mail because: You are the assignee for the bug. --1436357700.cBDdAA0.24456 Date: Wed, 8 Jul 2015 12:15:00 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
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 ha=
rd
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 setu=
p 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 displ=
ay
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 pa=
ge
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=C3=A4nzer <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=C3=A4nzer <michel.daenzer@amd.com>
    Reviewed-by: Christian K=C3=B6nig <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: =20=20=20=20=20=20
  • You are the assignee for the bug.
--1436357700.cBDdAA0.24456-- --===============1542814759== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHA6Ly9saXN0 cy5mcmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9kcmktZGV2ZWwK --===============1542814759==--