Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: On Dell Inspiron 15 (3573), when restarting system from sleep, the wireless no longer works. Cycling NetworkManager does not help. The only way to fix this issue is to reboot. Version-Release number of selected component (if applicable): Fedora 29 x86_64, all kernels so far. How reproducible: 100% Steps to Reproduce: 1. Boot Fedora 29 (or Fedora Live 29), connecting to wireless network. 2. Put computer to sleep 3. Wake the computer Actual results: System resumes all except for wireless. Wireless icon is greyed out (Gnome), and "select network" returns nothing. Wireless does not reconnect (or even prompt to reconnect). Expected results: Wireless to reconnect to network Additional info: Upon waking up this is what dmesg shows me: [ 451.508561] Restarting tasks ... [ 451.515804] Bluetooth: hci0: read Intel version: 3707100100012d0d00 [ 451.515809] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.0.1.2d.d.bseq [ 451.516119] done. [ 451.568896] PM: suspend exit [ 451.579039] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready [ 451.603078] ------------[ cut here ]------------ [ 451.603081] Timeout waiting for hardware access (CSR_GP_CNTRL 0xffffffff) [ 451.603154] WARNING: CPU: 1 PID: 1219 at drivers/net/wireless/intel/iwlwifi/pcie/trans.c:2009 iwl_trans_pcie_grab_nic_access+0x1e1/0x220 [iwlwifi] After the call trace and register dump, I see this message repeatedly [ 452.595431] iwlwifi 0000:01:00.0: Could not load the [0] uCode section [ 452.595439] iwlwifi 0000:01:00.0: Failed to start INIT ucode: -5 [ 452.595441] iwlwifi 0000:01:00.0: Failed to run INIT ucode: -5 [ 452.595442] iwlwifi 0000:01:00.0: Failed to start RT ucode: -5 journalctl reports this: -- The start-up result is done. Dec 14 07:58:19 myhost.mydomain.com wpa_supplicant[1294]: Could not set interface wlp1s0 flags (UP): Input/output error Dec 14 07:58:19 myhost.mydomain.com wpa_supplicant[1294]: nl80211: Could not set interface 'wlp1s0' UP Dec 14 07:58:19 myhost.mydomain.com wpa_supplicant[1294]: nl80211: deinit ifname=wlp1s0 disabled_11b_rates=0 Dec 14 07:58:20 myhost.mydomain.com kernel: iwlwifi 0000:01:00.0: Could not load the [0] uCode section Dec 14 07:58:20 myhost.mydomain.com kernel: iwlwifi 0000:01:00.0: Failed to start INIT ucode: -5 Dec 14 07:58:20 myhost.mydomain.com kernel: iwlwifi 0000:01:00.0: Failed to run INIT ucode: -5 Dec 14 07:58:20 myhost.mydomain.com kernel: iwlwifi 0000:01:00.0: Failed to start RT ucode: -5 Dec 14 07:58:22 myhost.mydomain.com wpa_supplicant[1294]: Could not set interface wlp1s0 flags (UP): Input/output error Dec 14 07:58:22 myhost.mydomain.com wpa_supplicant[1294]: WEXT: Could not set interface 'wlp1s0' UP Dec 14 07:58:22 myhost.mydomain.com wpa_supplicant[1294]: wlp1s0: Failed to initialize driver interface Dec 14 07:58:22 myhost.mydomain.com NetworkManager[1219]: <error> [1544792302.6551] sup-iface[0x559bf891ec40,wlp1s0]: error adding interface: wpa_supplicant couldn't grab this interface. Dec 14 07:58:22 myhost.mydomain.com NetworkManager[1219]: <info> [1544792302.6552] device (wlp1s0): supplicant interface state: starting -> down Notes: I changed out the network card to rule that out. Current card is: Intel Corporation Wireless 3160 (rev 83) System firmware is up to date. This is my first bug report, so please be kind.
This seems a kernel bug, changing component
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 29 kernel bugs. Fedora 29 has now been rebased to 4.20.5-200.fc29. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those.
Yes, I can confirm this issue is still occurring in kernel 4.20.5-200.fc29
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 29 kernel bugs. Fedora 29 has now been rebased to 5.2.9-100.fc29. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 30, and are still experiencing this issue, please change the version to Fedora 30. If you experience different issues, please open a new bug report for those.
Still happening under Fedora 30 - 5.2.7-200.fc30.x86_64
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 30 kernel bugs. Fedora 30 has now been rebased to 5.5.7-100.fc30. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 31, and are still experiencing this issue, please change the version to Fedora 31. If you experience different issues, please open a new bug report for those.
Yes still happening on Fedora 30 : Linux 5.5.8-100.fc30.x86_64 #1 SMP Thu Mar 5 21:55:51 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Happens under Fedora 31 and 32 Beta. Either fix this problem or close the bug. A year and a half is long enough.
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. 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 Fedora 'version' of '32'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 32 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 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 please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.