How best to identify useful data after system crash?

English Applications
,
1

Continuing the discussion from https://forums.opensuse.org/t/where-to-report-xwayland-crash-the-cause-matters-right/172543:

I’m now somewhat consistently getting something similar when running steam steam://rungameid/236390. Although I can run try to debug it via sh -c 'DEBUGGER=gdb steam', I never get the opportunity to bt it because the entire system seemingly hangs (I can’t even switch TTYs). However, it automatically reboots after about 20 seconds, and does respond to SysRq requests, so I’ve hope that it’s at least logging during all of that.

However, I’ve been looking at journalctl -b -1 --dmesg with -p 1 to -p 4, and see little of use:

PS /home/RokeJulianLockhart> journalctl -b -1 --dmesg -p 1
-- No entries --
PS /home/RokeJulianLockhart> journalctl -b -1 --dmesg -p 2
-- No entries --
PS /home/RokeJulianLockhart> journalctl -b -1 --dmesg -p 3
Mar 25 12:03:34 s1e8h4 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPC0.EC0], AE_NOT_FOUND (20230628/dswload2-162)
Mar 25 12:03:34 s1e8h4 kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20230628/psobject-220)
Mar 25 12:03:34 s1e8h4 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.GPP0._PRW], AE_ALREADY_EXISTS (20230628/dswload2-326)
Mar 25 12:03:34 s1e8h4 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220)
Mar 25 12:03:34 s1e8h4 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.GPP2._PRW], AE_ALREADY_EXISTS (20230628/dswload2-326)
Mar 25 12:03:34 s1e8h4 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220)
Mar 25 12:03:34 s1e8h4 kernel: ACPI BIOS Error (bug): Failure creating named object [\_GPE._L08], AE_ALREADY_EXISTS (20230628/dswload2-326)
Mar 25 12:03:34 s1e8h4 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220)
Mar 25 12:03:35 s1e8h4 kernel: hub 12-0:1.0: config failed, hub doesn't have any ports! (err -19)
Mar 25 12:03:38 s1e8h4 kernel: usbhid 5-6.2:1.2: couldn't find an input interrupt endpoint
Mar 25 12:03:43 s1e8h4 kernel: Bluetooth: hci0: No support for _PRR ACPI method
Mar 25 12:03:43 s1e8h4 kernel: Bluetooth: hci1: No support for _PRR ACPI method
Mar 25 12:03:43 s1e8h4 kernel: iwlwifi 0000:45:00.0: WRT: Invalid buffer destination
Mar 25 12:03:44 s1e8h4 kernel: iwlwifi 0000:4a:00.0: WRT: Invalid buffer destination
Mar 25 12:03:45 s1e8h4 kernel: iwlwifi 0000:45:00.0: WRT: Invalid buffer destination
Mar 25 12:03:45 s1e8h4 kernel: iwlwifi 0000:45:00.0: WRT: Invalid buffer destination
Mar 25 12:03:45 s1e8h4 kernel: iwlwifi 0000:4a:00.0: WRT: Invalid buffer destination
Mar 25 12:03:46 s1e8h4 kernel: iwlwifi 0000:4a:00.0: WRT: Invalid buffer destination
Mar 25 12:03:47 s1e8h4 kernel: Bluetooth: hci1: Malformed MSFT vendor event: 0x02
Mar 25 12:03:53 s1e8h4 kernel: iwlwifi 0000:4a:00.0: WRT: Invalid buffer destination
PS /home/RokeJulianLockhart> journalctl -b -1 --dmesg -p 4
Mar 25 12:03:34 s1e8h4 kernel: Speculative Return Stack Overflow: IBPB-extending microcode not applied!
Mar 25 12:03:34 s1e8h4 kernel: Speculative Return Stack Overflow: WARNING: See https://kernel.org/doc/html/latest/admin-guide/hw-vuln/srso.html for mitigation options.
Mar 25 12:03:34 s1e8h4 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPC0.EC0], AE_NOT_FOUND (20230628/dswload2-162)
Mar 25 12:03:34 s1e8h4 kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20230628/psobject-220)
Mar 25 12:03:34 s1e8h4 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.GPP0._PRW], AE_ALREADY_EXISTS (20230628/dswload2-326)
Mar 25 12:03:34 s1e8h4 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220)
Mar 25 12:03:34 s1e8h4 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.GPP2._PRW], AE_ALREADY_EXISTS (20230628/dswload2-326)
Mar 25 12:03:34 s1e8h4 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220)
Mar 25 12:03:34 s1e8h4 kernel: ACPI BIOS Error (bug): Failure creating named object [\_GPE._L08], AE_ALREADY_EXISTS (20230628/dswload2-326)
Mar 25 12:03:34 s1e8h4 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220)
Mar 25 12:03:34 s1e8h4 systemd[1]: /usr/lib/systemd/system/plymouth-start.service:15: Unit uses KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update the service to use a safer KillMode=, such as 'mixed' or '>
Mar 25 12:03:35 s1e8h4 kernel: nvme nvme0: missing or invalid SUBNQN field.
Mar 25 12:03:35 s1e8h4 kernel: nvme nvme3: missing or invalid SUBNQN field.
Mar 25 12:03:35 s1e8h4 kernel: nvme nvme1: missing or invalid SUBNQN field.
Mar 25 12:03:35 s1e8h4 kernel: hub 12-0:1.0: config failed, hub doesn't have any ports! (err -19)
Mar 25 12:03:37 s1e8h4 kernel: [drm] Fence fallback timer expired on ring sdma0
Mar 25 12:03:38 s1e8h4 kernel: [drm] Fence fallback timer expired on ring sdma0
Mar 25 12:03:38 s1e8h4 kernel: usbhid 5-6.2:1.2: couldn't find an input interrupt endpoint
Mar 25 12:03:38 s1e8h4 kernel: ------------[ cut here ]------------
Mar 25 12:03:38 s1e8h4 kernel: WARNING: CPU: 6 PID: 447 at drivers/gpu/drm/amd/amdgpu/../display/dc/link/protocols/link_dp_capability.c:1532 dp_retrieve_lttpr_cap+0x117/0x1e0 [amdgpu]
Mar 25 12:03:38 s1e8h4 kernel: Modules linked in: hid_generic(+) uas usb_storage usbhid amdgpu(+) crct10dif_pclmul crc32_pclmul ahci polyval_clmulni polyval_generic gf128mul libahci libata ghash_clmulni_intel sha512_ssse3 sd_mod scsi_dh_emc sha256_ssse3 scsi_dh_rdac xhc>
Mar 25 12:03:38 s1e8h4 kernel: CPU: 6 PID: 447 Comm: (udev-worker) Not tainted 6.8.1-1-default #1 openSUSE Tumbleweed a408dede100ecd8172a7eae2d0778227ac69e46d
Mar 25 12:03:38 s1e8h4 kernel: Hardware name: ASRock X670E Taichi/X670E Taichi, BIOS 1.21 04/26/2023
Mar 25 12:03:38 s1e8h4 kernel: RIP: 0010:dp_retrieve_lttpr_cap+0x117/0x1e0 [amdgpu]
Mar 25 12:03:38 s1e8h4 kernel: Code: 48 21 c8 48 c1 e2 38 48 09 d0 48 89 85 98 02 00 00 f6 85 c4 02 00 00 02 74 42 e8 d4 ed ff ff 84 c0 75 39 48 8b 85 d8 01 00 00 <0f> 0b c6 85 9c 02 00 00 80 48 8b 40 10 48 8b 30 48 85 f6 74 04 48
Mar 25 12:03:38 s1e8h4 kernel: RSP: 0018:ffffb26d803df5f0 EFLAGS: 00010246
Mar 25 12:03:38 s1e8h4 kernel: RAX: ffff8d7a749b2b00 RBX: 00000000ffffffff RCX: 00ffffffffffffff
Mar 25 12:03:38 s1e8h4 kernel: RDX: ff00000000000000 RSI: ffffb26d803df5f0 RDI: 0000000000000005
Mar 25 12:03:38 s1e8h4 kernel: RBP: ffff8d7a550a0000 R08: ffff8d7a74c195c0 R09: 0000000000000000
Mar 25 12:03:38 s1e8h4 kernel: R10: 0000000000000002 R11: ffff8d8178739364 R12: 0000000000000001
Mar 25 12:03:38 s1e8h4 kernel: R13: 0000000000000001 R14: ffff8d7a749b2b00 R15: ffff8d7a550a0800
Mar 25 12:03:38 s1e8h4 kernel: FS:  00007f8764d5c900(0000) GS:ffff8d8178700000(0000) knlGS:0000000000000000
Mar 25 12:03:38 s1e8h4 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Mar 25 12:03:38 s1e8h4 kernel: CR2: 00007f8764c94000 CR3: 0000000109258000 CR4: 0000000000750ef0
Mar 25 12:03:38 s1e8h4 kernel: PKRU: 55555554
Mar 25 12:03:38 s1e8h4 kernel: Call Trace:
Mar 25 12:03:38 s1e8h4 kernel:  <TASK>
Mar 25 12:03:38 s1e8h4 kernel:  ? dp_retrieve_lttpr_cap+0x117/0x1e0 [amdgpu 40787fed05d502b71939fdae86356ec27c02d23a]
Mar 25 12:03:38 s1e8h4 kernel:  ? __warn+0x81/0x130
Mar 25 12:03:38 s1e8h4 kernel:  ? dp_retrieve_lttpr_cap+0x117/0x1e0 [amdgpu 40787fed05d502b71939fdae86356ec27c02d23a]
Mar 25 12:03:38 s1e8h4 kernel:  ? report_bug+0x171/0x1a0
Mar 25 12:03:38 s1e8h4 kernel:  ? handle_bug+0x3c/0x80
Mar 25 12:03:38 s1e8h4 kernel:  ? exc_invalid_op+0x17/0x70
Mar 25 12:03:38 s1e8h4 kernel:  ? asm_exc_invalid_op+0x1a/0x20
Mar 25 12:03:38 s1e8h4 kernel:  ? dp_retrieve_lttpr_cap+0x117/0x1e0 [amdgpu 40787fed05d502b71939fdae86356ec27c02d23a]
Mar 25 12:03:38 s1e8h4 kernel:  ? try_to_configure_aux_timeout+0x7c/0xe0 [amdgpu 40787fed05d502b71939fdae86356ec27c02d23a]
Mar 25 12:03:38 s1e8h4 kernel:  retrieve_link_cap+0x61/0xd40 [amdgpu 40787fed05d502b71939fdae86356ec27c02d23a]
Mar 25 12:03:38 s1e8h4 kernel:  ? __entry_text_end+0xfddd5/0x101ed9
Mar 25 12:03:38 s1e8h4 kernel:  ? dal_gpio_close+0x1e/0x30 [amdgpu 40787fed05d502b71939fdae86356ec27c02d23a]
Mar 25 12:03:38 s1e8h4 kernel:  detect_link_and_local_sink+0xce4/0x10e0 [amdgpu 40787fed05d502b71939fdae86356ec27c02d23a]
Mar 25 12:03:38 s1e8h4 kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Mar 25 12:03:38 s1e8h4 kernel:  ? dm_write_reg_func+0x22/0x80 [amdgpu 40787fed05d502b71939fdae86356ec27c02d23a]
Mar 25 12:03:38 s1e8h4 kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Mar 25 12:03:38 s1e8h4 kernel:  ? dm_write_reg_func+0x22/0x80 [amdgpu 40787fed05d502b71939fdae86356ec27c02d23a]
Mar 25 12:03:38 s1e8h4 kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Mar 25 12:03:38 s1e8h4 kernel:  ? generic_reg_update_ex+0xb0/0x1d0 [amdgpu 40787fed05d502b71939fdae86356ec27c02d23a]
Mar 25 12:03:38 s1e8h4 kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Mar 25 12:03:38 s1e8h4 kernel:  ? dm_read_reg_func+0x38/0xb0 [amdgpu 40787fed05d502b71939fdae86356ec27c02d23a]
Mar 25 12:03:38 s1e8h4 kernel:  link_detect+0x3a/0x4f0 [amdgpu 40787fed05d502b71939fdae86356ec27c02d23a]
Mar 25 12:03:38 s1e8h4 kernel:  ? dal_gpio_destroy_irq+0x25/0x40 [amdgpu 40787fed05d502b71939fdae86356ec27c02d23a]
Mar 25 12:03:38 s1e8h4 kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Mar 25 12:03:38 s1e8h4 kernel:  ? query_hpd_status+0x6e/0xa0 [amdgpu 40787fed05d502b71939fdae86356ec27c02d23a]
Mar 25 12:03:38 s1e8h4 kernel:  amdgpu_dm_init.isra.0+0x10ee/0x2070 [amdgpu 40787fed05d502b71939fdae86356ec27c02d23a]
Mar 25 12:03:38 s1e8h4 kernel:  ? __pfx_enable_assr+0x10/0x10 [amdgpu 40787fed05d502b71939fdae86356ec27c02d23a]
Mar 25 12:03:38 s1e8h4 kernel:  ? __pfx_update_config+0x10/0x10 [amdgpu 40787fed05d502b71939fdae86356ec27c02d23a]
Mar 25 12:03:38 s1e8h4 kernel:  dm_hw_init+0x12/0x30 [amdgpu 40787fed05d502b71939fdae86356ec27c02d23a]
Mar 25 12:03:38 s1e8h4 kernel:  amdgpu_device_init+0x1dff/0x24b0 [amdgpu 40787fed05d502b71939fdae86356ec27c02d23a]
Mar 25 12:03:38 s1e8h4 kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Mar 25 12:03:38 s1e8h4 kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Mar 25 12:03:38 s1e8h4 kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Mar 25 12:03:38 s1e8h4 kernel:  ? pci_bus_read_config_word+0x4a/0x90
Mar 25 12:03:38 s1e8h4 kernel:  amdgpu_driver_load_kms+0x19/0x190 [amdgpu 40787fed05d502b71939fdae86356ec27c02d23a]
Mar 25 12:03:38 s1e8h4 kernel:  amdgpu_pci_probe+0x18b/0x510 [amdgpu 40787fed05d502b71939fdae86356ec27c02d23a]
Mar 25 12:03:38 s1e8h4 kernel:  local_pci_probe+0x42/0xa0
Mar 25 12:03:38 s1e8h4 kernel:  pci_device_probe+0xc7/0x240
Mar 25 12:03:38 s1e8h4 kernel:  really_probe+0x19b/0x3e0
Mar 25 12:03:38 s1e8h4 kernel:  ? __pfx___driver_attach+0x10/0x10
Mar 25 12:03:38 s1e8h4 kernel:  __driver_probe_device+0x78/0x160
Mar 25 12:03:38 s1e8h4 kernel:  driver_probe_device+0x1f/0x90
Mar 25 12:03:38 s1e8h4 kernel:  __driver_attach+0xd2/0x1c0
Mar 25 12:03:38 s1e8h4 kernel:  bus_for_each_dev+0x74/0xc0
Mar 25 12:03:38 s1e8h4 kernel:  bus_add_driver+0x116/0x220
Mar 25 12:03:38 s1e8h4 kernel:  driver_register+0x59/0x100
Mar 25 12:03:38 s1e8h4 kernel:  ? __pfx_amdgpu_init+0x10/0x10 [amdgpu 40787fed05d502b71939fdae86356ec27c02d23a]
Mar 25 12:03:38 s1e8h4 kernel:  do_one_initcall+0x45/0x310
Mar 25 12:03:38 s1e8h4 kernel:  ? do_init_module+0x22/0x240
Mar 25 12:03:38 s1e8h4 kernel:  do_init_module+0x60/0x240
Mar 25 12:03:38 s1e8h4 kernel:  __do_sys_init_module+0x17f/0x1b0
Mar 25 12:03:38 s1e8h4 kernel:  ? __seccomp_filter+0x31b/0x4e0
Mar 25 12:03:38 s1e8h4 kernel:  do_syscall_64+0x86/0x170
Mar 25 12:03:38 s1e8h4 kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Mar 25 12:03:38 s1e8h4 kernel:  ? syscall_exit_to_user_mode+0x80/0x230
Mar 25 12:03:38 s1e8h4 kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Mar 25 12:03:38 s1e8h4 kernel:  ? do_syscall_64+0x96/0x170
Mar 25 12:03:38 s1e8h4 kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Mar 25 12:03:38 s1e8h4 kernel:  ? ksys_read+0x67/0xe0
Mar 25 12:03:38 s1e8h4 kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Mar 25 12:03:38 s1e8h4 kernel:  ? syscall_exit_to_user_mode+0x80/0x230
Mar 25 12:03:38 s1e8h4 kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Mar 25 12:03:38 s1e8h4 kernel:  ? do_syscall_64+0x96/0x170
Mar 25 12:03:38 s1e8h4 kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Mar 25 12:03:38 s1e8h4 kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Mar 25 12:03:38 s1e8h4 kernel:  entry_SYSCALL_64_after_hwframe+0x6e/0x76
Mar 25 12:03:38 s1e8h4 kernel: RIP: 0033:0x7f87658ac5be
Mar 25 12:03:38 s1e8h4 kernel: Code: c3 66 2e 0f 1f 84 00 00 00 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3 0f 1e fa 66 90 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 2a 98 0d 00 f7 d8 64 89 01 48
Mar 25 12:03:38 s1e8h4 kernel: RSP: 002b:00007fff04372538 EFLAGS: 00000246 ORIG_RAX: 00000000000000af
Mar 25 12:03:38 s1e8h4 kernel: RAX: ffffffffffffffda RBX: 0000558604473ac0 RCX: 00007f87658ac5be
Mar 25 12:03:38 s1e8h4 kernel: RDX: 00007f87659b2061 RSI: 00000000019d5e43 RDI: 00007f8762a00010
Mar 25 12:03:38 s1e8h4 kernel: RBP: 00007f87659b2061 R08: 0000000000000940 R09: 0000000000000000
Mar 25 12:03:38 s1e8h4 kernel: R10: 00007f8765986b20 R11: 0000000000000246 R12: 0000000000020000
Mar 25 12:03:38 s1e8h4 kernel: R13: 0000000000000000 R14: 0000558604476b40 R15: 0000000000000000
Mar 25 12:03:38 s1e8h4 kernel:  </TASK>
Mar 25 12:03:38 s1e8h4 kernel: ---[ end trace 0000000000000000 ]---
Mar 25 12:03:42 s1e8h4 systemd[1]: /usr/lib/systemd/system/plymouth-start.service:15: Unit uses KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update the service to use a safer KillMode=, such as 'mixed' or '>
Mar 25 12:03:43 s1e8h4 kernel: Bluetooth: hci0: No support for _PRR ACPI method
Mar 25 12:03:43 s1e8h4 kernel: Bluetooth: hci1: No support for _PRR ACPI method
Mar 25 12:03:43 s1e8h4 kernel: thermal thermal_zone0: failed to read out thermal zone (-61)
Mar 25 12:03:43 s1e8h4 kernel: iwlwifi 0000:45:00.0: WRT: Invalid buffer destination
Mar 25 12:03:44 s1e8h4 kernel: usb 5-6.2: Warning! Unlikely big volume range (=3996), cval->res is probably wrong.
Mar 25 12:03:44 s1e8h4 kernel: usb 5-6.2: [5] FU [Mic Capture Volume] ch = 1, val = 0/3996/1
Mar 25 12:03:44 s1e8h4 kernel: thermal thermal_zone1: failed to read out thermal zone (-61)
Mar 25 12:03:44 s1e8h4 kernel: iwlwifi 0000:4a:00.0: WRT: Invalid buffer destination
Mar 25 12:03:44 s1e8h4 kernel: vboxdrv: loading out-of-tree module taints kernel.
Mar 25 12:03:45 s1e8h4 kernel: VBoxNetFlt: Successfully started.
Mar 25 12:03:45 s1e8h4 kernel: VBoxNetAdp: Successfully started.
Mar 25 12:03:45 s1e8h4 kernel: iwlwifi 0000:45:00.0: WRT: Invalid buffer destination
Mar 25 12:03:45 s1e8h4 kernel: ACPI: \: failed to evaluate _DSM bf0212f2-788f-c64d-a5b3-1f738e285ade (0x1001)
Mar 25 12:03:45 s1e8h4 kernel: ACPI: \: failed to evaluate _DSM bf0212f2-788f-c64d-a5b3-1f738e285ade (0x1001)
Mar 25 12:03:45 s1e8h4 kernel: ACPI: \: failed to evaluate _DSM bf0212f2-788f-c64d-a5b3-1f738e285ade (0x1001)
Mar 25 12:03:45 s1e8h4 kernel: ACPI: \: failed to evaluate _DSM bf0212f2-788f-c64d-a5b3-1f738e285ade (0x1001)
Mar 25 12:03:45 s1e8h4 kernel: ACPI: \: failed to evaluate _DSM bf0212f2-788f-c64d-a5b3-1f738e285ade (0x1001)
Mar 25 12:03:45 s1e8h4 kernel: ACPI: \: failed to evaluate _DSM bf0212f2-788f-c64d-a5b3-1f738e285ade (0x1001)
Mar 25 12:03:45 s1e8h4 kernel: ACPI: \: failed to evaluate _DSM bf0212f2-788f-c64d-a5b3-1f738e285ade (0x1001)
Mar 25 12:03:45 s1e8h4 kernel: ACPI: \: failed to evaluate _DSM bf0212f2-788f-c64d-a5b3-1f738e285ade (0x1001)
Mar 25 12:03:45 s1e8h4 kernel: iwlwifi 0000:45:00.0: WRT: Invalid buffer destination
Mar 25 12:03:45 s1e8h4 kernel: ACPI: \: failed to evaluate _DSM bf0212f2-788f-c64d-a5b3-1f738e285ade (0x1001)
Mar 25 12:03:45 s1e8h4 kernel: ACPI: \: failed to evaluate _DSM bf0212f2-788f-c64d-a5b3-1f738e285ade (0x1001)
Mar 25 12:03:45 s1e8h4 kernel: ACPI: \: failed to evaluate _DSM bf0212f2-788f-c64d-a5b3-1f738e285ade (0x1001)
Mar 25 12:03:45 s1e8h4 kernel: ACPI: \: failed to evaluate _DSM bf0212f2-788f-c64d-a5b3-1f738e285ade (0x1001)
Mar 25 12:03:45 s1e8h4 kernel: ACPI: \: failed to evaluate _DSM bf0212f2-788f-c64d-a5b3-1f738e285ade (0x1001)
Mar 25 12:03:45 s1e8h4 kernel: ACPI: \: failed to evaluate _DSM bf0212f2-788f-c64d-a5b3-1f738e285ade (0x1001)
Mar 25 12:03:45 s1e8h4 kernel: ACPI: \: failed to evaluate _DSM bf0212f2-788f-c64d-a5b3-1f738e285ade (0x1001)
Mar 25 12:03:45 s1e8h4 kernel: ACPI: \: failed to evaluate _DSM bf0212f2-788f-c64d-a5b3-1f738e285ade (0x1001)
Mar 25 12:03:45 s1e8h4 kernel: iwlwifi 0000:4a:00.0: WRT: Invalid buffer destination
Mar 25 12:03:46 s1e8h4 kernel: iwlwifi 0000:4a:00.0: WRT: Invalid buffer destination
Mar 25 12:03:46 s1e8h4 kernel: xhci_hcd 0000:57:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Mar 25 12:03:47 s1e8h4 kernel: Bluetooth: hci1: Malformed MSFT vendor event: 0x02
Mar 25 12:03:53 s1e8h4 kernel: iwlwifi 0000:4a:00.0: WRT: Invalid buffer destination
Mar 25 12:03:53 s1e8h4 kernel: FAT-fs (sdd1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Mar 25 12:03:55 s1e8h4 kernel: warning: `ckb-next' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211
Mar 25 14:42:36 s1e8h4 kernel: xhci_hcd 0000:57:00.0: WARN Event TRB for slot 3 ep 4 with no TDs queued?
Mar 25 21:38:56 s1e8h4 kernel: hid-generic 0005:054C:0DF0.000C: unknown main item tag 0x0
Mar 25 21:38:56 s1e8h4 kernel: hid-sensor-hub 0005:054C:0DF0.000C: unknown main item tag 0x0
Mar 25 21:39:06 s1e8h4 kernel: hid-sensor-hub 0005:054C:0DF0.000D: unknown main item tag 0x0

despite the fact that I surely should have some kind of logs indicating such a catastrophic failure.

2

There’s also nothing in coredumpctl.

3

@rokejulianlockhart so you don’t use gdb steam then at the prompt run? Untaint the kernel, does it duplicate.

Only way would be for you to remote in and then tail the journal… assuming your logging is set to persitant?

1 Like
4

Regarding kernel crashes, look into

(I was directed to that page by Anthony Iliopoulos in 1220814 – kernel 6.7.6-1-default Oops: unable to handle page faults and workqueue lockup (udev related?) and can confirm that it applies to tumbleweed as well.)

1 Like
5

@malcolmlewis, that doesn’t work for steam. I don’t know why, but considering that Steam/Troubleshooting - ArchWiki lists it as the way to do so, it seems like it’s at least expected. Trying to invoke steam with gdb directly informs the user that it’s not a binary, which is correct — the steam in $Env:PATH is a symbolic link to a .sh file.

Know where I can read about that? I do have a tablet and laptop running TW too, and a phone with https://github.com/termux/termux-app/releases/download/v0.118.0/termux-app_v0.118.0+github-debug_arm64-v8a.apk (from https://f-droid.org/repo/com.termux_118.apk).

It appears to be:

journalctl --list-boots

IDX BOOT ID                          FIRST ENTRY                 LAST ENTRY                 
-21 1d2420f266ae4c808a868a2b4efc3611 Wed 2024-03-13 23:58:09 GMT Thu 2024-03-14 00:32:50 GMT
-20 7e42854a86a044e0b2f0b84484b49606 Thu 2024-03-14 11:59:58 GMT Fri 2024-03-15 01:52:17 GMT
-19 47ae3727c524498f8052af079b1748eb Fri 2024-03-15 15:31:02 GMT Fri 2024-03-15 22:51:54 GMT
-18 9aca5c306d8f4f178bc81b76e65a538d Fri 2024-03-15 22:54:12 GMT Sat 2024-03-16 00:36:42 GMT
-17 c0ca293fbfd14d5893b3989460a4ccc3 Sat 2024-03-16 10:23:57 GMT Sun 2024-03-17 08:51:24 GMT
-16 8324909ae0714821ae82d3808f542494 Sun 2024-03-17 11:47:24 GMT Sun 2024-03-17 21:35:54 GMT
-15 74b5d2d978fa4c9a8012b4cd7e52b8ef Sun 2024-03-17 21:37:55 GMT Mon 2024-03-18 00:55:09 GMT
-14 b5c4fc8233c64cb98406b00a6ac127d0 Mon 2024-03-18 13:27:45 GMT Mon 2024-03-18 23:47:48 GMT
-13 c208cec196304b69bd1a0cd3163e9fae Tue 2024-03-19 13:49:01 GMT Tue 2024-03-19 14:13:59 GMT
-12 ed28087af3e14feba550640859f782e1 Tue 2024-03-19 14:14:39 GMT Wed 2024-03-20 01:56:33 GMT
-11 3161c7157bdb4b28a486967c757aac5c Wed 2024-03-20 13:10:38 GMT Wed 2024-03-20 14:51:04 GMT
-10 f894cdb5146b4eed9f7aa9ee0a706f2d Wed 2024-03-20 14:53:14 GMT Wed 2024-03-20 19:44:16 GMT
 -9 0dcd8e1b924a49c2be8dbad78dc4bf0a Wed 2024-03-20 19:45:35 GMT Thu 2024-03-21 01:07:02 GMT
 -8 c910bdced66e4466b5e3fd766484bcca Thu 2024-03-21 13:44:12 GMT Thu 2024-03-21 19:56:44 GMT
 -7 4a0b0e1bdc21408bbda9bfeda16d6dc4 Thu 2024-03-21 19:57:59 GMT Thu 2024-03-21 21:23:04 GMT
 -6 df1d040fab8743549defd058a307b971 Thu 2024-03-21 21:24:34 GMT Fri 2024-03-22 02:06:10 GMT
 -5 f95961c6f5d14d94a610cc6c2a38bb70 Fri 2024-03-22 12:48:36 GMT Sat 2024-03-23 00:27:56 GMT
 -4 8840c3c3588646f8a155d5ad60f2312d Sat 2024-03-23 11:25:42 GMT Sat 2024-03-23 21:57:41 GMT
 -3 3238c9a464fa48d3b39727cdda548e12 Sat 2024-03-23 21:59:34 GMT Sun 2024-03-24 02:47:38 GMT
 -2 aa213867dc21479f99e9b047d0529585 Sun 2024-03-24 11:49:00 GMT Sun 2024-03-24 23:44:14 GMT
 -1 66e894a3c47d4501b5073e1d3e8e83a0 Mon 2024-03-25 12:03:34 GMT Mon 2024-03-25 22:06:59 GMT
  0 84f1b769a87b43989fdbf240e5b05e91 Mon 2024-03-25 22:09:17 GMT Tue 2024-03-26 00:06:06 GMT
sh-5.2$
6

@rokejulianlockhart so can you not set the environment and run the steam binary?

Just ssh in from the device?

7

@malcolmlewis, can you elaborate? I’m somewhat new to debugging.

8

@rokejulianlockhart can you post the script?

I shows DEBUGGER=gdb steam and then run in that link?

9

I’m not sure what you mean. I debug literally just by invoking

DEBUGGER=gdb steam

in sh.

Somehow, that variable assignment automatically initializes the debugger:

PS /home/RokeJulianLockhart> sh
sh-5.2$ DEBUGGER=gdb steam
steam.sh[12033]: Running Steam on opensuse-tumbleweed 20240321 64-bit
steam.sh[12033]: STEAM_RUNTIME is enabled automatically
setup.sh[12149]: Steam runtime environment up-to-date!
steam.sh[12033]: Steam client's requirements are satisfied
gdb/cgdb launch with ARGSFILE: RokeJulianLockhart.steam.gdb.x8tg
gdb -x RokeJulianLockhart.steam.gdb.x8tg --args /home/RokeJulianLockhart/.local/share/Steam/ubuntu12_32/steam
GNU gdb (GDB; openSUSE Tumbleweed) 13.2
Copyright (C) 2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-suse-linux".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://bugs.opensuse.org/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /home/RokeJulianLockhart/.local/share/Steam/ubuntu12_32/steam...

This GDB supports auto-downloading debuginfo from the following URLs:
  <https://debuginfod.opensuse.org/>
Enable debuginfod for this session? (y or [n]) y
Debuginfod has been enabled.
To make this setting permanent, add 'set debuginfod enabled on' to .gdbinit.
Downloading separate debug info for /home/RokeJulianLockhart/.local/share/Steam/ubuntu12_32/steam
Missing separate debuginfo for /home/RokeJulianLockhart/.local/share/Steam/ubuntu12_32/steam                                                                                                                                                                                   
Try: zypper install -C "debuginfo(build-id)=c04eeb8e026e14386566b6fb5980d90612ca1c8d"
(No debugging symbols found in /home/RokeJulianLockhart/.local/share/Steam/ubuntu12_32/steam)
LD_LIBRARY_PATH = /home/RokeJulianLockhart/.local/share/Steam/ubuntu12_32:/home/RokeJulianLockhart/.local/share/Steam/ubuntu12_32/panorama:/home/RokeJulianLockhart/.local/share/Steam/ubuntu12_32/steam-runtime/pinned_libs_32:/home/RokeJulianLockhart/.local/share/Steam/ubuntu12_32/steam-runtime/pinned_libs_64:/usr/local/lib64:/usr/local/lib:/usr/lib64/pipewire-0.3/jack:/lib:/lib64:/lib64/glibc-hwcaps/x86-64-v2:/lib64/glibc-hwcaps/x86-64-v3:/lib64/glibc-hwcaps/x86-64-v4:/home/RokeJulianLockhart/.local/share/Steam/ubuntu12_32/steam-runtime/lib/i386-linux-gnu:/home/RokeJulianLockhart/.local/share/Steam/ubuntu12_32/steam-runtime/usr/lib/i386-linux-gnu:/home/RokeJulianLockhart/.local/share/Steam/ubuntu12_32/steam-runtime/lib/x86_64-linux-gnu:/home/RokeJulianLockhart/.local/share/Steam/ubuntu12_32/steam-runtime/usr/lib/x86_64-linux-gnu:/home/RokeJulianLockhart/.local/share/Steam/ubuntu12_32/steam-runtime/lib:/home/RokeJulianLockhart/.local/share/Steam/ubuntu12_32/steam-runtime/usr/lib
  Cache hits (this session): 0
Cache misses (this session): 0
(gdb) run

It doesn’t work in powershell, but it doesn’t assign variables that way, so I don’t know whether the variable assignment is what invokes it, or whether the shell matters.

10

@rokejulianlockhart use a normal terminal…

11

@malcolmlewis, I don’t know what you mean. I’m using https://download.opensuse.org/repositories/openSUSE:/Factory/standard/x86_64/konsole-24.02.1-1.1.x86_64.rpm.

12

@rokejulianlockhart you said it doesn’t work in the terminal (powershell) which I thought you were using, try strace instead of gdb… but if it’s crashing the kernel you need to remove the taint (virtualbox?).

13

Have a look at What is the difference between shell, console, and terminal? - Super User. A shell differs from a terminal. It’ll be useful knowledge for the future.

Not for this, because I don’t know how to get it working in that.

@malcolmlewis, are kernel modules a common cause for crashes — is that why you state that? Regardless, I don’t know whether the kernel is the culprit — that’s the problem at hand. I can’t find any useful logs anywhere.

14

@rokejulianlockhart it could be, but tainted kernel will likely not be accepted in a bug report…

1 Like
15

@malcolmlewis, I expect

sudo zypper remove 'virtualbox*' # https://forums.opensuse.org/t/how-to-remove-all-texlive-packages-from-command-line/136837/2

Reading installed packages...
Resolving package dependencies...

The following 6 packages are going to be REMOVED:
  virtualbox virtualbox-kmp-default-7.0.14_k6.7.6_1-3.2 virtualbox-kmp-default-7.0.14_k6.7.7_1-4.1 virtualbox-kmp-default-7.0.14_k6.7.9_1-5.1 virtualbox-kmp-default-7.0.14_k6.8.1_1-5.2 virtualbox-qt

6 packages to remove.
After the operation, 116.9 MiB will be freed.
Continue? [y/n/v/...? shows all options] (y): y

will be enough to remove it?

16

Yup and a reboot. Check the boot log after rebooting

1 Like
17

@malcolmlewis, whilst it’s hung? That’s a novel idea. I’ll try that next. Any idea how I could get a bt from another session, though? Remember, coredumptctl is strangely lacking any traces.

18

@rokejulianlockhart No, you log in remotely first then switch to root user and run journalctl -f then run the debugger…

1 Like
19

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.