All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 206017] Kernel 5.4.x unusable with GUI due to crashes (some hard)
Date: Fri, 17 Jan 2020 13:36:51 +0000	[thread overview]
Message-ID: <bug-206017-2300-lL2X1Mz5fP@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-206017-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=206017

Paul (paul.e.hill2@outlook.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |paul.e.hill2@outlook.com

--- Comment #13 from Paul (paul.e.hill2@outlook.com) ---
Hello! 

I am experiencing the same issue on 5.4.10 (Fedora 31, KDE Spin). I'm going to
attempt the 'amdgpu.noretry=0' fix later today.

I made the below bug report with Fedora:
https://ask.fedoraproject.org/t/fedora-kde-amdgpu-issue/5026


Summarized: 
gpu: Radeon Vega 10

Issue: I discovered a lot of these entries within journalctl and dmesg after
gui freezes:

kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft
recovered
kernel: [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences
timed out!

Thank you!

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2020-01-17 13:36 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-30 16:02 [Bug 206017] New: Kernel 5.4.x unusable with GUI due to [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out! bugzilla-daemon
2019-12-30 16:03 ` [Bug 206017] " bugzilla-daemon
2020-01-01 13:48 ` bugzilla-daemon
2020-01-01 14:31 ` bugzilla-daemon
2020-01-03  6:06 ` bugzilla-daemon
2020-01-04  4:53 ` bugzilla-daemon
2020-01-04  5:45 ` [Bug 206017] Kernel 5.4.x unusable with GUI due to hard crashes bugzilla-daemon
2020-01-04  5:53 ` [Bug 206017] Kernel 5.4.x unusable with GUI due to crashes (some hard) bugzilla-daemon
2020-01-05 11:53 ` bugzilla-daemon
2020-01-05 12:22 ` bugzilla-daemon
2020-01-05 15:38 ` bugzilla-daemon
2020-01-06 11:52 ` bugzilla-daemon
2020-01-06 12:02 ` bugzilla-daemon
2020-01-08 15:23 ` bugzilla-daemon
2020-01-10 16:56 ` bugzilla-daemon
2020-01-17 13:36 ` bugzilla-daemon [this message]
2020-01-18 23:51 ` bugzilla-daemon
2020-01-20 15:07 ` bugzilla-daemon
2020-01-20 15:14 ` bugzilla-daemon
2020-04-20  9:54 ` bugzilla-daemon
2020-05-17 12:55 ` bugzilla-daemon
2020-06-17 10:05 ` bugzilla-daemon
2020-06-17 13:50 ` bugzilla-daemon
2020-08-20 12:22 ` 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-206017-2300-lL2X1Mz5fP@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.