Description of problem: Installed FC24 on Microsoft SurfacePro3. All works good. I've updated to the latest via dnf and now wifi works when you boot, but eventually stop working or doesn't survive coming back from sleep. Version-Release number of selected component (if applicable): How reproducible: update to the latest packages (I guess its not just the kernel, but the firmware that might have changed) reboot, put the SP3 to sleep and when coming back no network will be found. Additional info: lspci -vvv for the marvel: 01:00.0 Ethernet controller: Marvell Technology Group Ltd. 88W8897 [AVASTAR] 802.11ac Wireless Subsystem: SafeNet (wrong ID) Device 045e Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 61 Region 0: Memory at c0500000 (64-bit, prefetchable) [size=1M] Region 2: Memory at c0400000 (64-bit, prefetchable) [size=1M] Capabilities: [40] Power Management version 3 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [50] MSI: Enable+ Count=1/32 Maskable+ 64bit+ Address: 00000000fee003b8 Data: 0000 Masking: fffffffe Pending: 00000000 Capabilities: [70] Express (v2) Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <1us, L1 unlimited ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset- SlotPowerLimit 10.000W DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend- LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <1us, L1 unlimited ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp+ LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- CommClk+ ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- DevCap2: Completion Timeout: Range ABCD, TimeoutDis+, LTR+, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, OBFF Disabled LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1- EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest- Capabilities: [100 v2] Advanced Error Reporting UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr- CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn- Capabilities: [140 v1] Device Serial Number 00-00-00-00-00-00-00-00 Capabilities: [150 v1] Power Budgeting <?> Capabilities: [160 v1] Latency Tolerance Reporting Max snoop latency: 3145728ns Max no snoop latency: 3145728ns Capabilities: [168 v1] L1 PM Substates L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+ PortCommonModeRestoreTime=70us PortTPowerOnTime=10us Kernel driver in use: mwifiex_pcie Kernel modules: mwifiex_pcie one of the traces: Aug 07 00:39:47 SurfacePro-FC24 kernel: Hardware name: Microsoft Corporation Surface Pro 3/Surface Pro 3, BIOS 3.11.11 50 12/09/2015 Aug 07 00:39:47 SurfacePro-FC24 kernel: Workqueue: events request_firmware_work_func Aug 07 00:39:47 SurfacePro-FC24 kernel: 0000000000000286 0000000017f3cab6 ffff8802432c7c68 ffffffff813dbcaf Aug 07 00:39:47 SurfacePro-FC24 kernel: 0000000000000000 0000000000000000 ffff8802432c7ca8 ffffffff810a742b Aug 07 00:39:47 SurfacePro-FC24 kernel: 0000016b432c7cca 0000000000000008 ffffffffc05c4b40 0000000000000000 Aug 07 00:39:47 SurfacePro-FC24 kernel: Call Trace: Aug 07 00:39:47 SurfacePro-FC24 kernel: [<ffffffff813dbcaf>] dump_stack+0x63/0x84 Aug 07 00:39:47 SurfacePro-FC24 kernel: [<ffffffff810a742b>] __warn+0xcb/0xf0 Aug 07 00:39:47 SurfacePro-FC24 kernel: [<ffffffff810a755d>] warn_slowpath_null+0x1d/0x20 Aug 07 00:39:47 SurfacePro-FC24 kernel: [<ffffffffc04ee835>] wiphy_new_nm+0x645/0x7a0 [cfg80211] Aug 07 00:39:47 SurfacePro-FC24 kernel: [<ffffffffc05b050f>] mwifiex_register_cfg80211+0x3f/0x410 [mwifiex] Aug 07 00:39:47 SurfacePro-FC24 kernel: [<ffffffffc058ccbd>] mwifiex_fw_dpc+0x33d/0x4f0 [mwifiex] Aug 07 00:39:47 SurfacePro-FC24 kernel: [<ffffffff810bca25>] ? usermodehelper_read_unlock+0x15/0x20 Aug 07 00:39:47 SurfacePro-FC24 kernel: [<ffffffff81533aca>] ? _request_firmware+0x39a/0x7e0 Aug 07 00:39:47 SurfacePro-FC24 kernel: [<ffffffff8153410f>] request_firmware_work_func+0x3f/0x80 Aug 07 00:39:47 SurfacePro-FC24 kernel: [<ffffffff810c0d74>] process_one_work+0x184/0x440 Aug 07 00:39:47 SurfacePro-FC24 kernel: [<ffffffff810c107e>] worker_thread+0x4e/0x480 Aug 07 00:39:47 SurfacePro-FC24 kernel: [<ffffffff810c1030>] ? process_one_work+0x440/0x440 Aug 07 00:39:47 SurfacePro-FC24 kernel: [<ffffffff810c1030>] ? process_one_work+0x440/0x440 Aug 07 00:39:47 SurfacePro-FC24 kernel: [<ffffffff810c6f68>] kthread+0xd8/0xf0 Aug 07 00:39:47 SurfacePro-FC24 kernel: [<ffffffff817e0982>] ret_from_fork+0x22/0x40 Aug 07 00:39:47 SurfacePro-FC24 kernel: [<ffffffff810c6e90>] ? kthread_worker_fn+0x180/0x180 Aug 07 00:39:47 SurfacePro-FC24 kernel: ---[ end trace d6ce2f6fae18ffbb ]--- Aug 07 00:39:47 SurfacePro-FC24 kernel: ------------[ cut here ]------------ Aug 07 00:39:47 SurfacePro-FC24 kernel: WARNING: CPU: 1 PID: 301 at net/wireless/core.c:364 wiphy_new_nm+0x619/0x7a0 [cfg80211] I'm running now on the 4.5.5-300 kernel and its working.
noticed this also happen on the original kernel of the fc24 ISO, 4.5.5-300 though it took a long time to happen, but once the SP3 was at sleep, same thing happens. the wifi couldn't see any wireless network until reboot.
Switching to kernel as that's the kernel/firmware issue so that it had a better chance to be resolved.
I have the SP3 with me and available to debug, whatever info is needed.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is 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 24 kernel bugs. Fedora 24 has now been rebased to 4.7.4-200.fc24. 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 25, and are still experiencing this issue, please change the version to Fedora 25. If you experience different issues, please open a new bug report for those.
did not fix the issue. I still see plenty of "PREP_CMD: FW is in bad state" and no WiFi is working.
*********** 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 24 kernel bugs. Fedora 25 has now been rebased to 4.10.9-100.fc24. 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 26, and are still experiencing this issue, please change the version to Fedora 26. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.