From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [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!
Date: Mon, 30 Dec 2019 16:02:23 +0000 [thread overview]
Message-ID: <bug-206017-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=206017
Bug ID: 206017
Summary: Kernel 5.4.x unusable with GUI due to
[drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR*
Waiting for fences timed out!
Product: Drivers
Version: 2.5
Kernel Version: 5.4.x
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: udovdh@xs4all.nl
Regression: No
AMD Ryzen 5 3400G with Radeon Vega Graphics on Gigabyte X570 AORUS PRO, running
Fedora 31, kernel.org kernels, git mesa, etc
After booting into 5.4, soon the GUI freezes, e.g. right when I start Firefox.
On 5.3.18 it takes days to crash amdgpu.
Soft recovery does not help.
5.3.18 is EOLed so 5.4 issues need priority:
(..)
[ 12.884828] pps pps0: new PPS source serial0
[ 12.884832] pps pps0: source "/dev/ttyS0" added
[ 12.898511] it87: it87 driver version <not provided>
[ 12.898635] it87: Found IT8792E/IT8795E chip at 0xa60, revision 3
[ 12.898675] it87: Beeping is supported
[ 14.244524] igb 0000:04:00.0: changing MTU from 1500 to 7200
[ 17.328845] igb 0000:04:00.0 eth0: igb: eth0 NIC Link is Up 1000 Mbps Full
Duplex, Flow Control: RX/TX
[ 17.331973] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 18.564142] io scheduler mq-deadline registered
[ 22.352636] igb 0000:04:00.0 eth0: igb: eth0 NIC Link is Up 1000 Mbps Full
Duplex, Flow Control: RX/TX
[ 31.464130] fuse: init (API version 7.31)
[ 75.198868] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for
fences timed out!
[ 80.318799] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but
soft recovered
--
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
next reply other threads:[~2019-12-30 16:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-30 16:02 bugzilla-daemon [this message]
2019-12-30 16:03 ` [Bug 206017] Kernel 5.4.x unusable with GUI due to [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out! 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
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@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox