From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 107545] radeon - ring 0 stalled - GPU lockup - SI Date: Thu, 23 Aug 2018 23:04:11 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1463058886==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 551276E5CE for ; Thu, 23 Aug 2018 23:04:11 +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 --===============1463058886== Content-Type: multipart/alternative; boundary="15350654511.b24A0d30C.29938" Content-Transfer-Encoding: 7bit --15350654511.b24A0d30C.29938 Date: Thu, 23 Aug 2018 23:04:11 +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=3D107545 --- Comment #7 from Christopher --- Hello, I am getting similar issues with regards to fence wait timeouts. However I have narrowed it further to it ONLY happening when gnome is running on xorg. I have over the past month or so rebuilt my system from the ground up. I am NOT using a distro that holds peoples hands with package managers and bloat= ed useless kernel modules. I use instructions from linuxfromscratch.org to bu= ild the entire system from the latest stable sourcecode. After I first boot into gnome, with it running on xorg, as soon as I have logged in and click on activities on the gnome menu and select terminal, th= en the little circle starts twirling, and after a few seconds the screen flash= es, and it momentarily goes to the grey login background, then flashes to what = can only be described as a mini pixal dump, then after a while it flashes back = to the login screen again and you need to login again. At this point, if you click on the drop down list to see the types of login session available, gn= ome on xorg is missing from the list. At this stage I login and going back and activating gnome terminal is successfull, however the dmesg log shows that = it has ring stalled errors, and the dreaded parser error that has been mention= ed here. If I start gnome on wayland, and then proceed to click on activities and th= en on terminal to bring up gnome terminal, even though the circle twirls for a long time after, the terminal window opens almost immediately and the outpu= t of dmesg is free of the ring timeouts. Running xorg by itself using twm with clock and xterm also produces a clean dmesg log. Please find the results attached for both boot tests. By the way this is on one of the latest versions of the 4.18 kernel series available on kernel.or= g. The version of Mesa used is: mesa-18.1.5 --=20 You are receiving this mail because: You are the assignee for the bug.= --15350654511.b24A0d30C.29938 Date: Thu, 23 Aug 2018 23:04:11 +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 # 7 on bug 10754= 5 from Christopher
Hello,

I am getting similar issues with regards to fence wait timeouts.  However I
have narrowed it further to it ONLY happening when gnome is running on xorg.

I have over the past month or so rebuilt my system from the ground up.  I am
NOT using a distro that holds peoples hands with package managers and bloat=
ed
useless kernel modules.  I use instructions from linuxfromscratch.org to bu=
ild
the entire system from the latest stable sourcecode.

After I first boot into gnome, with it running on xorg, as soon as I have
logged in and click on activities on the gnome menu and select terminal, th=
en
the little circle starts twirling, and after a few seconds the screen flash=
es,
and it momentarily goes to the grey login background, then flashes to what =
can
only be described as a mini pixal dump, then after a while it flashes back =
to
the login screen again and you need to login again.  At this point, if you
click on the drop down list to see the types of login session available, gn=
ome
on xorg is missing from the list.  At this stage I login and going back and
activating gnome terminal is successfull, however the dmesg log shows that =
it
has ring stalled errors, and the dreaded parser error that has been mention=
ed
here.

If I start gnome on wayland, and then proceed to click on activities and th=
en
on terminal to bring up gnome terminal, even though the circle twirls for a
long time after, the terminal window opens almost immediately and the outpu=
t of
dmesg is free of the ring timeouts.

Running xorg by itself using twm with clock and xterm also produces a clean
dmesg log.

Please find the results attached for both boot tests.  By the way this is on
one of the latest versions of the 4.18 kernel series available on kernel.or=
g.

The version of Mesa used is: mesa-18.1.5


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