All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 205089] amdgpu : drm:amdgpu_cs_ioctl : Failed to initialize parser -125
Date: Fri, 05 Jan 2024 10:51:11 +0000	[thread overview]
Message-ID: <bug-205089-2300-T2vEovWl7b@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-205089-2300@https.bugzilla.kernel.org/>

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

Rik (riksoft@gmail.com) changed:

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

--- Comment #61 from Rik (riksoft@gmail.com) ---
Yesterday I've apt update Debian 12 and with the update I got 6.1.0.-16 -->
6.1.0.-17.
This morning while I was scrolling rapidly a long page of code inside Netbeans
20, I find myself at login.
I DOUBT IT'S MERE COINCIDENCE because I've been working ok for months with the
same exact hw/sw config

I can see the culprit in log:
Jan 05 09:50:44  kernel: amdgpu 0000:01:00.0: amdgpu: GPU fault detected: 147
0x00000802 for process Xorg pid 1130 thread Xorg:cs0 pid 1605
That triggered a cascade of problems this way

Jan 05 09:50:44  kernel: amdgpu 0000:01:00.0: amdgpu: GPU fault detected: 147
0x00000802 for process Xorg pid 1130 thread Xorg:cs0 pid 1605
Jan 05 09:50:44  kernel: amdgpu 0000:01:00.0: amdgpu:  
VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00000800
Jan 05 09:50:44  kernel: amdgpu 0000:01:00.0: amdgpu:  
VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0C008002
Jan 05 09:50:44  kernel: amdgpu 0000:01:00.0: amdgpu: VM fault (0x02, vmid 6,
pasid 32769) at page 2048, read from 'TC0' (0x54433000) (8)
Jan 05 09:50:54  kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx
timeout, signaled seq=158350, emitted seq=158352
Jan 05 09:50:54  kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process
information: process Xorg pid 1130 thread Xorg:cs0 pid 1605
Jan 05 09:50:54  kernel: amdgpu 0000:01:00.0: amdgpu: GPU reset begin!
Jan 05 09:50:54  kernel: amdgpu: cp is busy, skip halt cp
Jan 05 09:50:55  kernel: amdgpu: rlc is busy, skip halt rlc
Jan 05 09:50:55  kernel: amdgpu 0000:01:00.0: amdgpu: BACO reset
Jan 05 09:50:55  kernel: amdgpu 0000:01:00.0: amdgpu: GPU reset succeeded,
trying to resume
Jan 05 09:50:55  kernel: [drm] PCIE GART of 256M enabled (table at
0x000000F400900000).
Jan 05 09:50:55  kernel: [drm] VRAM is lost due to GPU reset!
Jan 05 09:50:55  kernel: [drm] UVD and UVD ENC initialized successfully.
Jan 05 09:50:55  kernel: [drm] VCE initialized successfully.
Jan 05 09:50:55  kernel: amdgpu 0000:01:00.0: amdgpu: recover vram bo from
shadow start
Jan 05 09:50:55  kernel: amdgpu 0000:01:00.0: amdgpu: recover vram bo from
shadow done
Jan 05 09:50:55  kernel: [drm] Skip scheduling IBs!
Jan 05 09:50:55  kernel: [drm] Skip scheduling IBs!
Jan 05 09:50:55  kernel: amdgpu 0000:01:00.0: amdgpu: GPU reset(2) succeeded!
Jan 05 09:50:55  kernel: [drm] Skip scheduling IBs!
Jan 05 09:50:55  kernel: [drm] Skip scheduling IBs!
Jan 05 09:50:55  kernel: [drm] Skip scheduling IBs!
Jan 05 09:50:55  kernel: [drm] Skip scheduling IBs!
Jan 05 09:50:55  kernel: [drm] Skip scheduling IBs!
Jan 05 09:50:55  kernel: [drm] Skip scheduling IBs!
Jan 05 09:50:55  kernel: [drm] Skip scheduling IBs!
Jan 05 09:50:55  kernel: [drm] Skip scheduling IBs!
Jan 05 09:50:55  kernel: [drm] Skip scheduling IBs!
Jan 05 09:50:55  kernel: [drm] Skip scheduling IBs!
Jan 05 09:50:55  kernel: [drm] Skip scheduling IBs!
Jan 05 09:50:55  kernel: [drm] Skip scheduling IBs!
Jan 05 09:50:55  kernel: [drm] Skip scheduling IBs!
Jan 05 09:50:55  kernel: [drm] Skip scheduling IBs!
Jan 05 09:50:55  kernel: [drm] Skip scheduling IBs!
Jan 05 09:50:55  kernel: [drm] Skip scheduling IBs!
Jan 05 09:50:55  kernel: [drm] Skip scheduling IBs!
Jan 05 09:50:55  kernel: [drm] Skip scheduling IBs!
Jan 05 09:50:55  kernel: [drm] Skip scheduling IBs!
Jan 05 09:50:55  kernel: [drm] Skip scheduling IBs!
Jan 05 09:50:55  kernel: [drm] Skip scheduling IBs!
Jan 05 09:50:55  kernel: [drm] Skip scheduling IBs!
Jan 05 09:50:55  kernel: [drm] Skip scheduling IBs!
Jan 05 09:50:55  kernel: [drm] Skip scheduling IBs!
Jan 05 09:50:55  kernel: [drm] Skip scheduling IBs!
Jan 05 09:50:55  kernel: [drm] Skip scheduling IBs!
Jan 05 09:50:55  kernel: [drm] Skip scheduling IBs!
Jan 05 09:50:55  kernel: [drm] Skip scheduling IBs!
Jan 05 09:50:55  kernel: [drm] Skip scheduling IBs!
Jan 05 09:50:55  kernel: [drm] Skip scheduling IBs!
Jan 05 09:50:55  kernel: [drm] Skip scheduling IBs!
Jan 05 09:50:55  kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to
initialize parser -125!
Jan 05 09:50:55  pulseaudio[3356]: X11 I/O error handler called
Jan 05 09:50:55  pulseaudio[3356]: X11 I/O error exit handler called, preparing
to tear down X11 modules
Jan 05 09:50:55  polkitd[1078]: Unregistered Authentication Agent for
unix-session:4 (system bus name :1.44, object path
/org/mate/PolicyKit1/AuthenticationAgent, locale en_GB.UTF-8) (disconnected
from bus)
Jan 05 09:50:55  at-spi-bus-launcher[3480]: X connection to :0 broken (explicit
kill or server shutdown).
Jan 05 09:50:55  lightdm[2844]: pam_unix(lightdm:session): session closed for
user rik
Jan 05 09:50:55  systemd-logind[920]: Session 4 logged out. Waiting for
processes to exit.
Jan 05 09:50:55  firefox[4100]: Exiting due to channel error.
Jan 05 09:50:55  firefox[17385]: Exiting due to channel error.
Jan 05 09:50:55  firefox[4070]: Exiting due to channel error.
Jan 05 09:50:55  firefox[4074]: Exiting due to channel error.
Jan 05 09:50:55  firefox[17422]: Exiting due to channel error.
Jan 05 09:50:55  firefox[17383]: Exiting due to channel error.
Jan 05 09:50:55  firefox[4020]: Exiting due to channel error.
Jan 05 09:50:55  firefox[3959]: Exiting due to channel error.
Jan 05 09:50:55  kernel: ------------[ cut here ]------------
Jan 05 09:50:55  kernel: WARNING: CPU: 4 PID: 13711 at
drivers/gpu/drm/amd/amdgpu/amdgpu_irq.c:655 amdgpu_irq_put+0x45/0x70 [amdgpu]
Jan 05 09:50:55  kernel: Modules linked in: vboxnetadp(OE) vboxnetflt(OE)
vboxdrv(OE) rfkill ip6t_REJECT nf_reject_ipv6 xt_hl ip6_tables ip6t_rt
ipt_REJECT nf_reject_ipv4 xt_LOG nf_log_syslog xt_multiport nft_limit xt_limit
xt_addrtype xt_tcpudp sunrpc xt_conntrack nf_conn>
Jan 05 09:50:55  kernel:  loop fuse ip_tables x_tables autofs4 ext4 crc16
mbcache jbd2 btrfs blake2b_generic zstd_compress raid10 raid456
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq
libcrc32c crc32c_generic raid1 raid0 multipath linear md_mod hi>
Jan 05 09:50:55  kernel: CPU: 4 PID: 13711 Comm: kworker/4:0 Tainted: G        
  OE      6.1.0-17-amd64 #1  Debian 6.1.69-1
Jan 05 09:50:55  kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By
O.E.M./Z370 Extreme4, BIOS P1.80 03/20/2018
Jan 05 09:50:55  kernel: Workqueue: events drm_mode_rmfb_work_fn [drm]
Jan 05 09:50:55  kernel: RIP: 0010:amdgpu_irq_put+0x45/0x70 [amdgpu]
Jan 05 09:50:55  kernel: Code: 48 8b 4e 10 48 83 39 00 74 2c 89 d1 48 8d 04 88
8b 08 85 c9 74 14 f0 ff 08 b8 00 00 00 00 74 05 c3 cc cc cc cc e9 8b fd ff ff
<0f> 0b b8 ea ff ff ff c3 cc cc cc cc b8 ea ff ff ff c3 cc cc cc cc
Jan 05 09:50:55  kernel: RSP: 0018:ffff9c9603077900 EFLAGS: 00010046
Jan 05 09:50:55  kernel: RAX: ffff90d56350bca0 RBX: ffff90d540c63800 RCX:
0000000000000000
Jan 05 09:50:55  kernel: RDX: 0000000000000000 RSI: ffff90d54bf86578 RDI:
ffff90d54bf80000
Jan 05 09:50:55  kernel: RBP: 0000000000000000 R08: ffffffffc0e0691d R09:
0000000000000000
Jan 05 09:50:55  kernel: R10: ffff9c96030777f4 R11: 000000000000090d R12:
ffff90d54bf80010
Jan 05 09:50:55  kernel: R13: ffff90d54bf80000 R14: ffff90d62c5e4e00 R15:
ffff90d540c63800
Jan 05 09:50:55  kernel: FS:  0000000000000000(0000) GS:ffff90d89ed00000(0000)
knlGS:0000000000000000
Jan 05 09:50:55  kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jan 05 09:50:55  kernel: CR2: 00007f903f3433d8 CR3: 00000002e8a10006 CR4:
00000000003706e0
Jan 05 09:50:55  kernel: Call Trace:
Jan 05 09:50:55  kernel:  <TASK>
Jan 05 09:50:55  kernel:  ? __warn+0x7d/0xc0
Jan 05 09:50:55  kernel:  ? amdgpu_irq_put+0x45/0x70 [amdgpu]
Jan 05 09:50:55  kernel:  ? report_bug+0xe2/0x150
Jan 05 09:50:55  kernel:  ? handle_bug+0x41/0x70
Jan 05 09:50:55  kernel:  ? exc_invalid_op+0x13/0x60
Jan 05 09:50:55  kernel:  ? asm_exc_invalid_op+0x16/0x20
Jan 05 09:50:55  kernel:  ? amdgpu_irq_put+0x45/0x70 [amdgpu]
Jan 05 09:50:55  kernel:  dm_set_vblank+0x187/0x1b0 [amdgpu]
Jan 05 09:50:55  kernel:  drm_vblank_disable_and_save+0xb3/0xf0 [drm]
Jan 05 09:50:55  kernel:  drm_crtc_vblank_off+0xd1/0x2a0 [drm]
Jan 05 09:50:55  kernel:  amdgpu_dm_atomic_commit_tail+0x182/0x3790 [amdgpu]
Jan 05 09:50:55  kernel:  ? __alloc_pages+0x1dc/0x330
Jan 05 09:50:55  kernel:  ? free_unref_page_commit+0x7c/0x170
Jan 05 09:50:55  kernel:  ? free_unref_page+0x15f/0x1d0
Jan 05 09:50:55  kernel:  ? mod_lruvec_page_state.constprop.0+0x1c/0x30
Jan 05 09:50:55  kernel:  ? __kmalloc_large_node+0x9e/0xe0
Jan 05 09:50:55  kernel:  ? __kmalloc_node+0xbf/0x150
Jan 05 09:50:55  kernel:  ? dce112_validate_bandwidth+0x72/0x1c0 [amdgpu]
Jan 05 09:50:55  kernel:  ? dc_validate_global_state+0x309/0x3d0 [amdgpu]
Jan 05 09:50:55  kernel:  ? dma_resv_iter_first_unlocked+0x62/0x70
Jan 05 09:50:55  kernel:  ? dma_resv_get_fences+0x5d/0x220
Jan 05 09:50:55  kernel:  ? dma_resv_get_singleton+0x42/0x140
Jan 05 09:50:55  kernel:  ? wait_for_completion_timeout+0x13a/0x170
Jan 05 09:50:55  kernel:  ? wait_for_completion_interruptible+0x135/0x1e0
Jan 05 09:50:55  kernel:  commit_tail+0x91/0x130 [drm_kms_helper]
Jan 05 09:50:55  kernel:  drm_atomic_helper_commit+0x112/0x140 [drm_kms_helper]
Jan 05 09:50:55  kernel:  drm_atomic_commit+0x93/0xc0 [drm]
Jan 05 09:50:55  kernel:  ? drm_plane_get_damage_clips.cold+0x1c/0x1c [drm]
Jan 05 09:50:55  kernel:  drm_framebuffer_remove+0x479/0x510 [drm]
Jan 05 09:50:55  kernel:  drm_mode_rmfb_work_fn+0x76/0x90 [drm]
Jan 05 09:50:55  kernel:  process_one_work+0x1c4/0x380
Jan 05 09:50:55  kernel:  worker_thread+0x1ab/0x380
Jan 05 09:50:55  kernel:  ? rescuer_thread+0x3a0/0x3a0
Jan 05 09:50:55  kernel:  kthread+0xd7/0x100
Jan 05 09:50:55  kernel:  ? kthread_complete_and_exit+0x20/0x20
Jan 05 09:50:55  kernel:  ret_from_fork+0x1f/0x30
Jan 05 09:50:55  kernel:  </TASK>
Jan 05 09:50:55  kernel: ---[ end trace 0000000000000000 ]---
Jan 05 09:50:56  rtkit-daemon[2336]: Supervising 3 threads of 1 processes of 1
users.
Jan 05 09:50:56  rtkit-daemon[2336]: Successfully made thread 17615 of process
3356 owned by '1000' RT at priority 5.
Jan 05 09:50:56  rtkit-daemon[2336]: Supervising 4 threads of 1 processes of 1
users.
Jan 05 09:50:56  lightdm[17633]: pam_unix(lightdm-greeter:session): session
opened for user lightdm(uid=114) by (uid=0)
Jan 05 09:50:56  systemd[1]: Created slice user-114.slice - User Slice of UID
114.
Jan 05 09:50:56  systemd[1]: Starting user-runtime-dir@114.service - User
Runtime Directory /run/user/114...
Jan 05 09:50:56  systemd-logind[920]: New session c2 of user lightdm.



Graphics:
  Device-1: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X/590]
    driver: amdgpu v: kernel
  Display: x11 server: X.Org v: 1.21.1.7 driver: X: loaded: amdgpu
    unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu resolution:
    1: 1440x2560~60Hz 2: 1440x2560~60Hz
  API: OpenGL v: 4.6 Mesa 22.3.6 renderer: AMD Radeon RX 570 Series
    (polaris10 LLVM 15.0.6 DRM 3.49 6.1.0-17-amd64)

-- 
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:[~2024-01-05 10:51 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-05 11:48 [Bug 205089] New: amdgpu : drm:amdgpu_cs_ioctl : Failed to initialize parser -125 bugzilla-daemon
2019-10-07  3:16 ` [Bug 205089] " bugzilla-daemon
2019-10-08 17:50 ` bugzilla-daemon
2019-10-08 18:23 ` bugzilla-daemon
2019-10-08 20:15 ` bugzilla-daemon
2019-10-08 20:19 ` bugzilla-daemon
2019-10-12 19:05 ` bugzilla-daemon
2019-10-12 19:06 ` bugzilla-daemon
2019-10-14 17:20 ` bugzilla-daemon
2019-10-14 19:07 ` bugzilla-daemon
2020-04-27 16:58 ` bugzilla-daemon
2020-04-28  7:25 ` bugzilla-daemon
2020-04-28  8:01 ` bugzilla-daemon
2020-07-25  7:35 ` bugzilla-daemon
2021-07-26 20:35 ` bugzilla-daemon
2021-07-28 19:03 ` bugzilla-daemon
2021-08-01 19:43 ` bugzilla-daemon
2021-08-02 14:13 ` bugzilla-daemon
2021-08-02 14:24 ` bugzilla-daemon
2021-08-15 19:03 ` bugzilla-daemon
2021-08-25 16:03 ` bugzilla-daemon
2021-11-11 16:14 ` bugzilla-daemon
2021-11-11 16:15 ` bugzilla-daemon
2021-11-12  5:06 ` bugzilla-daemon
2021-11-12 19:29 ` bugzilla-daemon
2021-11-21 17:30 ` bugzilla-daemon
2021-11-22 14:50 ` bugzilla-daemon
2021-11-26 11:43 ` bugzilla-daemon
2021-11-27  2:51 ` bugzilla-daemon
2021-11-27 14:12 ` bugzilla-daemon
2021-11-28 14:32 ` bugzilla-daemon
2022-01-02  9:37 ` bugzilla-daemon
2022-03-06 12:34 ` bugzilla-daemon
2022-03-09 14:54 ` bugzilla-daemon
2022-03-13 17:46 ` bugzilla-daemon
2022-03-13 18:54 ` bugzilla-daemon
2022-03-21 17:07 ` bugzilla-daemon
2022-05-07  5:54 ` bugzilla-daemon
2022-05-07  6:28 ` bugzilla-daemon
2022-05-07  6:48 ` bugzilla-daemon
2022-05-08 19:23 ` bugzilla-daemon
2022-05-11  9:51 ` bugzilla-daemon
2022-05-27 11:22 ` bugzilla-daemon
2022-05-27 11:23 ` bugzilla-daemon
2022-05-30 12:39 ` bugzilla-daemon
2022-05-31 16:03 ` bugzilla-daemon
2022-05-31 18:34 ` bugzilla-daemon
2022-06-02 10:12 ` bugzilla-daemon
2022-09-09  4:08 ` bugzilla-daemon
2022-09-10  9:57 ` bugzilla-daemon
2022-10-07 21:41 ` bugzilla-daemon
2022-12-27  9:52 ` bugzilla-daemon
2022-12-27  9:53 ` bugzilla-daemon
2023-06-13 14:34 ` bugzilla-daemon
2023-07-01  5:10 ` bugzilla-daemon
2023-07-01  5:16 ` bugzilla-daemon
2023-07-11 13:14 ` bugzilla-daemon
2023-07-11 13:19 ` bugzilla-daemon
2023-09-07 17:31 ` bugzilla-daemon
2023-10-14 18:37 ` bugzilla-daemon
2023-10-15 12:09 ` bugzilla-daemon
2024-01-05 10:51 ` bugzilla-daemon [this message]
2024-12-13  1:06 ` bugzilla-daemon
2025-05-09 22:50 ` 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-205089-2300-T2vEovWl7b@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@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.