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 i
> acpi_call and remove/rescan the parent bridge of wifi (need to be
installed)
Sorry, I made a mistake
acpi_call (need to be installed) and remove/rescan the parent bridge of wifi
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
> But I fail to get these in my device(I don't know why, it is a different
> problem); So, I still fail to confirm we are hitting same issue;
Yeah, the device_dump is also a problematic one on Surface devices.
It's reported that if_ops.device_dump() will cause lockups [1] (e.g. prevent
system pow
Created attachment 285391
[PATCH] mwifiex: debugfs: add entry for device_dump
This is a patch to add debugfs entry for device_dump.
Just to test device_dump functionality on Surface devices.
Usage:
echo 1 | sudo tee /sys/kernel/debug/mwifiex/mlan0/device_dump
--
You received this bug notific
> 1. timeout happens after a resume, if we see below message in dmesg:
>"mwifiex_pci :02:00.0: Refused to change power state, currently in D0"
For me, it says instead:
`mwifiex_pcie :02:00.0: Refused to change power state, currently in D3`
> 2. if device is connected before the 1st s
Hi Ganapathi,
We can't do anything about power_save and firmware crashing. So, I
attached journal log and devcoredump when using with power_save on and
5GHz AP, containing 1) connection instability and 2) firmware crashing
eventually.
I hope it helps in debugging.
Thank you.
--
You received th
Created attachment 290067
mwifiex crash log on SB1 with ps_on, 5GHzAP
- power_save on
- connected to 5GHz AP
- connection instability (ping not responding)
- firmware crashing eventually
Journal log and devcoredump are included in the archive. I kept sending ping to
192.168.1.1 and the output wa
(In reply to Pali Rohár from comment #127)
> Hello!
Hello!
> Tsuchiya & Verdre: Do you have some fixes for instability issues when card
> is in 5GHz AP mode? This is issue which we are observing on 88W8997 SDIO
> wifi chips.
Unfortunately, not yet. I'm using 5GHz AP with just power_save off. May
Thank you for looking into this issue. Reporting current status.
== "mwifiex crash after suspend"
This issue might be the Surface devices specific problem? Not sure.
I know some ways to prevent at least mwifiex crashing:
1. Disabling d3cold for wifi device (even doable on mainline kernels):
Also, ff someone knows devices (other than Surface) that use the same
88W8897 chip (or at least similar PCIe chip like 88W8997), let me know.
I want to get the device as a reference.
Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
*if someone knows devices
--
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.n
== "mwifiex crash on idle/using"
I heard this issue only from Surface 3 and SP5 owners.
It can be fixed by disabling ASPM L1 state. I think this is the hardest issue
to fix. So, I hope at least we could fix the mwifiex reset feature (see below).
== "mwifiex reset feature broken"
I think this is
12 matches
Mail list logo
