From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 200531] amdgpu: *ERROR* REG_WAIT timeout when a display is put to sleep
Date: Wed, 05 Feb 2025 11:09:56 +0000 [thread overview]
Message-ID: <bug-200531-2300-PcrbFxAEhz@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-200531-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=200531
Ramses VdP (ramses@well-founded.dev) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ramses@well-founded.dev
--- Comment #13 from Ramses VdP (ramses@well-founded.dev) ---
This still happens on 6.13.1:
fév 05 10:07:39 framework kernel: amdgpu 0000:c1:00.0: [drm] REG_WAIT timeout
1us * 100 tries - dcn31_program_compbuf_size line:142
fév 05 10:07:39 framework kernel: ------------[ cut here ]------------
fév 05 10:07:39 framework kernel: WARNING: CPU: 11 PID: 2133 at
drivers/gpu/drm/amd/amdgpu/../display/dc/hubbub/dcn31/dcn31_hubbub.c:151
dcn31_program_compbuf_size+0xd2/0x240 [amdgpu]
fév 05 10:07:39 framework kernel: Modules linked in: rfcomm snd_seq_dummy
snd_hrtimer snd_seq ccm algif_aead crypto_null dummy wireguard des3_ede_x86_64
curve25519_x86_64 libchacha20poly1305 chacha_x86_64 poly>
fév 05 10:07:39 framework kernel: snd_hda_codec_generic
snd_hda_scodec_component snd_compress snd_usb_audio snd_hda_codec_hdmi ac97_bus
igc snd_pcm_dmaengine snd_rpl_pci_acp6x snd_acp_pci snd_acp_legacy_commo>
fév 05 10:07:39 framework kernel: serio_raw tcp_bbr sch_fq uinput tun tap
macvlan bridge stp llc kvm_amd ccp kvm fuse efi_pstore configfs nfnetlink zram
842_decompress 842_compress lz4hc_compress lz4_compress>
fév 05 10:07:39 framework kernel: CPU: 11 UID: 1000 PID: 2133 Comm: niri Not
tainted 6.13.1 #1-NixOS
fév 05 10:07:39 framework kernel: Hardware name: Framework Laptop 13 (AMD Ryzen
7040Series)/FRANMDCP07, BIOS 03.05 03/29/2024
fév 05 10:07:39 framework kernel: RIP:
0010:dcn31_program_compbuf_size+0xd2/0x240 [amdgpu]
fév 05 10:07:39 framework kernel: Code: 48 8b 43 28 8b 88 d8 01 00 00 48 8b 43
20 0f b6 50 76 48 8b 43 18 8b b0 14 01 00 00 e8 17 a1 0e 00 85 c0 0f 85 45 01
00 00 90 <0f> 0b 90 48 8b 44 24 08 65 48 2b 04 25 28>
fév 05 10:07:39 framework kernel: RSP: 0018:ffffab7d061d7708 EFLAGS: 00010202
fév 05 10:07:39 framework kernel: RAX: 0000000000000001 RBX: ffff951f435a3400
RCX: 0000000000000000
fév 05 10:07:39 framework kernel: RDX: 0000000000000000 RSI: 0000000000000000
RDI: 0000000000000000
fév 05 10:07:39 framework kernel: RBP: 0000000000000004 R08: 0000000000000000
R09: 0000000000000000
fév 05 10:07:39 framework kernel: R10: 0000000000000000 R11: 0000000000000000
R12: ffff952280200000
fév 05 10:07:39 framework kernel: R13: ffff951f5b400000 R14: ffff951f435a3400
R15: 0000000000000004
fév 05 10:07:39 framework kernel: FS: 00007fe2f88c5d00(0000)
GS:ffff952e1ff80000(0000) knlGS:0000000000000000
fév 05 10:07:39 framework kernel: CS: 0010 DS: 0000 ES: 0000 CR0:
0000000080050033
fév 05 10:07:39 framework kernel: CR2: 0000556b362d7dc0 CR3: 00000004319ec000
CR4: 0000000000f50ef0
fév 05 10:07:39 framework kernel: PKRU: 55555554
fév 05 10:07:39 framework kernel: Call Trace:
fév 05 10:07:39 framework kernel: <TASK>
fév 05 10:07:39 framework kernel: ? dcn31_program_compbuf_size+0xd2/0x240
[amdgpu]
fév 05 10:07:39 framework kernel: ? __warn.cold+0x93/0xf6
fév 05 10:07:39 framework kernel: ? dcn31_program_compbuf_size+0xd2/0x240
[amdgpu]
fév 05 10:07:39 framework kernel: ? report_bug+0x10d/0x150
fév 05 10:07:39 framework kernel: ? handle_bug+0x61/0xb0
fév 05 10:07:39 framework kernel: ? exc_invalid_op+0x17/0x80
fév 05 10:07:39 framework kernel: ? asm_exc_invalid_op+0x1a/0x20
fév 05 10:07:39 framework kernel: ? dcn31_program_compbuf_size+0xd2/0x240
[amdgpu]
fév 05 10:07:39 framework kernel: ? dcn31_program_compbuf_size+0xc9/0x240
[amdgpu]
fév 05 10:07:39 framework kernel: dcn20_optimize_bandwidth+0xe4/0x240 [amdgpu]
fév 05 10:07:39 framework kernel: dc_commit_state_no_check+0xc6c/0xeb0
[amdgpu]
fév 05 10:07:39 framework kernel: dc_commit_streams+0x283/0x470 [amdgpu]
fév 05 10:07:39 framework kernel: amdgpu_dm_atomic_commit_tail+0x67d/0x3760
[amdgpu]
fév 05 10:07:39 framework kernel: ? dcn314_validate_bandwidth+0x100/0x2c0
[amdgpu]
fév 05 10:07:39 framework kernel: ? srso_alias_return_thunk+0x5/0xfbef5
fév 05 10:07:39 framework kernel: ? amdgpu_dm_atomic_check+0x161f/0x1800
[amdgpu]
fév 05 10:07:39 framework kernel: ? srso_alias_return_thunk+0x5/0xfbef5
fév 05 10:07:39 framework kernel: ? __wait_for_common+0x192/0x1d0
fév 05 10:07:39 framework kernel: ? __pfx_schedule_timeout+0x10/0x10
fév 05 10:07:39 framework kernel: commit_tail+0x91/0x130
fév 05 10:07:39 framework kernel: drm_atomic_helper_commit+0x126/0x150
fév 05 10:07:39 framework kernel: drm_atomic_commit+0xaf/0xf0
fév 05 10:07:39 framework kernel: ? __pfx___drm_printfn_info+0x10/0x10
fév 05 10:07:39 framework kernel: drm_mode_atomic_ioctl+0xada/0xd30
fév 05 10:07:39 framework kernel: ? __wake_up_sync_key+0x3b/0x60
fév 05 10:07:39 framework kernel: ? __pfx_drm_mode_atomic_ioctl+0x10/0x10
fév 05 10:07:39 framework kernel: drm_ioctl_kernel+0xb5/0x110
fév 05 10:07:39 framework kernel: drm_ioctl+0x288/0x4e0
fév 05 10:07:39 framework kernel: ? __pfx_drm_mode_atomic_ioctl+0x10/0x10
fév 05 10:07:39 framework kernel: amdgpu_drm_ioctl+0x4b/0x90 [amdgpu]
fév 05 10:07:39 framework kernel: __x64_sys_ioctl+0xa0/0xe0
fév 05 10:07:39 framework kernel: do_syscall_64+0xb7/0x210
fév 05 10:07:39 framework kernel: entry_SYSCALL_64_after_hwframe+0x77/0x7f
fév 05 10:07:39 framework kernel: RIP: 0033:0x556b36a97c4c
fév 05 10:07:39 framework kernel: Code: 4c 89 6c 24 18 4c 89 64 24 20 4c 89 74
24 28 0f 57 c0 0f 11 44 24 30 89 c7 48 8d 54 24 08 b8 10 00 00 00 be bc 64 38
c0 0f 05 <49> 89 c7 48 83 3b 00 74 09 4c 89 c7 ff 15>
fév 05 10:07:39 framework kernel: RSP: 002b:00007ffc5fd86420 EFLAGS: 00000213
ORIG_RAX: 0000000000000010
fév 05 10:07:39 framework kernel: RAX: ffffffffffffffda RBX: 00007ffc5fd864c0
RCX: 0000556b36a97c4c
fév 05 10:07:39 framework kernel: RDX: 00007ffc5fd86428 RSI: 00000000c03864bc
RDI: 0000000000000028
fév 05 10:07:39 framework kernel: RBP: 0000000000000000 R08: 0000556b63cc7fd0
R09: 0000000000000001
fév 05 10:07:39 framework kernel: R10: 0000000000000000 R11: 0000000000000213
R12: 0000556b63da5590
fév 05 10:07:39 framework kernel: R13: 0000556b63cc7ff0 R14: 0000556b640923f0
R15: 0000000000000000
fév 05 10:07:39 framework kernel: </TASK>
fév 05 10:07:39 framework kernel: ---[ end trace 0000000000000000 ]---
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2025-02-05 11:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-18 0:41 [Bug 200531] New: amdgpu: *ERROR* REG_WAIT timeout when a display is put to sleep bugzilla-daemon
2018-07-18 0:41 ` [Bug 200531] " bugzilla-daemon
2018-07-18 0:56 ` bugzilla-daemon
2018-07-18 0:58 ` bugzilla-daemon
2018-07-18 7:36 ` bugzilla-daemon
2018-07-18 7:36 ` bugzilla-daemon
2018-07-22 13:16 ` bugzilla-daemon
2018-07-22 16:24 ` bugzilla-daemon
2018-08-26 0:53 ` bugzilla-daemon
2018-09-03 5:20 ` bugzilla-daemon
2018-09-04 14:35 ` bugzilla-daemon
2018-09-05 9:14 ` bugzilla-daemon
2018-09-11 14:15 ` bugzilla-daemon
2018-12-10 2:44 ` bugzilla-daemon
2018-12-31 15:16 ` bugzilla-daemon
2025-02-05 11:09 ` bugzilla-daemon [this message]
2025-05-26 13:15 ` bugzilla-daemon
2025-05-27 21:39 ` 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-200531-2300-PcrbFxAEhz@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.