To repro: 1. set karg "debugfs=off" on the latest Fedora 39 2. reboot 3. Observe that NetworkManager fails to start (times out) Reproducible: Always Steps to Reproduce: 1. set karg "debugfs=off" on the latest Fedora 39 2. reboot 3. Observe that NetworkManager fails to start (times out) Actual Results: NetworkManager fails to start (times out) Expected Results: NetworkManager starts fine
I can't reproduce the problem, please set the logging level to trace in /etc/NetworkManager/NetworkManager.conf, add kernel command line "rd.debug", reproduce the problem and attach the output of `journalctl -b`.
*** Bug 2263770 has been marked as a duplicate of this bug. ***
Attached the full log. The relevant portion appears to be this: ``` Feb 12 08:09:00 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=usbguard comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed' Feb 12 08:09:00 fedora audit: BPF prog-id=61 op=UNLOAD Feb 12 08:09:00 fedora kernel: iwlwifi 0000:00:14.3: Registered PHC clock: iwlwifi-PTP, with index: 0 Feb 12 08:09:00 fedora kernel: BUG: kernel NULL pointer dereference, address: 0000000000000027 Feb 12 08:09:00 fedora kernel: #PF: supervisor read access in kernel mode Feb 12 08:09:00 fedora kernel: #PF: error_code(0x0000) - not-present page Feb 12 08:09:00 fedora kernel: PGD 0 P4D 0 Feb 12 08:09:00 fedora kernel: Oops: 0000 [#1] PREEMPT SMP PTI ``` To repro, it looks like you'll need to use a machine with hardware that has iwlwifi in combination with the karg.
Created attachment 2016469 [details] previous boot logs
It's a kernel crash, I'm reassigning it to the right component.
Adding some additional details here. On kernel 6.7.7 on an iwlwifi machine with debugfs=off, it no longer causes a boot failure, but it still causes erratic behavior. Wifi is completely broken and programs frequently and sporadically lock up until the system freezes altogether. I have several other users who are able to repro as well. Please let me know if I can provide any additional context or if help is needed getting a repro. Thanks!
This message is a reminder that Fedora Linux 39 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 39 on 2024-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '39'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 39 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 39 entered end-of-life (EOL) status on 2024-11-26. Fedora Linux 39 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.