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 201957] amdgpu: ring gfx timeout
Date: Sun, 28 Mar 2021 13:19:59 +0000	[thread overview]
Message-ID: <bug-201957-2300-v0oNN2Pc6u@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-201957-2300@https.bugzilla.kernel.org/>

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

Csaba Tímár (csaba.timar01@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |csaba.timar01@gmail.com

--- Comment #47 from Csaba Tímár (csaba.timar01@gmail.com) ---
I have something very similar with my Vega56. I can reproduce it with Win10
too. 
I think it's an AMD Hw issue. 

march 28 15:07:35 PC-home kernel: [drm:amdgpu_dm_atomic_commit_tail [amdgpu]]
*ERROR* Waiting for fences timed out!
march 28 15:07:35 PC-home kernel: qcm fence wait loop timeout expired
march 28 15:07:35 PC-home kernel: The cp might be in an unrecoverable state due
to an unsuccessful queues preemption
march 28 15:07:35 PC-home kernel: amdgpu: Failed to evict process queues
march 28 15:07:35 PC-home kernel: amdgpu 0000:0a:00.0: amdgpu: GPU reset begin!
march 28 15:07:35 PC-home kernel: amdgpu: Failed to quiesce KFD
march 28 15:07:35 PC-home kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR*
ring gfx timeout, signaled seq=567492, emitted seq=567494
march 28 15:07:35 PC-home kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR*
Process information: process vkcube pid 7677 thread vkcube pid 7677
march 28 15:07:35 PC-home kernel: amdgpu 0000:0a:00.0: amdgpu: GPU reset begin!
march 28 15:07:35 PC-home kernel: amdgpu 0000:0a:00.0: amdgpu: Bailing on TDR
for s_job:869c2, as another already in progress
march 28 15:07:36 PC-home kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR*
ring page1 timeout, signaled seq=20352, emitted seq=20353
march 28 15:07:36 PC-home kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR*
Process information: process  pid 0 thread  pid 0
march 28 15:07:36 PC-home kernel: amdgpu 0000:0a:00.0: amdgpu: GPU reset begin!
march 28 15:07:36 PC-home kernel: amdgpu 0000:0a:00.0: amdgpu: Bailing on TDR
for s_job:4f80, as another already in progress
march 28 15:07:39 PC-home kernel: amdgpu 0000:0a:00.0: amdgpu: failed to
suspend display audio
march 28 15:07:39 PC-home kernel: BUG: unable to handle page fault for address:
ffffa9c54bb4f910
march 28 15:07:39 PC-home kernel: #PF: supervisor write access in kernel mode
march 28 15:07:39 PC-home kernel: #PF: error_code(0x0002) - not-present page
march 28 15:07:39 PC-home kernel: PGD 100000067 P4D 100000067 PUD 1001b9067 PMD
1cdabb067 PTE 0
march 28 15:07:39 PC-home kernel: Oops: 0002 [#1] PREEMPT SMP NOPTI
march 28 15:07:39 PC-home kernel: CPU: 9 PID: 8586 Comm: kworker/9:0 Tainted: G
          OE     5.11.6-1-MANJARO #1


march 28 15:07:39 PC-home kernel: Hardware name: System manufacturer System
Product Name/PRIME A320M-K, BIOS 5603 10/14/2020
march 28 15:07:39 PC-home kernel: Workqueue: events kfd_process_hw_exception
[amdgpu]
march 28 15:07:39 PC-home kernel: RIP: 0010:amdgpu_device_lock_adev+0x2b/0x83
[amdgpu]
march 28 15:07:39 PC-home kernel: Code: 1f 44 00 00 31 c0 ba 01 00 00 00 f0 0f
b1 97 f4 77 01 00 45 31 c0 85 c0 75 64 53 48 89 fb 48 8d bf 00 78 01 00 e8 e7
16 27 c9 <f0> ff 83 40 >
march 28 15:07:39 PC-home kernel: RSP: 0018:ffffa9c54c73be00 EFLAGS: 00010246
march 28 15:07:39 PC-home kernel: RAX: ffff951f0c155dc0 RBX: ffffa9c54bb495d0
RCX: 0000000000000001
march 28 15:07:39 PC-home kernel: RDX: 0000000000000001 RSI: 0000000000000000
RDI: ffffa9c54bb60dd0
march 28 15:07:39 PC-home kernel: RBP: 0000000000000000 R08: 0000000000000000
R09: 0000000000000000
march 28 15:07:39 PC-home kernel: R10: 0000000000000003 R11: 0000000000000000
R12: ffffa9c54bb495d0
march 28 15:07:39 PC-home kernel: R13: ffff951e19160000 R14: ffff951e19170e30
R15: 00000000000000e0
march 28 15:07:39 PC-home kernel: FS:  0000000000000000(0000)
GS:ffff95210ea40000(0000) knlGS:0000000000000000
march 28 15:07:39 PC-home kernel: CS:  0010 DS: 0000 ES: 0000 CR0:
0000000080050033
march 28 15:07:39 PC-home kernel: CR2: ffffa9c54bb4f910 CR3: 0000000385410000
CR4: 00000000003506e0
march 28 15:07:39 PC-home kernel: Call Trace:
march 28 15:07:39 PC-home kernel:  amdgpu_device_gpu_recover.cold+0x180/0x95d
[amdgpu]
march 28 15:07:39 PC-home kernel:  ?
amdgpu_device_doorbell_init.part.0+0x71/0xc0 [amdgpu]
march 28 15:07:39 PC-home kernel:  process_one_work+0x214/0x3e0
march 28 15:07:39 PC-home kernel:  worker_thread+0x4d/0x3d0
march 28 15:07:39 PC-home kernel:  ? rescuer_thread+0x3c0/0x3c0
march 28 15:07:39 PC-home kernel:  kthread+0x142/0x160
march 28 15:07:39 PC-home kernel:  ? __kthread_bind_mask+0x60/0x60
march 28 15:07:39 PC-home kernel:  ret_from_fork+0x22/0x30
march 28 15:07:39 PC-home kernel: Modules linked in: rfcomm cmac algif_hash
algif_skcipher af_alg bnep btusb btrtl btbcm btintel bluetooth ecdh_generic ecc
uas usb_storage mousedev>
march 28 15:07:39 PC-home kernel:  gpio_amdpt acpi_cpufreq drm uinput sg fuse
crypto_user agpgart ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2
crc32c_intel xhci_pci
march 28 15:07:39 PC-home kernel: CR2: ffffa9c54bb4f910
march 28 15:07:39 PC-home kernel: ---[ end trace 2eaf88bedaabd891 ]---
march 28 15:07:39 PC-home kernel: RIP: 0010:amdgpu_device_lock_adev+0x2b/0x83
[amdgpu]
march 28 15:07:39 PC-home kernel: Code: 1f 44 00 00 31 c0 ba 01 00 00 00 f0 0f
b1 97 f4 77 01 00 45 31 c0 85 c0 75 64 53 48 89 fb 48 8d bf 00 78 01 00 e8 e7
16 27 c9 <f0> ff 83 40 >
march 28 15:07:39 PC-home kernel: RSP: 0018:ffffa9c54c73be00 EFLAGS: 00010246
march 28 15:07:39 PC-home kernel: RAX: ffff951f0c155dc0 RBX: ffffa9c54bb495d0
RCX: 0000000000000001
march 28 15:07:39 PC-home kernel: RDX: 0000000000000001 RSI: 0000000000000000
RDI: ffffa9c54bb60dd0
march 28 15:07:39 PC-home kernel: RBP: 0000000000000000 R08: 0000000000000000
R09: 0000000000000000
march 28 15:07:39 PC-home kernel: R10: 0000000000000003 R11: 0000000000000000
R12: ffffa9c54bb495d0
march 28 15:07:39 PC-home kernel: R13: ffff951e19160000 R14: ffff951e19170e30
R15: 00000000000000e0
march 28 15:07:39 PC-home kernel: FS:  0000000000000000(0000)
GS:ffff95210ea40000(0000) knlGS:0000000000000000
march 28 15:07:39 PC-home kernel: CS:  0010 DS: 0000 ES: 0000 CR0:
0000000080050033
march 28 15:07:39 PC-home kernel: CR2: ffffa9c54bb4f910 CR3: 00000002fa6de000
CR4: 00000000003506e0

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

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:[~2021-03-28 13:20 UTC|newest]

Thread overview: 100+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-11  4:52 [Bug 201957] New: amdgpu: ring gfx timeout bugzilla-daemon
2018-12-11 14:57 ` [Bug 201957] " 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 [this message]
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-v0oNN2Pc6u@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).