From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 201957] amdgpu: ring gfx timeout
Date: Mon, 24 Jan 2022 23:17:23 +0000 [thread overview]
Message-ID: <bug-201957-2300-8F5he1ILu2@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-201957-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=201957
--- Comment #57 from Spencer (smp@nandre.com) ---
Created attachment 300315
--> https://bugzilla.kernel.org/attachment.cgi?id=300315&action=edit
Kernel config
OS: Gentoo
Kernel: 5.15.16, config attached, built with make -j12
Launch options: root=/dev/sda2 ro quiet
I'd like to be able to boot with amdgpu.dpm=0, as this seems to fix the bug
with minor tradeoffs, however:
When I boot with dpm disabled, my screen will freeze and leave this nice little
stinker to ruin my day
Jan 24 16:33:05 [kernel] [ 2.572474] Loading firmware: amdgpu/navi10_pfp.bin
Jan 24 16:33:05 [kernel] [ 2.572475] Loading firmware: amdgpu/navi10_me.bin
Jan 24 16:33:05 [kernel] [ 2.572476] Loading firmware: amdgpu/navi10_ce.bin
Jan 24 16:33:05 [kernel] [ 2.572477] Loading firmware: amdgpu/navi10_rlc.bin
Jan 24 16:33:05 [kernel] [ 2.572477] Loading firmware: amdgpu/navi10_mec.bin
Jan 24 16:33:05 [kernel] [ 2.572478] Loading firmware:
amdgpu/navi10_mec2.bin
Jan 24 16:33:05 [kernel] [ 2.572968] EXT4-fs (sdb1): mounted filesystem with
ordered data mode. Opts: discard. Quota mode: none.
Jan 24 16:33:05 [kernel] [ 2.573030] Loading firmware:
amdgpu/navi10_sdma.bin
Jan 24 16:33:05 [kernel] [ 2.573032] Loading firmware:
amdgpu/navi10_sdma1.bin
Jan 24 16:33:05 [kernel] [ 2.573071] Loading firmware: amdgpu/navi10_vcn.bin
Jan 24 16:33:05 [kernel] [ 2.573072] [drm] Found VCN firmware Version ENC:
1.14 DEC: 5 VEP: 0 Revision: 20
Jan 24 16:33:05 [kernel] [ 2.573075] amdgpu 0000:28:00.0: amdgpu: Will use
PSP to load VCN firmware
Jan 24 16:33:05 [kernel] [ 2.747244] [drm] reserve 0x900000 from
0x817e400000 for PSP TMR
Jan 24 16:33:05 [kernel] [ 2.785931] amdgpu 0000:28:00.0: amdgpu: RAS:
optional ras ta ucode is not available
Jan 24 16:33:05 [kernel] [ 2.790137] amdgpu 0000:28:00.0: amdgpu: RAP:
optional rap ta ucode is not available
Jan 24 16:33:05 [kernel] [ 2.790138] amdgpu 0000:28:00.0: amdgpu:
SECUREDISPLAY: securedisplay ta ucode is not available
Jan 24 16:33:05 [kernel] [ 2.790140] amdgpu: smu firmware loading failed
Jan 24 16:33:05 [kernel] [ 2.790141] amdgpu 0000:28:00.0: amdgpu:
amdgpu_device_ip_init failed
Jan 24 16:33:05 [kernel] [ 2.790143] amdgpu 0000:28:00.0: amdgpu: Fatal
error during GPU init
Jan 24 16:33:05 [kernel] [ 2.790144] amdgpu 0000:28:00.0: amdgpu: amdgpu:
finishing device.
Jan 24 16:33:05 [kernel] [ 2.793726] [drm] free PSP TMR buffer
Jan 24 16:33:05 [kernel] [ 2.825874] amdgpu: probe of 0000:28:00.0 failed
with error -95
Jan 24 16:33:05 [kernel] [ 2.825951] BUG: unable to handle page fault for
address: ffffa4af5100d000
Jan 24 16:33:05 [kernel] [ 2.825954] #PF: supervisor write access in kernel
mode
Jan 24 16:33:05 [kernel] [ 2.825955] #PF: error_code(0x0002) - not-present
page
Jan 24 16:33:05 [kernel] [ 2.825957] PGD 100000067 P4D 100000067 PUD
100104067 PMD 0
Jan 24 16:33:05 [kernel] [ 2.825960] Oops: 0002 [#1] SMP NOPTI
Jan 24 16:33:05 [kernel] [ 2.825962] CPU: 6 PID: 759 Comm: systemd-udevd Not
tainted 5.15.16-gentoo #8
Jan 24 16:33:05 [kernel] [ 2.825965] Hardware name: Micro-Star International
Co., Ltd MS-7B86/B450 GAMING PLUS MAX (MS-7B86), BIOS H.60 04/18/2020
Jan 24 16:33:05 [kernel] [ 2.825967] RIP: 0010:vcn_v2_0_sw_fini+0x65/0x80
[amdgpu]
Jan 24 16:33:05 [kernel] [ 2.826139] Code: 89 ef e8 fe 1b ff ff 85 c0 75 08
48 89 ef e8 42 1a ff ff 48 8b 54 24 08 65 48 2b 14 25 28 00 00 00 75 18 48 83
c4 10 5b 5d c3 <c7> 03 00 00 00 00 8b 7c 24 04 e8 4c c4 4d e9 eb bc e8 15 cd ab
e9
Jan 24 16:33:05 [kernel] [ 2.826142] RSP: 0018:ffffa4af40bc7c30 EFLAGS:
00010202
TL;DR: amdgpu: smu firmware loading failed
What it means exactly, I know not, but I know it means my screen is frozen
Is there a trick? A workaround to this?
If there is some info I left out ask for it and I'll fetch it
--
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:[~2022-01-24 23:17 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
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 [this message]
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-8F5he1ILu2@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).