From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 101672] radeonsi: 3D engines causing frequent GPU lockups Date: Mon, 24 Jul 2017 11:59:00 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1740716752==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 3443B6E267 for ; Mon, 24 Jul 2017 11:59:00 +0000 (UTC) In-Reply-To: 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 --===============1740716752== Content-Type: multipart/alternative; boundary="15008975400.8495b.13928"; charset="UTF-8" --15008975400.8495b.13928 Date: Mon, 24 Jul 2017 11:59:00 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D101672 --- Comment #9 from MirceaKitsune --- Created attachment 132863 --> https://bugs.freedesktop.org/attachment.cgi?id=3D132863&action=3Dedit Screenshot of sys/kernel/debug/dri/0 The exact same story repeats with Mesa 17.1.5 (as with 17.1.4); The release notes claim that a core crash has been fixed, yet inexplicably this freeze persists after updating to the latest version. Something very unusual happened however: I rebooted my machine and started testing under Xonotic. After about 10 minutes of playing I got my first fre= eze, however it did not block the machine; Only Xonotic itself crashed (image fr= oze and sound died), so I was able to alt-tab switch to my desktop... the system detected that the process was unresponsive and killed it, after which I cou= ld notice that it did NOT eat up any CPU or memory while it was frozen. I test= ed again and after about 15 minutes I got another freeze... this time though it froze the entire computer as usual (including taking down SSH). I preformed the suggested test of monitoring the files in sys/kernel/debug/dri/0 through my SSH connection, to check whether this mig= ht be caused by a vram leak. The most relevant file in there was radeon_vram, which seems to have 2.0 GB at all times (makes sense as that's the amount of vram on my video card). I used the command "watch -n 1 cat /sys/kernel/debug/dri/0/radeon_vram" to monitor it, but that has not printed any changes in the file itself. Adding a screenshot of that directory and i= ts contents. --=20 You are receiving this mail because: You are the assignee for the bug.= --15008975400.8495b.13928 Date: Mon, 24 Jul 2017 11:59:00 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Commen= t # 9 on bug 10167= 2 from MirceaKitsune 
Created att=
achment 132863 [details]
Screenshot of sys/kernel/debug/dri/0

The exact same story repeats with Mesa 17.1.5 (as with 17.1.4); The release
notes claim that a core crash has been fixed, yet inexplicably this freeze
persists after updating to the latest version.

Something very unusual happened however: I rebooted my machine and started
testing under Xonotic. After about 10 minutes of playing I got my first fre=
eze,
however it did not block the machine; Only Xonotic itself crashed (image fr=
oze
and sound died), so I was able to alt-tab switch to my desktop... the system
detected that the process was unresponsive and killed it, after which I cou=
ld
notice that it did NOT eat up any CPU or memory while it was frozen. I test=
ed
again and after about 15 minutes I got another freeze... this time though it
froze the entire computer as usual (including taking down SSH).

I preformed the suggested test of monitoring the files in
sys/kernel/debug/dri/0 through my SSH connection, to check whether this mig=
ht
be caused by a vram leak. The most relevant file in there was radeon_vram,
which seems to have 2.0 GB at all times (makes sense as that's the amount of
vram on my video card). I used the command "watch -n 1 cat
/sys/kernel/debug/dri/0/radeon_vram" to monitor it, but that has not p=
rinted
any changes in the file itself. Adding a screenshot of that directory and i=
ts
contents.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15008975400.8495b.13928-- --===============1740716752== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============1740716752==--