dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107545] radeon - ring 0 stalled - GPU lockup - SI
Date: Thu, 23 Aug 2018 23:04:11 +0000	[thread overview]
Message-ID: <bug-107545-502-2y3vKLM4bj@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-107545-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 2023 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=107545

--- Comment #7 from Christopher <me@pc-networking-services.com> ---
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 bloated
useless kernel modules.  I use instructions from linuxfromscratch.org to build
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, then
the little circle starts twirling, and after a few seconds the screen flashes,
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, gnome
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 mentioned
here.

If I start gnome on wayland, and then proceed to click on activities and then
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 output 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.org.

The version of Mesa used is: mesa-18.1.5

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2799 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2018-08-23 23:04 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-10 22:59 [Bug 107545] radeon - ring 0 stalled - GPU lockup - SI bugzilla-daemon
2018-08-14 16:52 ` bugzilla-daemon
2018-08-20 17:24 ` bugzilla-daemon
2018-08-20 17:26 ` bugzilla-daemon
2018-08-20 17:27 ` bugzilla-daemon
2018-08-20 17:42 ` bugzilla-daemon
2018-08-23 23:03 ` bugzilla-daemon
2018-08-23 23:04 ` bugzilla-daemon [this message]
2018-08-23 23:06 ` bugzilla-daemon
2018-08-24  7:30 ` bugzilla-daemon
2018-08-24  9:06 ` bugzilla-daemon
2018-08-24 23:34 ` bugzilla-daemon
2018-08-27 10:38 ` bugzilla-daemon
2018-11-14  9:57 ` bugzilla-daemon
2018-11-14  9:59 ` bugzilla-daemon
2018-11-14 10:02 ` bugzilla-daemon
2018-11-14 10:07 ` bugzilla-daemon
2018-11-14 10:07 ` bugzilla-daemon
2018-11-14 10:09 ` bugzilla-daemon
2018-11-15 22:24 ` bugzilla-daemon
2019-11-19  9:34 ` 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-107545-502-2y3vKLM4bj@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;
as well as URLs for NNTP newsgroup(s).