From: Steven J Abner <pheonix.sja@att.net>
To: linux-kernel@vger.kernel.org
Subject: amdgpu/drm boot blackout
Date: Thu, 08 Sep 2022 10:05:34 -0400 [thread overview]
Message-ID: <AT9WHR.3Z1T3VI9A2AQ3@att.net> (raw)
In-Reply-To: AT9WHR.3Z1T3VI9A2AQ3.ref@att.net
Hi
On boot up display has high probability of being NULL, but OS runs.
Hopefully enough to trace?
Linux version 5.18.19 (steven@steven-ryzen) (gcc (Ubuntu
9.4.0-1ubuntu1~20.04.1) 9.4.0, GNU ld (GNU Binutils for Ubuntu) 2.34)
#1 SMP PREEMPT_DYNAMIC Tue Sep 6 10:58:17 EDT 2022
note: not a ubuntu .config, building specific to AMD 2400g, actual
OS: elementary
ASRock Fatal1ty B450 Gaming-ITX/ac
AGESA PinnaclePI-AM4_1.0.0.4 afraid to update to AGESA to 1.0.0.6
'cause not on windows, nor have windows
microcode: CPUx: patch_level=0x0810100b
normal dmesg stuff, missing from journalctl:
ccp 0000:38:00.2: ccp enabled
ccp 0000:38:00.2: enabling device (0000 -> 0002)
ccp 0000:38:00.2: psp: unable to access the device: you might be
running a broken BIOS.
NOTE: broken BIOS a normal message according to AMD forum thread,
left for developers
after,which dmesg journalctl have: [drm] reserve 0x400000 from
0xf47fc00000 for PSP TMR
probable crash point next drm/amdgpu:
normal dmesg stuff, missing from journalctl:
amdgpu 0000:38:00.0: amdgpu: RAS: optional ras ta ucode is not available
amdgpu 0000:38:00.0: amdgpu: RAP: optional rap ta ucode is not available
amdgpu 0000:38:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is
not available
NOTE: according to internet searches, above not supported on raven
cpus
intro to all blackouts:
Sep 08 08:18:37 steven-ryzen kernel: [drm] psp gfx command
SETUP_TMR(0x5) failed and response status is (0x0)
Sep 08 08:18:37 steven-ryzen kernel: [drm:psp_hw_start.cold [amdgpu]]
*ERROR* PSP load tmr failed!
Sep 08 08:18:37 steven-ryzen kernel: [drm:psp_hw_init [amdgpu]] *ERROR*
PSP firmware loading failed
Sep 08 08:18:37 steven-ryzen kernel: [drm:amdgpu_device_fw_loading
[amdgpu]] *ERROR* hw_init of IP block <psp> failed -22
Sep 08 08:18:37 steven-ryzen kernel: amdgpu 0000:38:00.0: amdgpu:
amdgpu_device_ip_init failed
Sep 08 08:18:37 steven-ryzen kernel: amdgpu 0000:38:00.0: amdgpu: Fatal
error during GPU init
Sep 08 08:18:37 steven-ryzen kernel: amdgpu 0000:38:00.0: amdgpu:
amdgpu: finishing device.
Sep 08 08:18:37 steven-ryzen kernel: amdgpu: probe of 0000:38:00.0
failed with error -22
Sep 08 08:18:37 steven-ryzen kernel: BUG: kernel NULL pointer
dereference, address: 0000000000000090
Sep 08 08:18:37 steven-ryzen kernel: #PF: supervisor write access in
kernel mode
Sep 08 08:18:37 steven-ryzen kernel: #PF: error_code(0x0002) -
not-present page
Sep 08 08:18:37 steven-ryzen kernel: PGD 0 P4D 0
Sep 08 08:18:37 steven-ryzen kernel: Oops: 0002 [#1] PREEMPT SMP NOPTI
followed by slightly different:
Sep 08 06:56:39 steven-ryzen kernel: CPU: 4 PID: 128 Comm:
systemd-udevd Not tainted 5.18.19 #1
Sep 08 06:56:39 steven-ryzen kernel: Hardware name: To Be Filled By
O.E.M. To Be Filled By O.E.M./B450 Gaming-ITX/ac, BIOS P1.30 11/08/2018
Sep 08 06:56:39 steven-ryzen kernel: RIP: 0010:drm_sched_fini+0x7a/0xa0
[gpu_sched]
Sep 08 06:56:39 steven-ryzen kernel: Code: 01 00 00 e8 98 6d bb e3 c6
85 8c 01 00 00 00 5b 5d 41 5c 41 5d e9 a6 2c 55 e4 4c 89 e7 e8 ee 25 24
e4 48 8b 03 48 39 d8 74 0f <c6> 80 90 00 00 00 01 48 8b 00 48 39 d8 75
f1 4c 89 e7 e8 ff 21 24
Sep 08 06:56:39 steven-ryzen kernel: RSP: 0018:ffffb3e880493978 EFLAGS:
00010213
Sep 08 06:56:39 steven-ryzen kernel: RAX: 0000000000000000 RBX:
ffff91560ace9768 RCX: 0000000080400033
Sep 08 06:56:39 steven-ryzen kernel: RDX: 0000000000000001 RSI:
ffff91560b868468 RDI: ffff91560ace9758
Sep 08 06:56:39 steven-ryzen kernel: RBP: ffff91560ace96c0 R08:
ffff91560ace0014 R09: 0000000000000001
Sep 08 06:56:39 steven-ryzen kernel: R10: 000000000000001b R11:
ffff9156006a9b60 R12: ffff91560ace9758
Sep 08 06:56:39 steven-ryzen kernel: R13: ffff91560ace96c8 R14:
ffff91560ace6400 R15: ffff915600af9b48
Sep 08 06:56:39 steven-ryzen kernel: FS: 00007f2689dc8880(0000)
GS:ffff915698b00000(0000) knlGS:0000000000000000
Sep 08 06:56:39 steven-ryzen kernel: CS: 0010 DS: 0000 ES: 0000 CR0:
0000000080050033
Sep 08 06:56:39 steven-ryzen kernel: CR2: 0000000000000090 CR3:
0000000101834000 CR4: 00000000003506e0
Sep 08 06:56:39 steven-ryzen kernel: Call Trace:
Sep 08 06:56:39 steven-ryzen kernel: <TASK>
Sep 08 06:56:39 steven-ryzen kernel:
amdgpu_fence_driver_sw_fini+0xbf/0xd0 [amdgpu]
Sep 08 06:56:39 steven-ryzen kernel: amdgpu_device_fini_sw+0x22/0x300
[amdgpu]
Sep 08 06:56:39 steven-ryzen kernel: amdgpu_driver_release_kms+0xd/0x30
[amdgpu]
Sep 08 06:56:39 steven-ryzen kernel: drm_dev_release+0x1e/0x40 [drm]
Sep 08 06:56:39 steven-ryzen kernel: release_nodes+0x29/0x50
Sep 08 06:56:39 steven-ryzen kernel: devres_release_all+0x86/0xc0
Sep 08 06:56:39 steven-ryzen kernel: device_unbind_cleanup+0x9/0x70
Sep 08 06:56:39 steven-ryzen kernel: really_probe+0xee/0x210
Sep 08 06:56:39 steven-ryzen kernel: __driver_probe_device+0x6d/0xd0
Sep 08 06:56:39 steven-ryzen kernel: driver_probe_device+0x19/0xa0
Sep 08 06:56:39 steven-ryzen kernel: __driver_attach+0x5a/0xe0
Sep 08 06:56:39 steven-ryzen kernel: ? __device_attach_driver+0xa0/0xa0
Sep 08 06:56:39 steven-ryzen kernel: bus_for_each_dev+0x73/0xc0
Sep 08 06:56:39 steven-ryzen kernel: bus_add_driver+0x17c/0x1d0
Sep 08 06:56:39 steven-ryzen kernel: driver_register+0x67/0xc0
Sep 08 06:56:39 steven-ryzen kernel: ? 0xffffffffc0aa4000
Sep 08 06:56:39 steven-ryzen kernel: do_one_initcall+0x47/0x1a0
Sep 08 06:56:39 steven-ryzen kernel: ? kmem_cache_alloc+0x32/0x3b0
Sep 08 06:56:39 steven-ryzen kernel: do_init_module+0x41/0x1e0
Sep 08 06:56:39 steven-ryzen kernel: load_module+0x2597/0x2850
Sep 08 06:56:39 steven-ryzen kernel: ? __do_sys_finit_module+0xa6/0x100
Sep 08 06:56:39 steven-ryzen kernel: __do_sys_finit_module+0xa6/0x100
Sep 08 06:56:39 steven-ryzen kernel: do_syscall_64+0x5c/0x90
Sep 08 06:56:39 steven-ryzen kernel: ?
syscall_exit_to_user_mode+0x1d/0x40
Sep 08 06:56:39 steven-ryzen kernel: ? do_syscall_64+0x69/0x90
Sep 08 06:56:39 steven-ryzen kernel: ?
syscall_exit_to_user_mode+0x1d/0x40
Sep 08 06:56:39 steven-ryzen kernel: ? do_syscall_64+0x69/0x90
Sep 08 06:56:39 steven-ryzen kernel: ?
syscall_exit_to_user_mode+0x1d/0x40
Sep 08 06:56:39 steven-ryzen kernel: ? do_syscall_64+0x69/0x90
Sep 08 06:56:39 steven-ryzen kernel: ? do_syscall_64+0x69/0x90
Sep 08 06:56:39 steven-ryzen kernel: ? do_syscall_64+0x69/0x90
Sep 08 06:56:39 steven-ryzen kernel:
entry_SYSCALL_64_after_hwframe+0x49/0xb3
Sep 08 06:56:39 steven-ryzen kernel: RIP: 0033:0x7f268a3f273d
Sep 08 06:56:39 steven-ryzen kernel: Code: 00 c3 66 2e 0f 1f 84 00 00
00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d
89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 23 37
0d 00 f7 d8 64 89 01 48
Sep 08 06:56:39 steven-ryzen kernel: RSP: 002b:00007ffc1422a078 EFLAGS:
00000246 ORIG_RAX: 0000000000000139
Sep 08 06:56:39 steven-ryzen kernel: RAX: ffffffffffffffda RBX:
0000557a5aff83f0 RCX: 00007f268a3f273d
Sep 08 06:56:39 steven-ryzen kernel: RDX: 0000000000000000 RSI:
00007f268a2d2ded RDI: 0000000000000015
Sep 08 06:56:39 steven-ryzen kernel: RBP: 0000000000020000 R08:
0000000000000000 R09: 0000000000000000
Sep 08 06:56:39 steven-ryzen kernel: R10: 0000000000000015 R11:
0000000000000246 R12: 00007f268a2d2ded
Sep 08 06:56:39 steven-ryzen kernel: R13: 0000000000000000 R14:
0000557a5aff76d0 R15: 0000557a5aff83f0
Sep 08 06:56:39 steven-ryzen kernel: </TASK>
Sep 08 06:56:39 steven-ryzen kernel: Modules linked in: hid_generic
usbhid hid uas usb_storage amdgpu(+) drm_ttm_helper ttm mfd_core
gpu_sched drm_dp_helper drm_kms_helper drm xhci_pci igb i2c_piix4
drm_panel_orientation_quirks xhci_hcd nvme cec ptp nvme_core rc_core
pps_core usbcore i2c_algo_bit usb_common gpio_amdpt gpio_generic
Sep 08 06:56:39 steven-ryzen kernel: CR2: 0000000000000090
Sep 08 06:56:39 steven-ryzen kernel: ---[ end trace 0000000000000000
]---
Sep 08 06:56:39 steven-ryzen kernel: RIP: 0010:drm_sched_fini+0x7a/0xa0
[gpu_sched]
Sep 08 06:56:39 steven-ryzen kernel: Code: 01 00 00 e8 98 6d bb e3 c6
85 8c 01 00 00 00 5b 5d 41 5c 41 5d e9 a6 2c 55 e4 4c 89 e7 e8 ee 25 24
e4 48 8b 03 48 39 d8 74 0f <c6> 80 90 00 00 00 01 48 8b 00 48 39 d8 75
f1 4c 89 e7 e8 ff 21 24
Sep 08 06:56:39 steven-ryzen kernel: RSP: 0018:ffffb3e880493978 EFLAGS:
00010213
Sep 08 06:56:39 steven-ryzen kernel: RAX: 0000000000000000 RBX:
ffff91560ace9768 RCX: 0000000080400033
Sep 08 06:56:39 steven-ryzen kernel: RDX: 0000000000000001 RSI:
ffff91560b868468 RDI: ffff91560ace9758
Sep 08 06:56:39 steven-ryzen kernel: RBP: ffff91560ace96c0 R08:
ffff91560ace0014 R09: 0000000000000001
Sep 08 06:56:39 steven-ryzen kernel: R10: 000000000000001b R11:
ffff9156006a9b60 R12: ffff91560ace9758
Sep 08 06:56:39 steven-ryzen kernel: R13: ffff91560ace96c8 R14:
ffff91560ace6400 R15: ffff915600af9b48
Sep 08 06:56:39 steven-ryzen kernel: FS: 00007f2689dc8880(0000)
GS:ffff915698b00000(0000) knlGS:0000000000000000
Sep 08 06:56:39 steven-ryzen kernel: CS: 0010 DS: 0000 ES: 0000 CR0:
0000000080050033
Sep 08 06:56:39 steven-ryzen kernel: CR2: 0000000000000090 CR3:
0000000101834000 CR4: 00000000003506e0
do have more if needed, and doesn't seem hard to recreate:
./Documents/reboot-jctl
steven@steven-ryzen:~$ sudo journalctl -b -1 > ./Documents/jctl-1
steven@steven-ryzen:~$ sudo journalctl -b -2 > ./Documents/jctl-2
steven@steven-ryzen:~$ sudo journalctl -b -3 > ./Documents/jctl-3
steven@steven-ryzen:~$ sudo journalctl -b -4 > ./Documents/jctl-4
steven@steven-ryzen:~$ sudo journalctl -b -5 > ./Documents/jctl-5
steven@steven-ryzen:~$ sudo journalctl -b -6 > ./Documents/jctl-6
steven@steven-ryzen:~$ sudo journalctl -b -7 > ./Documents/jctl-7
Also, I don't think this occurs during ubuntu mainline builds.
Steve
parent reply other threads:[~2022-09-08 14:06 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <AT9WHR.3Z1T3VI9A2AQ3.ref@att.net>]
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=AT9WHR.3Z1T3VI9A2AQ3@att.net \
--to=pheonix.sja@att.net \
--cc=linux-kernel@vger.kernel.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.