All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 201957] New: amdgpu: ring gfx timeout
Date: Tue, 11 Dec 2018 04:52:52 +0000	[thread overview]
Message-ID: <bug-201957-2300@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 201957
           Summary: amdgpu: ring gfx timeout
           Product: Drivers
           Version: 2.5
    Kernel Version: 4.19.8, 4.20-rc5
          Hardware: Intel
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: blocking
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: felix.adrianto@gmail.com
        Regression: No

Error message: 
[Dec 5 22:08] amdgpu 0000:23:00.0: GPU fault detected: 146 0x0000480c for
process yuzu pid 2920 thread yuzu:cs0 pid 2935
[  +0.000005] amdgpu 0000:23:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
0x00000000
[  +0.000002] amdgpu 0000:23:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x0604800C
[  +0.000003] amdgpu 0000:23:00.0: VM fault (0x0c, vmid 3, pasid 32770) at page
0, read from 'TC4' (0x54433400) (72)
[ +10.053011] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout,
signaled seq=37241, emitted seq=37244
[  +0.000007] [drm] GPU recovery disabled.


How to reproduce the issue:
1. Playing with yuzu-emulator 
2. Load Super Mario Odyssey
3. Start new game
4. When Mario is about to jump for the first time after being woken up by
Cappy, this bug must occur. 

During the issue, the following occured:
1. Graphic locked up. 
2. System can be access through SSH.

System specification:
Debian Sid
Radeon RX 580

I have tried the following combination:
1. Kernel 4.17, 4.18, 4.19, 4.20, drm-next-4.21.wip
2. Mesa 18.2, 18.3, 19.0-development branch

But none of the above combination fixes the issue. Let me know if you need more
information and more testing from me.

-- 
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

             reply	other threads:[~2018-12-11  4:52 UTC|newest]

Thread overview: 100+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-11  4:52 bugzilla-daemon [this message]
2018-12-11 14:57 ` [Bug 201957] amdgpu: ring gfx timeout bugzilla-daemon
2018-12-11 18:18 ` bugzilla-daemon
2019-03-07  5:20 ` bugzilla-daemon
2019-03-07  5:24 ` bugzilla-daemon
2019-03-12 13:15 ` bugzilla-daemon
2019-04-01 18:20 ` bugzilla-daemon
2019-04-01 18:44 ` bugzilla-daemon
2019-08-20 15:06 ` bugzilla-daemon
2019-09-11  8:36 ` bugzilla-daemon
2019-09-20 11:37 ` bugzilla-daemon
2019-10-02 10:39 ` bugzilla-daemon
2019-10-11 22:00 ` bugzilla-daemon
2019-10-14 17:18 ` bugzilla-daemon
2019-10-24 16:39 ` bugzilla-daemon
2019-10-24 16:40 ` bugzilla-daemon
2019-10-27 18:44 ` bugzilla-daemon
2019-11-10  7:11 ` bugzilla-daemon
2019-11-25  9:43 ` bugzilla-daemon
2019-12-03 15:53 ` bugzilla-daemon
2019-12-03 16:07 ` bugzilla-daemon
2019-12-03 21:34 ` bugzilla-daemon
2019-12-04  9:54 ` bugzilla-daemon
2019-12-08 17:32 ` bugzilla-daemon
2020-01-02  8:30 ` bugzilla-daemon
2020-01-02  9:11 ` bugzilla-daemon
2020-01-19 17:03 ` bugzilla-daemon
2020-01-19 17:04 ` bugzilla-daemon
2020-01-19 17:04 ` bugzilla-daemon
2020-01-19 17:13 ` bugzilla-daemon
2020-04-04 21:54 ` bugzilla-daemon
2020-05-01  9:03 ` bugzilla-daemon
2020-05-01 19:52 ` bugzilla-daemon
2020-05-25 12:21 ` bugzilla-daemon
2020-06-19 19:11 ` bugzilla-daemon
2020-08-10 23:49 ` bugzilla-daemon
2020-09-01 14:00 ` bugzilla-daemon
2020-09-13 11:14 ` bugzilla-daemon
2020-11-23 16:27 ` bugzilla-daemon
2021-01-24 19:37 ` bugzilla-daemon
2021-01-24 22:26 ` bugzilla-daemon
2021-01-24 22:51 ` bugzilla-daemon
2021-01-24 22:56 ` bugzilla-daemon
2021-01-25 22:24 ` bugzilla-daemon
2021-01-26  3:22 ` bugzilla-daemon
2021-02-14 19:48 ` bugzilla-daemon
2021-02-28 12:35 ` bugzilla-daemon
2021-03-28 13:19 ` bugzilla-daemon
2021-08-22 20:01 ` bugzilla-daemon
2021-11-17  7:14 ` bugzilla-daemon
2021-11-26  2:09 ` bugzilla-daemon
2021-12-12 21:59 ` bugzilla-daemon
2021-12-22 20:33 ` bugzilla-daemon
2022-01-01  4:29 ` bugzilla-daemon
2022-01-09 18:06 ` bugzilla-daemon
2022-01-22 23:54 ` bugzilla-daemon
2022-01-22 23:56 ` bugzilla-daemon
2022-01-24 23:17 ` bugzilla-daemon
2022-01-25  8:56 ` bugzilla-daemon
2022-01-25 18:19 ` bugzilla-daemon
2022-01-25 18:49 ` bugzilla-daemon
2022-02-02 11:39 ` bugzilla-daemon
2022-02-03  1:37 ` bugzilla-daemon
2022-02-03  1:39 ` bugzilla-daemon
2022-02-03  3:42 ` bugzilla-daemon
2022-02-11 12:23 ` bugzilla-daemon
2022-02-24 23:40 ` bugzilla-daemon
2022-02-25 14:20 ` bugzilla-daemon
2022-05-05 15:19 ` bugzilla-daemon
2022-05-05 19:14 ` bugzilla-daemon
2022-06-11 22:06 ` bugzilla-daemon
2022-06-13  1:20 ` bugzilla-daemon
2022-06-20 12:03 ` bugzilla-daemon
2022-06-20 12:06 ` bugzilla-daemon
2022-06-22 12:56 ` bugzilla-daemon
2022-06-23 10:04 ` bugzilla-daemon
2022-06-23 10:26 ` bugzilla-daemon
2022-06-23 11:05 ` bugzilla-daemon
2022-06-23 11:44 ` bugzilla-daemon
2022-06-23 22:12 ` bugzilla-daemon
2022-06-29  2:58 ` bugzilla-daemon
2022-07-14 10:17 ` bugzilla-daemon
2022-07-17 10:28 ` bugzilla-daemon
2022-07-17 20:08 ` bugzilla-daemon
2022-08-11  2:59 ` bugzilla-daemon
2023-01-11  1:13 ` bugzilla-daemon
2023-05-23 10:27 ` bugzilla-daemon
2023-05-24  8:55 ` bugzilla-daemon
2023-08-15 12:33 ` bugzilla-daemon
2023-08-24 15:52 ` bugzilla-daemon
2023-09-21 22:38 ` bugzilla-daemon
2023-09-23  1:52 ` bugzilla-daemon
2023-09-30 10:25 ` bugzilla-daemon
2023-09-30 18:57 ` bugzilla-daemon
2023-09-30 19:08 ` bugzilla-daemon
2023-09-30 19:35 ` bugzilla-daemon
2023-09-30 19:47 ` bugzilla-daemon
2023-10-21 14:29 ` bugzilla-daemon
2023-10-22 17:35 ` bugzilla-daemon
2023-10-23 17: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-201957-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 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.