May 06 10:07:09 mahdev-top kernel: ACPI: Low-level resume complete May 06 10:07:09 mahdev-top kernel: smpboot: CPU 3 is now offline May 06 10:07:09 mahdev-top kernel: smpboot: CPU 2 is now offline May 06 10:07:09 mahdev-top kernel: IRQ 19: no longer affine to CPU2 May 06 10:07:09 mahdev-top kernel: smpboot: CPU 1 is now offline May 06 10:07:09 mahdev-top kernel: IRQ 29: no longer affine to CPU1 May 06 10:07:09 mahdev-top kernel: Disabling non-boot CPUs. May 06 10:07:09 mahdev-top kernel: PM: Saving platform NVS memory May 06 10:07:09 mahdev-top kernel: ACPI: EC: EC stopped May 06 10:07:09 mahdev-top kernel: ACPI: EC: event blocked May 06 10:07:09 mahdev-top kernel: ACPI: Preparing to enter system sleep state > May 06 10:07:09 mahdev-top kernel: ACPI: EC: interrupt blocked May 06 10:07:09 mahdev-top kernel: PM: suspend devices took 0.909 seconds May 06 10:07:09 mahdev-top kernel: sd 0:0:0:0: Synchronizing SCSI cache May 06 10:07:09 mahdev-top kernel: printk: Suspending console(s) (use no_consol> May 06 10:07:09 mahdev-top kernel: Freezing remaining freezable tasks. May 06 10:07:09 mahdev-top kernel: OOM killer disabled. May 06 10:07:09 mahdev-top kernel: Freezing user space processes. May 06 10:07:01 mahdev-top slim: (II) AIGLX: Suspending AIGLX clients for > May 06 10:07:01 mahdev-top kernel: PM: Syncing filesystems. May 06 10:07:00 mahdev-top dbus-broker: A security policy denied :1.48 to > May 06 10:07:00 mahdev-top pkexec: j: Executing command [TTY> May 06 10:07:00 mahdev-top pkexec: pam_unix(polkit-1:session): session o> May 06 10:07:00 mahdev-top kernel: PM: suspend entry (deep) May 06 10:07:00 mahdev-top systemd-sleep: Suspending system. May 06 10:07:00 mahdev-top systemd: Starting Suspend. May 06 10:07:00 mahdev-top systemd: Reached target Sleep. May 06 10:07:00 mahdev-top NetworkManager: manag> May 06 10:06:59 mahdev-top dbus-broker: A security policy denied :1.48 to > The full output of journalctl is: May 06 10:06:59 mahdev-top systemd-logind: Lid closed. May 06 10:07:09 mahdev-top systemd: Failed to start Suspend. So not sure as to why shutdown is hanging.Īs far as the issue with suspend here are the concerns I can see from journalctl: May 06 10:07:09 mahdev-top systemd: suspend.target: Failed to set invocation ID for unit: File exists However, I’d say about 50% of the time shutdown hangs. I installed a dkms fix from github for the RTL8192CU chipset. I have been running a USB adapter: Belkin Components F7D2102 802.11n N300 Micro Wireless Adapter v3000. I have also blacklisted the bluetooth module, because it a combo Bluetooth/Wifi adapter. Since a few days after the upgrade to Fedora 30, I have not used akmods, akmod-wl, or broadcom-wl. The Wifi card is: Network controller: Broadcom Inc. Hope this information can shed some light on the bugs I’ve been seeing on here about hanging shutdowns and Broadcom wireless chips having issues. This issue is present even if ‘wl’ kmod is not loaded. When attempting to shut down after this occurs, shutdown hangs. Furthermore, opening a terminal and typing ‘su’ after this happens causes ‘su’ to hang and not prompt for a password. Once woken up and the lid is closed again or any time after that it will not suspend. When the lid is initially closed for the first time it will suspend. I am running XFCE, under power management settings I have it set to while on battery and plugged-in, suspend whenever the laptop lid is closed. Not to mention that if it were a driver issue I do not think one would be able to see nearby access points or any for that matter, but just not connect to them. Even with power savings disabled in my NetworkManager configuration for WiFi, the next issue makes me think that it this issue might be related. When trying to shut down with ‘wl’ kmod loaded shutdown hangs. I have been able to get it to connect a few times by pressing the wireless toggle on/off toggle key on my laptop, however, it does not connect upon start. They are as followed:īroadcom devices using akmods, akmod-wl, broadcom-wl, from RPMFusion will not connect to wireless access points. I have noticed the following issues thus far and feel that they all may be related to a power management issue. I just recently upgraded to Fedora 30 from Fedora 29.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |