Hi Verdre and Ganapathi,
I own Surface Book 1 (Skylake, same as Surface Pro 4) and Surface 3 (non-pro,
Intel Atom Cherry Trail) for daily usage
and recently I got Surface Pro 4 (with broken sensor) for debugging purposes.
env:
- freshly installed Fedora 31 Beta on an external USB drive and use it on SP4
- run `sudo dnf upgrade` and now `uname -r` shows `5.3.2-300.fc31.x86_64`
@Ganapathi
> I am doing different try outs, I will update as soon I could recreate these;
You mean you're having trouble recreating issues?
On my SP4:
- "cmd_timeout"
This issue will occur after a second suspend like the dmesg log on
Comment#91 regardless of 2.4GHz/5GHz AP or power_save on/off. So, I'm not sure
why you cannot recreate this issue.
- "Firmware wakeup failed"
This issue will randomly occur after a while when using with 5GHz
AP+power_save on
- "WLAN FW already running! Skip FW dnld" after card reset
As you can see on the dmesg log (Comment#91), after card reset, the
firmware will not be re-downloaded on Surface devices. I think that
re-downloading the firmware is the expected behavior.
You may recreate this issue by this command:
echo 1 | sudo tee /sys/kernel/debug/mwifiex/mlan0/reset
After resetting, it shows these messages repeatedly on dmesg and wifi is
not usable anymore:
kern :info : [ 175.478500] mwifiex_pcie 0000:02:00.0: cmd_wait_q terminated:
-110
kern :info : [ 175.478510] mwifiex_pcie 0000:02:00.0: deleting the crypto
keys
Maybe this is the simplest one to fix? and at least if resetting works,
we can continue to use wifi.
To reset the card with firmware re-downloading, currently I have to call
an ACPI method using acpi_call and remove/rescan the parent bridge of
wifi (need to be installed) like this:
WIFI_PARENT="0000:00:1d.0" # SP4 specific
ACPI_WIFI_RST_PATH="\_SB.PCI0.RP09.PXSX.PRWF._RST" # SP4 specific
acall(){ echo "$1" | tee /proc/acpi/call >/dev/null && cat
/proc/acpi/call;echo;} # wrapper
modprobe acpi_call
acall $ACPI_WIFI_RST_PATH
echo 1 | tee "/sys/bus/pci/devices/$WIFI_PARENT/remove"
sleep 1
echo 1 | tee /sys/bus/pci/rescan
---
By the way, I find 2.4GHz AP is much more stable with even power_save
on. 5GHz AP with power_save on causes wifi stop without any message on
dmesg.
It seems that showing APs (e.g. `nmcli d wifi list`) will temporarily
fix the wifi stop.
This is another issue from what we're discussing now, though.
Best regards,
Tsuchiya, Yuto (kitakar5525)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1730924
Title:
Wifi does down "crash" in Surface Pro 4
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1730924/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
