Description of problem: since upgrading to F25 yesterday, the wifi speed dropped by an order of magnitude, other devices on the same network still work fine, wired connection works fine the wifi device is a broadcom BCM43225 using the bcma driver booting with an older kernel does not solve the problem. lspci output 09:00.0 Network controller: Broadcom Limited BCM43225 802.11b/g/n (rev 01) Subsystem: Foxconn International, Inc. T77H103.00 Wireless Half-size Mini PCIe Card 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 17 Region 0: Memory at f0500000 (64-bit, non-prefetchable) [size=16K] Capabilities: <access denied> Kernel driver in use: bcma-pci-bridge Kernel modules: bcma Version-Release number of selected component (if applicable): kernel 4.9.5-200.fc25.x86_64 How reproducible: upgrade from F24 to F25 Steps to Reproduce: 1. 2. 3. Actual results: Wifi speeds lower than 1Mbps Expected results: Wifi speed > 20Mbps, other devices on the network work fine, wired connection works fine Additional info: i've selected the kernel component, since i assume it is a driver problem, although changing to an older kernel does not fix the problem
*********** 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 25 kernel bugs. Fedora 25 has now been rebased to 4.10.9-200.fc25. 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.