Bug 491820 - Crash Report is unable to produce trace.
Summary: Crash Report is unable to produce trace.
Status: REPORTED
Alias: None
Product: drkonqi
Classification: Applications
Component: backtraceparsing (other bugs)
Version First Reported In: 6.1.4
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-08-17 11:43 UTC by Roke Julian Lockhart Beedell
Modified: 2024-08-27 11:37 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Demonstration screencast of hung submission on Radeon RX 5700 machine. (208.17 KB, video/webm)
2024-08-17 11:43 UTC, Roke Julian Lockhart Beedell
Details
Demonstration screenshot of hung submission on Radeon RX 5700 machine. (34.97 KB, image/png)
2024-08-17 11:44 UTC, Roke Julian Lockhart Beedell
Details
Demonstration screenshot of successful submission on Radeon RX 5700 machine. (34.58 KB, image/png)
2024-08-17 11:45 UTC, Roke Julian Lockhart Beedell
Details
Demonstration screenshot of hung submission on Radeon RX 7900 machine. (29.92 KB, image/png)
2024-08-17 11:45 UTC, Roke Julian Lockhart Beedell
Details
0B KCrash file from hung submission on Radeon RX 5700 machine. (166 bytes, application/zip)
2024-08-17 11:48 UTC, Roke Julian Lockhart Beedell
Details
Log of the actual crash that it should have reported from the Radeon RX 5700 machine. (9.71 KB, text/markdown)
2024-08-17 11:50 UTC, Roke Julian Lockhart Beedell
Details
CPV summary of the actual crash that it should have reported from the Radeon RX 5700 machine. (91.92 KB, text/markdown)
2024-08-17 11:57 UTC, Roke Julian Lockhart Beedell
Details
0B KCrash file from hung submission on Radeon RX 7900 machine. (158 bytes, application/zip)
2024-08-17 12:01 UTC, Roke Julian Lockhart Beedell
Details
Demonstration screencast of hung submission on Radeon RX 7900 machine. (49.67 KB, video/webm)
2024-08-17 12:02 UTC, Roke Julian Lockhart Beedell
Details
Demonstration screenshot of hung submission on Radeon RX 7900 machine. (33.85 KB, image/png)
2024-08-17 12:02 UTC, Roke Julian Lockhart Beedell
Details
journalctl log of relevant boot; all priorities. (350.30 KB, text/markdown)
2024-08-19 15:06 UTC, Roke Julian Lockhart Beedell
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Roke Julian Lockhart Beedell 2024-08-17 11:43:58 UTC
Created attachment 172692 [details]
Demonstration screencast of hung submission on Radeon RX 5700 machine.

SUMMARY
-------

The Crash Handler is unable to produce traces.

STEPS TO REPRODUCE
------------------

1. Crash PlasmShell or Dolphin (these are merely the sole times I've managed to have the Crash handler appear).
2. Either automatically report it, or attempt to manually do so.

OBSERVED RESULT
---------------

The user is unable to manually report it, and the automatic report remains indefinitely.

EXPECTED RESULT
---------------

It should generate traces.

SOFTWARE/OS VERSIONS
--------------------

1. > Operating System: Fedora Linux 40  
   > KDE Plasma Version: 6.1.4  
   > KDE Frameworks Version: 6.5.0  
   > Qt Version: 6.7.2  
   > Kernel Version: 6.10.5-200.fc40.x86_64 (64-bit)  
   > Graphics Platform: Wayland  
   > Processors: 12 × AMD Ryzen 5 7600X 6-Core Processor  
   > Memory: 30.5 GiB of RAM  
   > Graphics Processor: AMD Radeon RX 5700  
   > Manufacturer: ASRock  
   > Product Name: X670E Taichi  

2. > Operating System: Fedora Linux 40  
   > KDE Plasma Version: 6.1.4  
   > KDE Frameworks Version: 6.5.0  
   > Qt Version: 6.7.2  
   > Kernel Version: 6.10.3-200.fc40.x86_64 (64-bit)  
   > Graphics Platform: Wayland  
   > Processors: 12 × AMD Ryzen 5 7600X 6-Core Processor  
   > Memory: 30.5 GiB of RAM  
   > Graphics Processor: AMD Radeon RX 7900 XTX  
   > Product Name: X670E Taichi  

ADDITIONAL INFORMATION
----------------------

The debug package download dialogue doesn't change anything.
Comment 1 Roke Julian Lockhart Beedell 2024-08-17 11:44:39 UTC
Created attachment 172693 [details]
Demonstration screenshot of hung submission on Radeon RX 5700 machine.
Comment 2 Roke Julian Lockhart Beedell 2024-08-17 11:45:19 UTC
Created attachment 172694 [details]
Demonstration screenshot of successful submission on Radeon RX 5700 machine.

The sole ones which appear to succeed are those which appear every time I try to use Firefox's XDG File Picker portal implementation.
Comment 3 Roke Julian Lockhart Beedell 2024-08-17 11:45:48 UTC
Created attachment 172695 [details]
Demonstration screenshot of hung submission on Radeon RX 7900 machine.
Comment 4 Roke Julian Lockhart Beedell 2024-08-17 11:48:15 UTC
Created attachment 172696 [details]
0B KCrash file from hung submission on Radeon RX 5700 machine.
Comment 5 Roke Julian Lockhart Beedell 2024-08-17 11:50:35 UTC
Created attachment 172697 [details]
Log of the actual crash that it should have reported from the Radeon RX 5700 machine.
Comment 6 Roke Julian Lockhart Beedell 2024-08-17 11:52:32 UTC
(In reply to Roke Julian Lockhart Beedell from comment #5)
If that's worth reporting separately, I can. However, I've never manually reported stuff from the Crashed Processes Viewer before - it's difficult for me to ascertain whether a given trace is useful (especially because there are entries there for crashes in the background, which I can't provide the faintest idea of how to reproduce). If it integrated into GNOME-ABRT, I would.
Comment 7 Roke Julian Lockhart Beedell 2024-08-17 11:57:00 UTC
Created attachment 172698 [details]
CPV summary of the actual crash that it should have reported from the Radeon RX 5700 machine.

(In reply to Roke Julian Lockhart Beedell from comment #5)
I forgot to include the Crashed Process Viewer's summary, in addition to the previous `gdb` backtrace. I imagine they're both necessary.
Comment 8 Roke Julian Lockhart Beedell 2024-08-17 12:01:06 UTC
Created attachment 172700 [details]
0B KCrash file from hung submission on Radeon RX 7900 machine.
Comment 9 Roke Julian Lockhart Beedell 2024-08-17 12:02:05 UTC
Created attachment 172701 [details]
Demonstration screencast of hung submission on Radeon RX 7900 machine.
Comment 10 Roke Julian Lockhart Beedell 2024-08-17 12:02:42 UTC
Created attachment 172702 [details]
Demonstration screenshot of hung submission on Radeon RX 7900 machine.
Comment 11 Harald Sitter 2024-08-17 14:52:43 UTC
What does journalctl have to say?
Comment 12 Roke Julian Lockhart Beedell 2024-08-17 15:18:16 UTC
(In reply to Harald Sitter from comment #11)
Is there a keyword I should be looking for? I doubt you want my entire `journalctl` output - it's rather large.
Comment 13 Harald Sitter 2024-08-17 15:26:20 UTC
(In reply to Roke Julian Lockhart Beedell from comment #12)
> (In reply to Harald Sitter from comment #11)
> Is there a keyword I should be looking for? I doubt you want my entire
> `journalctl` output - it's rather large.

I don't know what I'm looking for until I see it :) 
It's best if you just find the relevant time frame when this happens and then extract that portion with something like this command `journalctl --since '1hr ago' --until 'now'`
Comment 14 Roke Julian Lockhart Beedell 2024-08-19 15:06:10 UTC
Created attachment 172753 [details]
journalctl log of relevant boot; all priorities.

(In reply to Harald Sitter from comment #13)

Apologies for the wait.

```sh
journalctl --list-boots | grep '2024-08-17 12'
```

returns

> ```log
> PS /home/RokeJulianLockhart> journalctl --list-boots | grep '2024-08-17 12'
>  -7 a031d3656fcd4e22826a236bf7e1a69e Sat 2024-08-17 12:24:42 BST Sat 2024-08-17 12:25:03 BST
>  -6 b13c509dc4a34919991149d611a98e92 Sat 2024-08-17 12:25:48 BST Sat 2024-08-17 19:00:16 BST
> ```

Consequently, I've attached the output of `journalctl -b 'a031d3656fcd4e22826a236bf7e1a69e' -p 7 --until '2024-08-17 12:43:00' -o short-iso-precise`.

However, I've provided a shorter summary (`-p 5`) beneath too, if of use. It does contain a single trace:

> ```log
> PS /home/RokeJulianLockhart> journalctl -b 'a031d3656fcd4e22826a236bf7e1a69e' -p 5 --until '2024-08-17 12:43:00' -o short-iso-precise
> 2024-08-17T12:24:42.280194+01:00 sayw4i kernel: Linux version 6.10.5-200.fc40.x86_64 (mockbuild@108d1f86bb354c66b23c12a955335bb7) (gcc (GCC) 14.2.1 20240801 (Red Hat 14.2.1-1), GNU ld version 2.41-37.fc40) #1 SMP PREEMPT_DYNAMIC Wed Aug 14 15:49:44 UTC 2024
> 2024-08-17T12:24:42.280381+01:00 sayw4i kernel: random: crng init done
> 2024-08-17T12:24:42.280860+01:00 sayw4i kernel: Kernel command line: BOOT_IMAGE=(hd1,gpt2)/vmlinuz-6.10.5-200.fc40.x86_64 root=UUID=7d940ad3-aa33-4284-b5eb-b902c9568f0b ro rootflags=subvol=root rhgb quiet
> 2024-08-17T12:24:42.280863+01:00 sayw4i kernel: Unknown kernel command line parameters "rhgb BOOT_IMAGE=(hd1,gpt2)/vmlinuz-6.10.5-200.fc40.x86_64", will be passed to user space.
> 2024-08-17T12:24:42.281018+01:00 sayw4i kernel: Speculative Return Stack Overflow: IBPB-extending microcode not applied!
> 2024-08-17T12:24:42.281022+01:00 sayw4i kernel: Speculative Return Stack Overflow: WARNING: See https://kernel.org/doc/html/latest/admin-guide/hw-vuln/srso.html for mitigation options.
> 2024-08-17T12:24:42.281198+01:00 sayw4i kernel: audit: type=2000 audit(1723893878.146:1): state=initialized audit_enabled=0 res=1
> 2024-08-17T12:24:42.281265+01:00 sayw4i kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPC0.EC0], AE_NOT_FOUND (20240322/dswload2-162)
> 2024-08-17T12:24:42.281268+01:00 sayw4i kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20240322/psobject-220)
> 2024-08-17T12:24:42.281275+01:00 sayw4i kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.GPP0._PRW], AE_ALREADY_EXISTS (20240322/dswload2-326)
> 2024-08-17T12:24:42.281278+01:00 sayw4i kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240322/psobject-220)
> 2024-08-17T12:24:42.281281+01:00 sayw4i kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.GPP2._PRW], AE_ALREADY_EXISTS (20240322/dswload2-326)
> 2024-08-17T12:24:42.281284+01:00 sayw4i kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240322/psobject-220)
> 2024-08-17T12:24:42.281288+01:00 sayw4i kernel: ACPI BIOS Error (bug): Failure creating named object [\_GPE._L08], AE_ALREADY_EXISTS (20240322/dswload2-326)
> 2024-08-17T12:24:42.281295+01:00 sayw4i kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240322/psobject-220)
> 2024-08-17T12:24:42.281305+01:00 sayw4i kernel: ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
> 2024-08-17T12:24:42.302730+01:00 sayw4i kernel: SCSI subsystem initialized
> 2024-08-17T12:24:42.304900+01:00 sayw4i kernel: VFS: Disk quotas dquot_6.6.0
> 2024-08-17T12:24:42.318871+01:00 sayw4i kernel: Initialise system trusted keyrings
> 2024-08-17T12:24:42.318874+01:00 sayw4i kernel: Key type blacklist registered
> 2024-08-17T12:24:42.318884+01:00 sayw4i kernel: integrity: Platform Keyring initialized
> 2024-08-17T12:24:42.318887+01:00 sayw4i kernel: integrity: Machine keyring initialized
> 2024-08-17T12:24:42.318896+01:00 sayw4i kernel: Key type asymmetric registered
> 2024-08-17T12:24:42.318899+01:00 sayw4i kernel: Asymmetric key parser 'x509' registered
> 2024-08-17T12:24:42.330308+01:00 sayw4i kernel: hub 12-0:1.0: config failed, hub doesn't have any ports! (err -19)
> 2024-08-17T12:24:42.330543+01:00 sayw4i kernel: device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log.
> 2024-08-17T12:24:42.330703+01:00 sayw4i kernel: Loading compiled-in X.509 certificates
> 2024-08-17T12:24:42.330707+01:00 sayw4i kernel: Loaded X.509 cert 'Fedora kernel signing key: 3d632b4a2994979c9e93863ee717c26d8c1b4fc5'
> 2024-08-17T12:24:42.330710+01:00 sayw4i kernel: Loaded X.509 cert 'Fedora IMA CA: a8a00c31663f853f9c6ff2564872e378af026b28'
> 2024-08-17T12:24:42.330719+01:00 sayw4i kernel: Key type .fscrypt registered
> 2024-08-17T12:24:42.330722+01:00 sayw4i kernel: Key type fscrypt-provisioning registered
> 2024-08-17T12:24:42.330728+01:00 sayw4i kernel: Key type big_key registered
> 2024-08-17T12:24:42.330731+01:00 sayw4i kernel: Key type trusted registered
> 2024-08-17T12:24:42.330734+01:00 sayw4i kernel: Key type encrypted registered
> 2024-08-17T12:24:42.330737+01:00 sayw4i kernel: Loading compiled-in module X.509 certificates
> 2024-08-17T12:24:42.330741+01:00 sayw4i kernel: Loaded X.509 cert 'Fedora kernel signing key: 3d632b4a2994979c9e93863ee717c26d8c1b4fc5'
> 2024-08-17T12:24:42.276567+01:00 sayw4i systemd-vconsole-setup[386]: /usr/bin/setfont failed with a "system error" (EX_OSERR), ignoring.
> 2024-08-17T12:24:42.296770+01:00 sayw4i systemd-vconsole-setup[386]: Setting source virtual console failed, ignoring remaining ones.
> 2024-08-17T12:24:42.346023+01:00 sayw4i systemd-tmpfiles[476]: /usr/lib/tmpfiles.d/var.conf:14: Duplicate line for path "/var/log", ignoring.
> 2024-08-17T12:24:42.525975+01:00 sayw4i kernel: ccp 0000:59:00.2: psp: unable to access the device: you might be running a broken BIOS.
> 2024-08-17T12:24:42.548087+01:00 sayw4i kernel: nvme nvme0: missing or invalid SUBNQN field.
> 2024-08-17T12:24:42.555353+01:00 sayw4i systemd-vconsole-setup[596]: /usr/bin/setfont failed with a "system error" (EX_OSERR), ignoring.
> 2024-08-17T12:24:42.575708+01:00 sayw4i systemd-vconsole-setup[596]: Setting source virtual console failed, ignoring remaining ones.
> 2024-08-17T12:24:42.681963+01:00 sayw4i kernel: nvme nvme2: missing or invalid SUBNQN field.
> 2024-08-17T12:24:42.682062+01:00 sayw4i kernel: nvme nvme3: missing or invalid SUBNQN field.
> 2024-08-17T12:24:43.968999+01:00 sayw4i kernel: amdgpu: ATPX version 1, functions 0x00000000
> 2024-08-17T12:24:44.635971+01:00 sayw4i kernel: usbhid 5-9.2:1.2: couldn't find an input interrupt endpoint
> 2024-08-17T12:24:44.978264+01:00 sayw4i kernel: [drm] Fence fallback timer expired on ring sdma0
> 2024-08-17T12:24:45.482225+01:00 sayw4i kernel: [drm] Fence fallback timer expired on ring sdma0
> 2024-08-17T12:24:45.798280+01:00 sayw4i kernel: ------------[ cut here ]------------
> 2024-08-17T12:24:45.798299+01:00 sayw4i kernel: WARNING: CPU: 7 PID: 545 at drivers/gpu/drm/amd/amdgpu/../display/dc/link/protocols/link_dp_capability.c:1532 dp_retrieve_lttpr_cap+0x121/0x1e0 [amdgpu]
> 2024-08-17T12:24:45.798310+01:00 sayw4i kernel: Modules linked in: amdgpu(+) hid_logitech_hidpp amdxcp i2c_algo_bit drm_ttm_helper ttm crct10dif_pclmul crc32_pclmul drm_exec crc32c_intel polyval_clmulni gpu_sched polyval_generic ghash_clmulni_intel drm_suballoc_helper n>
> 2024-08-17T12:24:45.798318+01:00 sayw4i kernel: CPU: 7 PID: 545 Comm: (udev-worker) Not tainted 6.10.5-200.fc40.x86_64 #1
> 2024-08-17T12:24:45.798325+01:00 sayw4i kernel: Hardware name: ASRock X670E Taichi/X670E Taichi, BIOS 1.21 04/26/2023
> 2024-08-17T12:24:45.798331+01:00 sayw4i kernel: RIP: 0010:dp_retrieve_lttpr_cap+0x121/0x1e0 [amdgpu]
> 2024-08-17T12:24:45.798337+01:00 sayw4i 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 7a eb 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
> 2024-08-17T12:24:45.798344+01:00 sayw4i kernel: RSP: 0018:ffffb99400d57460 EFLAGS: 00010246
> 2024-08-17T12:24:45.798352+01:00 sayw4i kernel: RAX: ffff93520b0a4c00 RBX: 00000000ffffffff RCX: 00ffffffffffffff
> 2024-08-17T12:24:45.798358+01:00 sayw4i kernel: RDX: 0000000000000007 RSI: ffffb99400d57460 RDI: 0000000000000000
> 2024-08-17T12:24:45.798364+01:00 sayw4i kernel: RBP: ffff93520bf41000 R08: ffff935210d454c0 R09: 0000000000000000
> 2024-08-17T12:24:45.798370+01:00 sayw4i kernel: R10: 000000000000000a R11: 0000000000000001 R12: 0000000000000001
> 2024-08-17T12:24:45.798377+01:00 sayw4i kernel: R13: ffff93520bf41000 R14: 0000000000000020 R15: 0000000000000000
> 2024-08-17T12:24:45.798382+01:00 sayw4i kernel: FS:  00007fc6d815d980(0000) GS:ffff935938780000(0000) knlGS:0000000000000000
> 2024-08-17T12:24:45.798388+01:00 sayw4i kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> 2024-08-17T12:24:45.798395+01:00 sayw4i kernel: CR2: 00007fc3cadd4f60 CR3: 000000010fb5e000 CR4: 0000000000f50ef0
> 2024-08-17T12:24:45.798401+01:00 sayw4i kernel: PKRU: 55555554
> 2024-08-17T12:24:45.798406+01:00 sayw4i kernel: Call Trace:
> 2024-08-17T12:24:45.798413+01:00 sayw4i kernel:  <TASK>
> 2024-08-17T12:24:45.798420+01:00 sayw4i kernel:  ? dp_retrieve_lttpr_cap+0x121/0x1e0 [amdgpu]
> 2024-08-17T12:24:45.798426+01:00 sayw4i kernel:  ? __warn.cold+0x8e/0xe8
> 2024-08-17T12:24:45.798432+01:00 sayw4i kernel:  ? dp_retrieve_lttpr_cap+0x121/0x1e0 [amdgpu]
> 2024-08-17T12:24:45.798438+01:00 sayw4i kernel:  ? report_bug+0xff/0x140
> 2024-08-17T12:24:45.798444+01:00 sayw4i kernel:  ? handle_bug+0x3c/0x80
> 2024-08-17T12:24:45.798450+01:00 sayw4i kernel:  ? exc_invalid_op+0x17/0x70
> 2024-08-17T12:24:45.798456+01:00 sayw4i kernel:  ? asm_exc_invalid_op+0x1a/0x20
> 2024-08-17T12:24:45.798462+01:00 sayw4i kernel:  ? dp_retrieve_lttpr_cap+0x121/0x1e0 [amdgpu]
> 2024-08-17T12:24:45.798468+01:00 sayw4i kernel:  retrieve_link_cap+0x79/0xd90 [amdgpu]
> 2024-08-17T12:24:45.798474+01:00 sayw4i kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
> 2024-08-17T12:24:45.798988+01:00 sayw4i kernel:  detect_link_and_local_sink+0xc3e/0x1210 [amdgpu]
> 2024-08-17T12:24:45.799007+01:00 sayw4i kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
> 2024-08-17T12:24:45.799015+01:00 sayw4i kernel:  link_detect+0x37/0x540 [amdgpu]
> 2024-08-17T12:24:45.799024+01:00 sayw4i kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
> 2024-08-17T12:24:45.799029+01:00 sayw4i kernel:  ? dal_gpio_destroy_irq+0x25/0x40 [amdgpu]
> 2024-08-17T12:24:45.799034+01:00 sayw4i kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
> 2024-08-17T12:24:45.800051+01:00 sayw4i kernel:  ? query_hpd_status+0x6e/0xa0 [amdgpu]
> 2024-08-17T12:24:45.800066+01:00 sayw4i kernel:  amdgpu_dm_init.isra.0+0x11a1/0x22d0 [amdgpu]
> 2024-08-17T12:24:45.800072+01:00 sayw4i kernel:  ? __pfx_enable_assr+0x10/0x10 [amdgpu]
> 2024-08-17T12:24:45.800078+01:00 sayw4i kernel:  ? __pfx_update_config+0x10/0x10 [amdgpu]
> 2024-08-17T12:24:45.800082+01:00 sayw4i kernel:  dm_hw_init+0x12/0x30 [amdgpu]
> 2024-08-17T12:24:45.800087+01:00 sayw4i kernel:  amdgpu_device_init.cold+0x1c69/0x1fb6 [amdgpu]
> 2024-08-17T12:24:45.800966+01:00 sayw4i kernel:  amdgpu_driver_load_kms+0x19/0x70 [amdgpu]
> 2024-08-17T12:24:45.800980+01:00 sayw4i kernel:  amdgpu_pci_probe+0x1a7/0x4b0 [amdgpu]
> 2024-08-17T12:24:45.800987+01:00 sayw4i kernel:  local_pci_probe+0x42/0x90
> 2024-08-17T12:24:45.800995+01:00 sayw4i kernel:  pci_device_probe+0xc1/0x2a0
> 2024-08-17T12:24:45.801000+01:00 sayw4i kernel:  really_probe+0xdb/0x340
> 2024-08-17T12:24:45.801005+01:00 sayw4i kernel:  ? pm_runtime_barrier+0x54/0x90
> 2024-08-17T12:24:45.801009+01:00 sayw4i kernel:  ? __pfx___driver_attach+0x10/0x10
> 2024-08-17T12:24:45.801014+01:00 sayw4i kernel:  __driver_probe_device+0x78/0x110
> 2024-08-17T12:24:45.801019+01:00 sayw4i kernel:  driver_probe_device+0x1f/0xa0
> 2024-08-17T12:24:45.801024+01:00 sayw4i kernel:  __driver_attach+0xba/0x1c0
> 2024-08-17T12:24:45.801029+01:00 sayw4i kernel:  bus_for_each_dev+0x8c/0xe0
> 2024-08-17T12:24:45.801033+01:00 sayw4i kernel:  bus_add_driver+0x142/0x220
> 2024-08-17T12:24:45.801038+01:00 sayw4i kernel:  driver_register+0x72/0xd0
> 2024-08-17T12:24:45.801043+01:00 sayw4i kernel:  ? __pfx_amdgpu_init+0x10/0x10 [amdgpu]
> 2024-08-17T12:24:45.801048+01:00 sayw4i kernel:  do_one_initcall+0x58/0x310
> 2024-08-17T12:24:45.801052+01:00 sayw4i kernel:  do_init_module+0x90/0x250
> 2024-08-17T12:24:45.801059+01:00 sayw4i kernel:  __do_sys_init_module+0x17a/0x1b0
> 2024-08-17T12:24:45.801063+01:00 sayw4i kernel:  do_syscall_64+0x82/0x160
> 2024-08-17T12:24:45.801068+01:00 sayw4i kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
> 2024-08-17T12:24:45.801073+01:00 sayw4i kernel:  ? vfs_read+0x296/0x370
> 2024-08-17T12:24:45.801078+01:00 sayw4i kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
> 2024-08-17T12:24:45.801082+01:00 sayw4i kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
> 2024-08-17T12:24:45.801087+01:00 sayw4i kernel:  ? syscall_exit_to_user_mode+0x72/0x220
> 2024-08-17T12:24:45.801092+01:00 sayw4i kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
> 2024-08-17T12:24:45.801096+01:00 sayw4i kernel:  ? do_syscall_64+0x8e/0x160
> 2024-08-17T12:24:45.801103+01:00 sayw4i kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
> 2024-08-17T12:24:45.801107+01:00 sayw4i kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
> 2024-08-17T12:24:45.801112+01:00 sayw4i kernel:  ? __count_memcg_events+0x75/0x130
> 2024-08-17T12:24:45.801116+01:00 sayw4i kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
> 2024-08-17T12:24:45.801121+01:00 sayw4i kernel:  ? count_memcg_events.constprop.0+0x1a/0x30
> 2024-08-17T12:24:45.801127+01:00 sayw4i kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
> 2024-08-17T12:24:45.801132+01:00 sayw4i kernel:  ? handle_mm_fault+0x1f0/0x300
> 2024-08-17T12:24:45.801136+01:00 sayw4i kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
> 2024-08-17T12:24:45.801141+01:00 sayw4i kernel:  ? do_user_addr_fault+0x36c/0x620
> 2024-08-17T12:24:45.801146+01:00 sayw4i kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
> 2024-08-17T12:24:45.801150+01:00 sayw4i kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
> 2024-08-17T12:24:45.801155+01:00 sayw4i kernel:  entry_SYSCALL_64_after_hwframe+0x76/0x7e
> 2024-08-17T12:24:45.801160+01:00 sayw4i kernel: RIP: 0033:0x7fc6d8b3d80e
> 2024-08-17T12:24:45.801165+01:00 sayw4i kernel: Code: 48 8b 0d 0d a6 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d da a5 0c 00 f7 d8 64 89 01 48
> 2024-08-17T12:24:45.801170+01:00 sayw4i kernel: RSP: 002b:00007ffd9983f128 EFLAGS: 00000246 ORIG_RAX: 00000000000000af
> 2024-08-17T12:24:45.801175+01:00 sayw4i kernel: RAX: ffffffffffffffda RBX: 000056450a6288a0 RCX: 00007fc6d8b3d80e
> 2024-08-17T12:24:45.801180+01:00 sayw4i kernel: RDX: 00007fc6d8c5707d RSI: 00000000024ec21e RDI: 00007fc6d2e00010
> 2024-08-17T12:24:45.801184+01:00 sayw4i kernel: RBP: 00007ffd9983f1e0 R08: 000056450a5b0010 R09: 0000000000000007
> 2024-08-17T12:24:45.801191+01:00 sayw4i kernel: R10: 0000000000000006 R11: 0000000000000246 R12: 00007fc6d8c5707d
> 2024-08-17T12:24:45.801196+01:00 sayw4i kernel: R13: 0000000000020000 R14: 000056450a625c70 R15: 000056450a66bb40
> 2024-08-17T12:24:45.801200+01:00 sayw4i kernel:  </TASK>
> 2024-08-17T12:24:45.801205+01:00 sayw4i kernel: ---[ end trace 0000000000000000 ]---
> 2024-08-17T12:24:46.126294+01:00 sayw4i systemd[1]: Switching root.
> 2024-08-17T12:24:46.766578+01:00 sayw4i kernel: audit: type=1404 audit(1723893886.219:2): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295 enabled=1 old-enabled=1 lsm=selinux res=1
> 2024-08-17T12:24:46.766652+01:00 sayw4i kernel: audit: type=1403 audit(1723893886.295:3): auid=4294967295 ses=4294967295 lsm=selinux res=1
> 2024-08-17T12:24:46.767969+01:00 sayw4i kernel: audit: type=1130 audit(1723893886.766:4): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-journald comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? re>
> 2024-08-17T12:24:47.166272+01:00 sayw4i kernel: audit: type=1130 audit(1723893886.796:5): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-random-seed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=?>
> 2024-08-17T12:24:47.166297+01:00 sayw4i kernel: audit: type=1130 audit(1723893886.796:6): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-sysctl comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=>
> 2024-08-17T12:24:47.166312+01:00 sayw4i kernel: audit: type=1130 audit(1723893886.803:7): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=lvm2-monitor comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=su>
> 2024-08-17T12:24:47.166326+01:00 sayw4i kernel: audit: type=1130 audit(1723893886.809:8): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-tmpfiles-setup-dev-early comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr>
> 2024-08-17T12:24:47.166379+01:00 sayw4i kernel: audit: type=1130 audit(1723893886.845:9): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-tmpfiles-setup-dev comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? ter>
> 2024-08-17T12:24:47.166394+01:00 sayw4i kernel: audit: type=1334 audit(1723893886.845:10): prog-id=36 op=LOAD
> 2024-08-17T12:24:47.166408+01:00 sayw4i kernel: audit: type=1334 audit(1723893886.845:11): prog-id=37 op=LOAD
> 2024-08-17T12:24:47.171192+01:00 sayw4i kernel: cfg80211: Loading compiled-in X.509 certificates for regulatory database
> 2024-08-17T12:24:47.171208+01:00 sayw4i kernel: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
> 2024-08-17T12:24:47.171222+01:00 sayw4i kernel: Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
> 2024-08-17T12:24:47.211007+01:00 sayw4i kernel: Bluetooth: hci0: No support for _PRR ACPI method
> 2024-08-17T12:24:47.317054+01:00 sayw4i systemd-vconsole-setup[922]: KD_FONT_OP_GET failed while trying to get the font metadata: Invalid argument
> 2024-08-17T12:24:47.317060+01:00 sayw4i systemd-vconsole-setup[922]: Fonts will not be copied to remaining consoles
> 2024-08-17T12:24:47.382961+01:00 sayw4i kernel: iwlwifi 0000:49:00.0: WRT: Invalid buffer destination
> 2024-08-17T12:24:47.594971+01:00 sayw4i kernel: usb 3-3: current rate 16000 is different from the runtime rate 24000
> 2024-08-17T12:24:47.616970+01:00 sayw4i kernel: usb 3-3: current rate 16000 is different from the runtime rate 32000
> 2024-08-17T12:24:47.638968+01:00 sayw4i kernel: usb 3-3: current rate 16000 is different from the runtime rate 48000
> 2024-08-17T12:24:47.655247+01:00 sayw4i wireless[994]: setting regulatory domain to GB based on timezone (Europe/London)
> 2024-08-17T12:24:47.967100+01:00 sayw4i boltd[1012]: bolt 0.9.8 starting up.
> 2024-08-17T12:24:48.006622+01:00 sayw4i bluetoothd[1011]: src/plugin.c:init_plugin() System does not support bap plugin
> 2024-08-17T12:24:48.006628+01:00 sayw4i bluetoothd[1011]: src/plugin.c:init_plugin() System does not support bass plugin
> 2024-08-17T12:24:48.006630+01:00 sayw4i bluetoothd[1011]: src/plugin.c:init_plugin() System does not support mcp plugin
> 2024-08-17T12:24:48.006633+01:00 sayw4i bluetoothd[1011]: src/plugin.c:init_plugin() System does not support vcp plugin
> 2024-08-17T12:24:48.006635+01:00 sayw4i bluetoothd[1011]: profiles/audio/micp.c:micp_init() D-Bus experimental not enabled
> 2024-08-17T12:24:48.006638+01:00 sayw4i bluetoothd[1011]: src/plugin.c:init_plugin() System does not support micp plugin
> 2024-08-17T12:24:48.006640+01:00 sayw4i bluetoothd[1011]: src/plugin.c:init_plugin() System does not support ccp plugin
> 2024-08-17T12:24:48.006643+01:00 sayw4i bluetoothd[1011]: src/plugin.c:init_plugin() System does not support csip plugin
> 2024-08-17T12:24:48.006645+01:00 sayw4i bluetoothd[1011]: src/plugin.c:init_plugin() System does not support asha plugin
> 2024-08-17T12:24:48.052073+01:00 sayw4i polkitd[1039]: Loading rules from directory /etc/polkit-1/rules.d
> 2024-08-17T12:24:48.052105+01:00 sayw4i polkitd[1039]: Loading rules from directory /usr/share/polkit-1/rules.d
> 2024-08-17T12:24:48.053794+01:00 sayw4i polkitd[1039]: Finished loading, compiling and executing 14 rules
> 2024-08-17T12:24:48.054002+01:00 sayw4i polkitd[1039]: Acquired the name org.freedesktop.PolicyKit1 on the system bus
> 2024-08-17T12:24:48.055040+01:00 sayw4i boltd[1012]: power: force power support: yes
> 2024-08-17T12:24:48.056647+01:00 sayw4i boltd[1012]: [2c4c8780-0073-domain0                    ] newly connected [none] (/sys/devices/pci0000:00/0000:00:01.2/0000:04:00.0/0000:05:00.0/0000:06:00.0/domain0/0-0)
> 2024-08-17T12:24:48.056729+01:00 sayw4i boltd[1012]: [2c4c8780-0073-domain0                    ] udev: failed to determine if uid is stable: unknown NHI PCI id '0x1137'
> 2024-08-17T12:24:48.056926+01:00 sayw4i boltd[1012]: [2c4c8780-0073-Intel Thunderbolt generic m] device added, status: authorized, at /sys/devices/pci0000:00/0000:00:01.2/0000:04:00.0/0000:05:00.0/0000:06:00.0/domain0/0-0
> 2024-08-17T12:24:48.093889+01:00 sayw4i bluetoothd[1011]: Failed to load LTKs for hci0: Invalid Parameters (0x0d)
> 2024-08-17T12:24:48.093905+01:00 sayw4i bluetoothd[1011]: Failed to load IRKs for hci0: Invalid Parameters (0x0d)
> 2024-08-17T12:24:48.344969+01:00 sayw4i kernel: iwlwifi 0000:49:00.0: WRT: Invalid buffer destination
> 2024-08-17T12:24:48.639973+01:00 sayw4i kernel: iwlwifi 0000:49:00.0: WRT: Invalid buffer destination
> 2024-08-17T12:24:48.921514+01:00 sayw4i wpa_supplicant[1125]: Successfully initialized wpa_supplicant
> 2024-08-17T12:24:52.511964+01:00 sayw4i kernel: usb 5-9.2: Warning! Unlikely big volume range (=3996), cval->res is probably wrong.
> 2024-08-17T12:24:52.512203+01:00 sayw4i kernel: usb 5-9.2: [5] FU [Mic Capture Volume] ch = 1, val = 0/3996/1
> 2024-08-17T12:24:52.595022+01:00 sayw4i wpa_supplicant[1125]: wlp73s0: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=GB
> 2024-08-17T12:24:52.595268+01:00 sayw4i wpa_supplicant[1125]: p2p-dev-wlp73s0: Channel list changed: 6 GHz was enabled
> 2024-08-17T12:24:52.595481+01:00 sayw4i wpa_supplicant[1125]: wlp73s0: Channel list changed: 6 GHz was enabled
> 2024-08-17T12:24:52.595506+01:00 sayw4i wpa_supplicant[1125]: wlp73s0: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=GB
> 2024-08-17T12:24:52.665958+01:00 sayw4i kernel: kauditd_printk_skb: 63 callbacks suppressed
> 2024-08-17T12:24:52.665975+01:00 sayw4i kernel: audit: type=1131 audit(1723893892.664:75): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res>
> 2024-08-17T12:24:52.768975+01:00 sayw4i kernel: audit: type=1130 audit(1723893892.767:76): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-wait-online comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? te>
> 2024-08-17T12:24:52.768976+01:00 sayw4i systemd[1]: iscsi.service: Unit cannot be reloaded because it is inactive.
> 2024-08-17T12:24:52.781108+01:00 sayw4i systemd[1]: iscsi.service: Unit cannot be reloaded because it is inactive.
> 2024-08-17T12:25:01.461957+01:00 sayw4i kernel: audit: type=1130 audit(1723893901.460:77): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=run-r98e9d7376cac4da68ec362ad7e8f2aad comm="systemd" exe="/usr/lib/systemd/systemd" hostname=>
> 2024-08-17T12:25:01.664957+01:00 sayw4i kernel: audit: type=1334 audit(1723893901.663:78): prog-id=47 op=LOAD
> 2024-08-17T12:25:01.664972+01:00 sayw4i kernel: audit: type=1334 audit(1723893901.663:79): prog-id=39 op=UNLOAD
> 2024-08-17T12:25:01.666956+01:00 sayw4i kernel: audit: type=1334 audit(1723893901.665:80): prog-id=48 op=LOAD
> 2024-08-17T12:25:01.666964+01:00 sayw4i kernel: audit: type=1334 audit(1723893901.665:81): prog-id=44 op=UNLOAD
> 2024-08-17T12:25:01.666978+01:00 sayw4i kernel: audit: type=1334 audit(1723893901.665:82): prog-id=49 op=LOAD
> 2024-08-17T12:25:01.666988+01:00 sayw4i kernel: audit: type=1334 audit(1723893901.665:83): prog-id=50 op=LOAD
> 2024-08-17T12:25:01.666998+01:00 sayw4i kernel: audit: type=1334 audit(1723893901.665:84): prog-id=45 op=UNLOAD
> 2024-08-17T12:25:01.667004+01:00 sayw4i kernel: audit: type=1334 audit(1723893901.665:85): prog-id=46 op=UNLOAD
> 2024-08-17T12:25:01.667013+01:00 sayw4i kernel: audit: type=1334 audit(1723893901.665:86): prog-id=51 op=LOAD
> 2024-08-17T12:25:02.525004+01:00 sayw4i systemctl[1630]: Job for man-db-cache-update.service canceled.
> 2024-08-17T12:25:02.525004+01:00 sayw4i systemctl[1568]: Job for man-db-cache-update.service canceled.
> 2024-08-17T12:25:02.527686+01:00 sayw4i systemd[1]: run-r98e9d7376cac4da68ec362ad7e8f2aad.service: Main process exited, code=exited, status=1/FAILURE
> 2024-08-17T12:25:02.527771+01:00 sayw4i systemd[1]: run-r98e9d7376cac4da68ec362ad7e8f2aad.service: Failed with result 'exit-code'.
> 2024-08-17T12:25:02.528085+01:00 sayw4i systemd[1]: run-r4b9204a245054fcca7eab88f3fa3fd77.service: Main process exited, code=exited, status=1/FAILURE
> 2024-08-17T12:25:02.528166+01:00 sayw4i systemd[1]: run-r4b9204a245054fcca7eab88f3fa3fd77.service: Failed with result 'exit-code'.
> 2024-08-17T12:25:02.532070+01:00 sayw4i nm-dispatcher[1074]: Caught signal 15, shutting down...
> 2024-08-17T12:25:02.549155+01:00 sayw4i systemd[1]: man-db-cache-update.service: Main process exited, code=killed, status=15/TERM
> 2024-08-17T12:25:02.556262+01:00 sayw4i wpa_supplicant[1125]: p2p-dev-wlp73s0: CTRL-EVENT-DSCP-POLICY clear_all
> 2024-08-17T12:25:02.556320+01:00 sayw4i wpa_supplicant[1125]: p2p-dev-wlp73s0: CTRL-EVENT-DSCP-POLICY clear_all
> 2024-08-17T12:25:02.556326+01:00 sayw4i wpa_supplicant[1125]: nl80211: deinit ifname=p2p-dev-wlp73s0 disabled_11b_rates=0
> 2024-08-17T12:25:02.583959+01:00 sayw4i kernel: iwlwifi 0000:49:00.0: WRT: Invalid buffer destination
> 2024-08-17T12:25:02.752860+01:00 sayw4i systemd[1]: man-db-cache-update.service: Failed with result 'signal'.
> 2024-08-17T12:25:02.758000+01:00 sayw4i dbus-broker-launch[1015]: Activation request for 'org.freedesktop.nm_dispatcher' failed.
> 2024-08-17T12:25:02.842085+01:00 sayw4i wpa_supplicant[1125]: p2p-dev-wlp73s0: CTRL-EVENT-TERMINATING
> 2024-08-17T12:25:02.842335+01:00 sayw4i wpa_supplicant[1125]: wlp73s0: CTRL-EVENT-DSCP-POLICY clear_all
> 2024-08-17T12:25:02.845056+01:00 sayw4i dbus-broker-launch[1015]: Activation request for 'org.freedesktop.nm_dispatcher' failed.
> 2024-08-17T12:25:02.864175+01:00 sayw4i wpa_supplicant[1125]: wlp73s0: CTRL-EVENT-DSCP-POLICY clear_all
> 2024-08-17T12:25:02.864180+01:00 sayw4i wpa_supplicant[1125]: nl80211: deinit ifname=wlp73s0 disabled_11b_rates=0
> 2024-08-17T12:25:02.864239+01:00 sayw4i wpa_supplicant[1125]: wlp73s0: CTRL-EVENT-TERMINATING
> 2024-08-17T12:25:02.984861+01:00 sayw4i systemd[1]: Shutting down.
> 2024-08-17T12:25:03.161967+01:00 sayw4i kernel: watchdog: watchdog0: watchdog did not stop!
> ```
Comment 15 Harald Sitter 2024-08-19 15:52:52 UTC
Your system appears to have logging aggressively disabled so it doesn't show any useful output unfortunately.

Maybe https://invent.kde.org/plasma/drkonqi/-/merge_requests/261 will help shed some light on what's going on.
Comment 16 Roke Julian Lockhart Beedell 2024-08-19 19:38:47 UTC
(In reply to Harald Sitter from comment #15)

Apologies, although I expect that to be a fault of Fedora's default installation preferences, because I can't imagine that I've accidentally modified that. It did appear to be a rather small amount of logs for an entire boot, in comparison to what I used to see on openSUSE Tumbleweed.

You don't happen to know of an upstream RedHat bug about that? If not, I'll create one, but I'm totally sure what I should be seeing, so it'll be a little difficult to describe.

Irrespective, thanks for the MR. I can't say I completely understand its description, though, being the novice developer I am.
Comment 17 Harald Sitter 2024-08-27 11:37:43 UTC
Git commit 34cc1171c26d72dc423cbe0f10d03ac541b3d1e6 by Harald Sitter.
Committed on 27/08/2024 at 11:24.
Pushed by sitter into branch 'master'.

backtracegenerator: cache raw debugger output and give the user access to it

this now means we capture both stdout and stderr. shouldn't be a huge
problem because we ultimately run the output through the gdb parser
anyway and that filters out most of the noise. plus, we mostly care
about the traces in sentry anyway and those are generated by the
preamble and clean.

there are two ways to get the data
- the inlinemessage now sports a details link that opens a txt file
- via the developer view, which no longer shows a useless error

there area also now verbosity lines to mark the beginning and the end of
the debugging session
Related: bug 477586, bug 474116, bug 478110

M  +53   -2    src/backtracegenerator.cpp
M  +7    -0    src/backtracegenerator.h
M  +2    -3    src/qml/DeveloperPage.qml
M  +16   -1    src/qml/main.qml

https://invent.kde.org/plasma/drkonqi/-/commit/34cc1171c26d72dc423cbe0f10d03ac541b3d1e6