Bug 195183

Summary: Wifi randomly fails to work on Surface Pro 3
Product: Drivers Reporter: lribeir1
Component: network-wirelessAssignee: drivers_network-wireless (drivers_network-wireless)
Status: RESOLVED DUPLICATE    
Severity: high CC: andy.shevchenko, gbhat, lribeir1, mercy.speax
Priority: P1    
Hardware: x86-64   
OS: Linux   
Kernel Version: 4.10.7 Subsystem:
Regression: No Bisected commit-id:
Bug Depends on: 109681    
Bug Blocks:    
Attachments: dmesg | grep mwifiex output

Description lribeir1 2017-03-31 13:51:47 UTC
Created attachment 255663 [details]
dmesg | grep mwifiex output

The Wifi on the Surface Pro 3 will intermittently drop. Only running the following commands will make it work again:
  rmmod mwifiex_pcie
  rmmod mwifiex
  modprobe mwifiex_pcie

I've attached my dmesg | grep mwifiex and pasted my lspci below. I've made a script that resets the modules automatically so that I don't have to, but this is a very makeshift fix.

00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller
00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 09)
00:14.0 USB controller: Intel Corporation 8 Series USB xHCI HC (rev 04)
00:16.0 Communication controller: Intel Corporation 8 Series HECI #0 (rev 04)
00:1b.0 Audio device: Intel Corporation 8 Series HD Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 3 (rev e4)
00:1f.0 ISA bridge: Intel Corporation 8 Series LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 8 Series SATA Controller 1 [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 8 Series SMBus Controller (rev 04)
01:00.0 Ethernet controller: Marvell Technology Group Ltd. 88W8897 [AVASTAR] 802.11ac Wireless
Comment 1 Andy Shevchenko 2018-01-01 12:03:30 UTC
Does running
sudo iw dev wlp1s0 set power_save off
solves the issue?
Comment 2 Ganapathi Bhat 2018-11-25 07:12:15 UTC
Hi lribeir1,

Can you re-run your use case with below steps:

1. Enable complete log level:
echo 0xffffffff > /sys/kernel/debug/mwifiex/mlan0/debug_mask

2. After your issue is hit, trigger firmware dump:
cat /sys/kernel/debug/mwifiex/mlan0/device_dump

3. When the dump is complete dmesg will log "mwifiex firmware dump end"

4. Copy the dump as it will be deleted automatically in 5 minutes
cp /sys/devices/virtual/devcoredump/devcd1/data fw_dump.txt

Regards,
Ganapathi
Comment 3 Ganapathi Bhat 2018-11-25 07:14:27 UTC
(In reply to Ganapathi Bhat from comment #2)
> Hi lribeir1,
> 
> Can you re-run your use case with below steps:
> 
> 1. Enable complete log level:
> echo 0xffffffff > /sys/kernel/debug/mwifiex/mlan0/debug_mask
> 
> 2. After your issue is hit, trigger firmware dump:
Here, do not reload the driver, instead collect firmware dump.
> cat /sys/kernel/debug/mwifiex/mlan0/device_dump
> 
> 3. When the dump is complete dmesg will log "mwifiex firmware dump end"
> 
> 4. Copy the dump as it will be deleted automatically in 5 minutes
> cp /sys/devices/virtual/devcoredump/devcd1/data fw_dump.txt
> 
> Regards,
> Ganapathi
Comment 4 Andy Shevchenko 2020-10-12 14:26:49 UTC
It might be even duplicate of #109681
Comment 5 Andy Shevchenko 2021-08-06 15:39:07 UTC

*** This bug has been marked as a duplicate of bug 109681 ***