dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 213145] AMDGPU resets, timesout and crashes after "*ERROR* Waiting for fences timed out!"
Date: Mon, 07 Jun 2021 19:41:11 +0000	[thread overview]
Message-ID: <bug-213145-2300-sigzrhOzWN@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-213145-2300@https.bugzilla.kernel.org/>

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

--- Comment #7 from Tomas Gayoso (tgayoso@gmail.com) ---
System config for the record as in the mesa bug: 

root@tufboxen:~# date 
Mon Jun  7 16:40:27 -03 2021
root@tufboxen:~# inxi -GSC -xx
System:    Host: tufboxen.lan Kernel: 5.10.42-TUF x86_64 bits: 64 compiler: gcc
v: 2.36.1-slack15 Desktop: i3 4.18.3 dm: XDM 
           Distro: Slackware 14.2 
CPU:       Info: 8-Core model: AMD Ryzen 7 4800H with Radeon Graphics bits: 64
type: MT MCP arch: Zen 2 rev: 1 cache: 
           L1: 512 KiB L2: 4 MiB L3: 8 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3
svm bogomips: 92624 
           Speed: 1370 MHz min/max: 1400/2900 MHz boost: enabled Core speeds
(MHz): 1: 1370 2: 1290 3: 1402 4: 1497 5: 1388 
           6: 1327 7: 1390 8: 1391 9: 1566 10: 1370 11: 1301 12: 1396 13: 1394
14: 1411 15: 1397 16: 1517 
Graphics:  Device-1: NVIDIA TU116M [GeForce GTX 1660 Ti Mobile] vendor: ASUSTeK
driver: nvidia v: 465.31 bus-ID: 01:00.0 
           chip-ID: 10de:2191 
           Device-2: Advanced Micro Devices [AMD/ATI] Renoir vendor: ASUSTeK
driver: amdgpu v: kernel bus-ID: 05:00.0 
           chip-ID: 1002:1636 
           Device-3: IMC Networks USB2.0 HD UVC WebCam type: USB driver:
uvcvideo bus-ID: 3-4:4 chip-ID: 13d3:56a2 
           Display: server: X.Org 1.20.11 driver: loaded: amdgpu,ati,nvidia
unloaded: modesetting,nouveau,nv,vesa 
           alternate: fbdev resolution: 1: 1920x1080~144Hz 2: 2560x1440 s-dpi:
96 
           OpenGL: renderer: AMD RENOIR (DRM 3.40.0 5.10.42-TUF LLVM 12.0.0) v:
4.6 Mesa 21.1.2 direct render: Yes 
root@tufboxen:~#

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2021-06-07 19:41 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-19 14:46 [Bug 213145] New: AMDGPU resets, timesout and crashes after "*ERROR* Waiting for fences timed out!" bugzilla-daemon
2021-05-19 14:47 ` [Bug 213145] " bugzilla-daemon
2021-05-19 14:47 ` bugzilla-daemon
2021-05-27 13:43 ` bugzilla-daemon
2021-06-04 21:37 ` bugzilla-daemon
2021-06-04 21:38 ` bugzilla-daemon
2021-06-05  0:38 ` bugzilla-daemon
2021-06-07 19:37 ` bugzilla-daemon
2021-06-07 19:41 ` bugzilla-daemon [this message]
2021-06-08 16:38 ` bugzilla-daemon
2021-06-08 17:17 ` bugzilla-daemon
2021-06-08 17:25 ` bugzilla-daemon
2021-06-08 17:30 ` bugzilla-daemon
2022-05-25  2:21 ` bugzilla-daemon
2022-05-25  2:30 ` bugzilla-daemon
2022-05-25  4:03 ` bugzilla-daemon
2022-05-25  4:07 ` bugzilla-daemon
2022-05-25 20:18 ` bugzilla-daemon
2022-05-29  7:40 ` bugzilla-daemon
2022-05-31 19:59 ` bugzilla-daemon
2022-06-13  6:58 ` bugzilla-daemon
2022-07-26 20:42 ` bugzilla-daemon
2022-09-12 17:07 ` bugzilla-daemon
2022-09-30 15:00 ` bugzilla-daemon
2022-10-09 20:11 ` bugzilla-daemon
2022-10-10 18:24 ` bugzilla-daemon
2022-10-12 10:51 ` bugzilla-daemon
2022-10-12 12:01 ` bugzilla-daemon
2022-10-30 16:57 ` bugzilla-daemon
2022-11-12 16:24 ` bugzilla-daemon
2022-11-20 21:57 ` bugzilla-daemon
2022-11-26 20:19 ` bugzilla-daemon
2023-07-01  5:25 ` bugzilla-daemon
2023-07-01  5:27 ` bugzilla-daemon
2024-01-04 11:33 ` bugzilla-daemon
2024-02-04  0:04 ` bugzilla-daemon
2025-02-10 10:57 ` bugzilla-daemon
2025-02-10 12:37 ` 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-213145-2300-sigzrhOzWN@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;
as well as URLs for NNTP newsgroup(s).