[Bug 213145] New: AMDGPU resets, timesout and crashes after "*ERROR* Waiting for fences timed out!" - dri-devel - freedesktop.org experimental mailing list

List overview All Threads
Download

newer

[Bug 213145] New: AMDGPU resets, timesout and crashes after "ERROR Waiting for fences timed out!"

older

[PATCH 0/1] For stable: "drm/ast:...

[PATCH v3 1/2] dt-bindings:...

bugzilla-daemon＠bugzilla.kernel.org

19 May 2021 19 May '21

2:46 p.m.

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

Bug ID: 213145 Summary: AMDGPU resets, timesout and crashes after "*ERROR* Waiting for fences timed out!" Product: Drivers Version: 2.5 Kernel Version: 5.10.37 and 5.10.38 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: tgayoso@gmail.com Regression: No

Created attachment 296867 --> https://bugzilla.kernel.org/attachment.cgi?id=296867&action=edit lspci output

AMDGPU driver crashes randomly corrupting screen and freezing X with:

[ 60.449781] [drm:0xffffffffc25a7a57] *ERROR* Waiting for fences timed out! [ 60.971941] [drm:0xffffffffc25281ae] *ERROR* ring gfx timeout, signaled seq=3658, emitted seq=3660 [ 60.971946] [drm:0xffffffffc25281cb] *ERROR* Process information: process Xorg pid 1192 thread Xorg:cs0 pid 1193 [ 60.971952] amdgpu 0000:05:00.0: amdgpu: GPU reset begin!

... (some output suppressed for clarity, look at attached dmesg, please).

[ 61.800343] amdgpu 0000:05:00.0: amdgpu: recover vram bo from shadow start [ 61.800346] amdgpu 0000:05:00.0: amdgpu: recover vram bo from shadow done [ 61.800348] [drm] Skip scheduling IBs! [ 61.800350] [drm] Skip scheduling IBs! [ 61.800382] [drm] Skip scheduling IBs! [ 61.800398] amdgpu 0000:05:00.0: amdgpu: GPU reset(2) succeeded! [ 61.800566] [drm] Skip scheduling IBs! [ 61.800580] [drm] Skip scheduling IBs! [ 61.800627] [drm] Skip scheduling IBs! [ 61.801012] [drm] Skip scheduling IBs! [ 61.801024] [drm] Skip scheduling IBs! [ 61.801052] [drm] Skip scheduling IBs! [ 61.801062] [drm] Skip scheduling IBs! [ 61.801096] [drm] Skip scheduling IBs! [ 61.801105] [drm] Skip scheduling IBs! [ 61.801137] [drm] Skip scheduling IBs! [ 61.801806] [drm:0xffffffffc24219b8] *ERROR* Failed to initialize parser -125! [ 61.808746] [drm:0xffffffffc24219b8] *ERROR* Failed to initialize parser -125! [ 61.809392] [drm:0xffffffffc24219b8] *ERROR* Failed to initialize parser -125! [ 61.809764] [drm:0xffffffffc24219b8] *ERROR* Failed to initialize parser -125! [ 61.810389] [drm:0xffffffffc24219b8] *ERROR* Failed to initialize parser -125! [ 61.810866] [drm:0xffffffffc24219b8] *ERROR* Failed to initialize parser -125! [ 61.812529] [drm:0xffffffffc24219b8] *ERROR* Failed to initialize parser -125! [ 61.813359] [drm:0xffffffffc24219b8] *ERROR* Failed to initialize parser -125! [ 61.814770] [drm:0xffffffffc24219b8] *ERROR* Failed to initialize parser -125! [ 61.816488] [drm:0xffffffffc24219b8] *ERROR* Failed to initialize parser -125! [ 62.541982] ucsi_acpi USBC000:00: PPM init failed (-110) [ 67.004898] amdgpu_cs_ioctl: 1467 callbacks suppressed

Hardware: ASUS TUF506IU laptop (dual GPU Renoir and Nvidia GeForce GTX 1660 Ti Mobile)

Detailed hardware in lspci.txt. Detailed modules in lsmod.txt. Kernle config attached in Kernel_config.

-- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.

Show replies by date

bugzilla-daemon＠bugzilla.kernel.org

19 May 19 May

2:47 p.m.

New subject: [Bug 213145] AMDGPU resets, timesout and crashes after "*ERROR* Waiting for fences timed out!"

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

--- Comment #1 from Tomas Gayoso (tgayoso@gmail.com) --- Created attachment 296869 --> https://bugzilla.kernel.org/attachment.cgi?id=296869&action=edit lsmod output

-- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.

bugzilla-daemon＠bugzilla.kernel.org

2:47 p.m.

New subject: [Bug 213145] AMDGPU resets, timesout and crashes after "*ERROR* Waiting for fences timed out!"

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

--- Comment #2 from Tomas Gayoso (tgayoso@gmail.com) --- Created attachment 296871 --> https://bugzilla.kernel.org/attachment.cgi?id=296871&action=edit kernel configuration

-- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.

bugzilla-daemon＠bugzilla.kernel.org

27 May 27 May

1:43 p.m.

New subject: [Bug 213145] AMDGPU resets, timesout and crashes after "*ERROR* Waiting for fences timed out!"

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

meep@binary-kitchen.de changed:

What |Removed |Added ---------------------------------------------------------------------------- CC| |meep@binary-kitchen.de

--- Comment #3 from meep@binary-kitchen.de --- We have some crashes probably related to this at https://gitlab.freedesktop.org/drm/amd/-/issues/1591

I have the exact the same kernel log, however missing the very first line.

I can trigger this bug reproducibly by just opening a lot of xterm windows if truetype fonts enabled.

My Machine is brand new. So I dont have any last-working-setup/date. Thinkpad T14s. AMD U4750 (no dedicated GFX). Archlinux updated from 19.5.2021 till 27.5.2021 for sure has this bug in it.

Tried various kernel down/grades from 5.10.1 to 5.12.6, all crashed. Tried a lot of different linux-firmwares too.

Complete Archlinux Rollback to 1/March/2021 stopped crashing. I chose this date randomly so some days later everything might be fine too.

Not experienced in that whole Graphics-System and how packages/components interconnect.

Willing to help pinpointing the problem, testing fixes/solutions.

-- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.

bugzilla-daemon＠bugzilla.kernel.org

4 Jun 4 Jun

9:37 p.m.

New subject: [Bug 213145] AMDGPU resets, timesout and crashes after "*ERROR* Waiting for fences timed out!"

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

--- Comment #4 from Tomas Gayoso (tgayoso@gmail.com) --- Created attachment 297161 --> https://bugzilla.kernel.org/attachment.cgi?id=297161&action=edit 5.10.42 dmesg output with crash aftrer reset

Bug is still present on 5.10.42. Locking and crashing X after driver fails to reset. Attaching dmesg output.

-- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.

bugzilla-daemon＠bugzilla.kernel.org

9:38 p.m.

New subject: [Bug 213145] AMDGPU resets, timesout and crashes after "*ERROR* Waiting for fences timed out!"

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

Tomas Gayoso (tgayoso@gmail.com) changed:

What |Removed |Added ---------------------------------------------------------------------------- Kernel Version|5.10.37 and 5.10.38 |5.10.37 until 5.10.42

-- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.

bugzilla-daemon＠bugzilla.kernel.org

5 Jun 5 Jun

12:38 a.m.

New subject: [Bug 213145] AMDGPU resets, timesout and crashes after "*ERROR* Waiting for fences timed out!"

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

--- Comment #5 from meep@binary-kitchen.de --- https://gitlab.freedesktop.org/mesa/mesa/-/issues/4866

seems exactly same Problem, same config as another guy. seems to be introduced with removing some check from mesa to test size of drawbuffer against zero. not yet decided if its a bug to remove this, or if radeonsi or amdgpu firmware should handle this case.

there are some solutions and quickfixes posted, you could try them and report back then.

-- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.

bugzilla-daemon＠bugzilla.kernel.org

7 Jun 7 Jun

7:37 p.m.

New subject: [Bug 213145] AMDGPU resets, timesout and crashes after "*ERROR* Waiting for fences timed out!"

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

--- Comment #6 from Tomas Gayoso (tgayoso@gmail.com) --- I upgraded my setep to mesa-21.1.2, but I can still trigger the bug at will on fresh boot by opening a single xterm on i3wm and resizing it while running any fast scrolling character binary, like cli-visualizer ( https://github.com/dpayne/cli-visualizer ).

The other suggestions on the thread for the amdgpu module setting do nothing for me.

Willing to patch my kernel and test, I can compile my own.

-- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.

bugzilla-daemon＠bugzilla.kernel.org

7:41 p.m.

New subject: [Bug 213145] AMDGPU resets, timesout and crashes after "*ERROR* Waiting for fences timed out!"

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.

bugzilla-daemon＠bugzilla.kernel.org

8 Jun 8 Jun

4:38 p.m.

New subject: [Bug 213145] AMDGPU resets, timesout and crashes after "*ERROR* Waiting for fences timed out!"

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

--- Comment #8 from meep@binary-kitchen.de --- how about reading any comments ?

-- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.

bugzilla-daemon＠bugzilla.kernel.org

5:17 p.m.

New subject: [Bug 213145] AMDGPU resets, timesout and crashes after "*ERROR* Waiting for fences timed out!"

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

--- Comment #9 from Tomas Gayoso (tgayoso@gmail.com) --- Created attachment 297243 --> https://bugzilla.kernel.org/attachment.cgi?id=297243&action=edit patch for mesa 21.1.2

Thanks for the irony.

Recompiling Mesa 21.1.2 with the attached patch fixes the issue for me in kernels 5.10.42 and 5.12.9.

I followed this suggestion from the mesa bug report:

can you try 21.1.2 and change this line: file: src/mesa/main/draw.c function: validate_draw_arrays

change: if (count < 0 || numInstances < 0) into: if (count <= 0 || numInstances <= 0)

Cheers,

-- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.

bugzilla-daemon＠bugzilla.kernel.org

5:25 p.m.

New subject: [Bug 213145] AMDGPU resets, timesout and crashes after "*ERROR* Waiting for fences timed out!"

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

--- Comment #10 from meep@binary-kitchen.de --- ok nice :)

please report back to https://gitlab.freedesktop.org/mesa/mesa/-/issues/4866 with your config and that this fix resolved random crashes

thanks :)

(its not a kernel issue)

-- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.

bugzilla-daemon＠bugzilla.kernel.org

5:30 p.m.

New subject: [Bug 213145] AMDGPU resets, timesout and crashes after "*ERROR* Waiting for fences timed out!"

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

--- Comment #11 from meep@binary-kitchen.de --- if you have an easy and reproducible way to trigger this bug please tell them

-- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.

bugzilla-daemon＠kernel.org

25 May 25 May

2:21 a.m.

New subject: [Bug 213145] AMDGPU resets, timesout and crashes after "*ERROR* Waiting for fences timed out!"

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

Eric Wheeler (bugzilla-kernel@z.ewheeler.org) changed:

--- Comment #12 from Eric Wheeler (bugzilla-kernel@z.ewheeler.org) --- Considering this is a kernel crash, why wouldn't we still consider this a kernel bug?

Just because it can be fixed in userspace doesn't mean we shouldn't address the kernel crash because userspace should not be able to crash the kernel!

For servers it is considered a security problem when non-root users can crash the machine.

-- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.

bugzilla-daemon＠kernel.org

2:30 a.m.

New subject: [Bug 213145] AMDGPU resets, timesout and crashes after "*ERROR* Waiting for fences timed out!"

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

Alex Deucher (alexdeucher@gmail.com) changed:

What |Removed |Added ---------------------------------------------------------------------------- CC| |alexdeucher@gmail.com

--- Comment #13 from Alex Deucher (alexdeucher@gmail.com) --- (In reply to Eric Wheeler from comment #12)

...

Considering this is a kernel crash, why wouldn't we still consider this a kernel bug?

Just because it can be fixed in userspace doesn't mean we shouldn't address the kernel crash because userspace should not be able to crash the kernel!

For servers it is considered a security problem when non-root users can crash the machine.

There is no reasonable way for the kernel to handle it. We would need to parse every texture, vertex buffer, command buffer, and shader that the application submits to the GPU to try and verify if that combination of data, shader code and pipeline state would possibly cause a hang. A more robust solution would for session managers to monitor the GPU for resets and then restart the user's session so they don't lose their desktop. This is how it works on other OSes.

-- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.

bugzilla-daemon＠kernel.org

4:03 a.m.

New subject: [Bug 213145] AMDGPU resets, timesout and crashes after "*ERROR* Waiting for fences timed out!"

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

--- Comment #14 from Eric Wheeler (bugzilla-kernel@z.ewheeler.org) --- Interesting, that makes sense. Does the kernel have a framework for notifying window managers that the graphics driver reset? If not then that seems like that would be the next logical step.

-- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.

bugzilla-daemon＠kernel.org

4:07 a.m.

New subject: [Bug 213145] AMDGPU resets, timesout and crashes after "*ERROR* Waiting for fences timed out!"

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

--- Comment #15 from Eric Wheeler (bugzilla-kernel@z.ewheeler.org) --- I found this bug because our card was hanging the entire system, it didn't even ping and we had to get dmesg output from netconsole. While it would be (more) acceptable for the gpu driver to hang and X to need a restart, it would be nice if the OS remained up.

I'm trying the brand-new 5.18 to see if that helps.

(We were on a vendor-supplied 5.4.x Oracle UEK kernel on OL8 and the 5.13 amdgpu driver from amd's site built by DKMS so maybe something newer will help.)

-- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.

bugzilla-daemon＠kernel.org

8:18 p.m.

New subject: [Bug 213145] AMDGPU resets, timesout and crashes after "*ERROR* Waiting for fences timed out!"

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

--- Comment #16 from Eric Wheeler (bugzilla-kernel@z.ewheeler.org) --- FYI: 5.18 seems to be working! I guess the 5.13 driver from AMD needs to be fixed, but thats on them...

-- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.

bugzilla-daemon＠kernel.org

29 May 29 May

7:40 a.m.

New subject: [Bug 213145] AMDGPU resets, timesout and crashes after "*ERROR* Waiting for fences timed out!"

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

Nix\ (nix.sasl@gmail.com) changed:

What |Removed |Added ---------------------------------------------------------------------------- CC| |nix.sasl@gmail.com

--- Comment #17 from Nix\ (nix.sasl@gmail.com) --- I have the exact bug, Lenovo LENOVO 81LW AMD Ryzen 3 3200U with Radeon Vega Mobile Gfx When run the OpenCL geekbench test or OpenCL in libreoffice. With Vulkan works fine.

[11824.771725] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out! [11829.688441] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=1319920, emitted seq=1319922 [11829.688735] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 1908 thread Xorg:cs0 pid 2276 [11829.689018] amdgpu 0000:03:00.0: amdgpu: GPU reset begin! [11829.787762] [drm] free PSP TMR buffer [11829.823613] CPU: 0 PID: 40202 Comm: kworker/u32:0 Tainted: G W OE 5.18.0-2-MANJARO #1 e81df7241f6a360dc27e43ab195df7d97a8118f5 [11829.823619] Hardware name: LENOVO 81LW/LNVNB161216, BIOS ARCN37WW 05/14/2021 [11829.823621] Workqueue: amdgpu-reset-dev drm_sched_job_timedout [gpu_sched] [11829.823630] Call Trace: [11829.823633] <TASK> [11829.823634] dump_stack_lvl+0x48/0x5d [11829.823640] amdgpu_do_asic_reset+0x2a/0x470 [amdgpu 3e08061ca61bf3b1e24b4c9d96c6f8977494b21f] [11829.823954] amdgpu_device_gpu_recover_imp.cold+0x535/0x8ca [amdgpu 3e08061ca61bf3b1e24b4c9d96c6f8977494b21f] [11829.824258] amdgpu_job_timedout+0x18c/0x1c0 [amdgpu 3e08061ca61bf3b1e24b4c9d96c6f8977494b21f] [11829.824541] drm_sched_job_timedout+0x73/0x100 [gpu_sched ac691790925fcace6384349a4c749a4fc130c519] [11829.824548] process_one_work+0x1c4/0x380 [11829.824552] worker_thread+0x51/0x380 [11829.824554] ? rescuer_thread+0x3a0/0x3a0 [11829.824557] kthread+0xdb/0x110 [11829.824560] ? kthread_complete_and_exit+0x20/0x20 [11829.824563] ret_from_fork+0x1f/0x30 [11829.824568] </TASK> [11829.824571] amdgpu 0000:03:00.0: amdgpu: MODE2 reset [11829.824616] amdgpu 0000:03:00.0: amdgpu: GPU reset succeeded, trying to resume [11829.825038] [drm] PCIE GART of 1024M enabled. [11829.825039] [drm] PTB located at 0x000000F400900000 [11829.825055] [drm] PSP is resuming... [11829.845091] [drm] reserve 0x400000 from 0xf47fc00000 for PSP TMR [11829.919126] amdgpu 0000:03:00.0: amdgpu: RAS: optional ras ta ucode is not available [11829.925670] amdgpu 0000:03:00.0: amdgpu: RAP: optional rap ta ucode is not available [11830.673326] [drm] kiq ring mec 2 pipe 1 q 0 [11830.684064] [drm] VCN decode and encode initialized successfully(under SPG Mode). [11830.684072] amdgpu 0000:03:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0 [11830.684076] amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0 [11830.684078] amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0 [11830.684079] amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0 [11830.684082] amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0 [11830.684083] amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0 [11830.684085] amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0 [11830.684087] amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0 [11830.684089] amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0 [11830.684091] amdgpu 0000:03:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0 [11830.684093] amdgpu 0000:03:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 1 [11830.684094] amdgpu 0000:03:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on hub 1 [11830.684096] amdgpu 0000:03:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 on hub 1 [11830.684098] amdgpu 0000:03:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 on hub 1 [11830.684100] amdgpu 0000:03:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 1 [11830.688342] [drm:amdgpu_dm_set_vline0_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vline0_irq_state: crtc is NULL at id :3 [11830.688698] [drm:amdgpu_dm_set_vline0_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vline0_irq_state: crtc is NULL at id :3 [11830.689009] [drm:amdgpu_dm_set_vline0_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vline0_irq_state: crtc is NULL at id :3 [11830.689319] [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3 [11830.689628] [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3 [11830.689933] [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3 [11830.690243] [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 [11830.690551] [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 [11830.690860] [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 [11830.691169] [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 [11830.691478] [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3 [11830.691807] [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3 [11830.692112] [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3 [11830.696428] amdgpu 0000:03:00.0: amdgpu: recover vram bo from shadow start [11830.696430] amdgpu 0000:03:00.0: amdgpu: recover vram bo from shadow done [11830.696432] [drm] Skip scheduling IBs! [11830.696434] [drm] Skip scheduling IBs! [11830.696498] amdgpu 0000:03:00.0: amdgpu: GPU reset(2) succeeded! [11830.696501] [drm] Skip scheduling IBs! [11830.696511] [drm] Skip scheduling IBs! [11830.696518] [drm] Skip scheduling IBs! [11830.696523] [drm] Skip scheduling IBs! [11830.696529] [drm] Skip scheduling IBs! [11830.696535] [drm] Skip scheduling IBs! [11830.696541] [drm] Skip scheduling IBs! [11830.696547] [drm] Skip scheduling IBs! [11830.696554] [drm] Skip scheduling IBs! [11830.696631] [drm] Skip scheduling IBs! [11830.696729] [drm] Skip scheduling IBs! [11830.696748] [drm] Skip scheduling IBs! [11830.696822] [drm] Skip scheduling IBs! [11830.696832] [drm] Skip scheduling IBs! [11830.696850] [drm] Skip scheduling IBs! [11830.696857] [drm] Skip scheduling IBs! [11830.696864] [drm] Skip scheduling IBs! [11830.696870] [drm] Skip scheduling IBs! [11830.696876] [drm] Skip scheduling IBs! [11830.696883] [drm] Skip scheduling IBs! [11830.696898] [drm] Skip scheduling IBs! [11830.696905] [drm] Skip scheduling IBs! [11830.696913] [drm] Skip scheduling IBs! [11830.696930] [drm] Skip scheduling IBs! [11830.697050] [drm] Skip scheduling IBs! [11830.697059] [drm] Skip scheduling IBs! [11830.697098] [drm] Skip scheduling IBs! [11830.697107] [drm] Skip scheduling IBs! [11830.697116] [drm] Skip scheduling IBs! [11830.697125] [drm] Skip scheduling IBs! [11830.697142] [drm] Skip scheduling IBs! [11830.699931] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [11830.708071] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [11830.708980] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [11830.710191] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [11830.711089] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [11830.711615] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [11830.712737] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [11830.713297] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [11830.713959] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [11830.714583] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!

-- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.

bugzilla-daemon＠kernel.org

31 May 31 May

7:59 p.m.

New subject: [Bug 213145] AMDGPU resets, timesout and crashes after "*ERROR* Waiting for fences timed out!"

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

--- Comment #18 from Eric Wheeler (bugzilla-kernel@z.ewheeler.org) --- Nix, did you try Linux 5.18? It worked for me...

-- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.

bugzilla-daemon＠kernel.org

13 Jun 13 Jun

6:58 a.m.

New subject: [Bug 213145] AMDGPU resets, timesout and crashes after "*ERROR* Waiting for fences timed out!"

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

emlodnaor@gmail.com changed:

What |Removed |Added ---------------------------------------------------------------------------- CC| |emlodnaor@gmail.com

--- Comment #19 from emlodnaor@gmail.com --- It seemed to work for me at first, but just crashed again... However, for me it happens more randomly, and I haven't found a way to reproduce it...

I've also once had a similar crash in windows, so have been suspecting faulty hardware?

-- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.

1042

Age (days ago)

1432

Last active (days ago)

dri-devel@lists.freedesktop.org

20 comments

2 participants

tags (0)

participants (2)

bugzilla-daemon＠bugzilla.kernel.org
bugzilla-daemon＠kernel.org