Hi Ganapathi,

I'm making progress with figuring out potential workarounds for this
issue right now, seems like the "Firmware wakeup failed" error on resume
indeed is caused by another issue (that might still be related to PCI
connection/ASPM issues) than the command timeout: I wasn't seeing the
"Firmware wakeup failed" error at all so far, it only started appearing
after I went back to a clean kernel and tried disabling L1.2 to fix the
command timeout. While that indeed fixed the command timeout issue, the
"Firmware wakeup failed" issue wasn't fixed. Turns out I had at least
two changes in my modified kernel sources that (combined) fix the
"Firmware wakeup failed" issue, I'm trying to isolate those changes
right now.

Your testing setup sounds correct and should trigger the "Firmware
wakeup failed" issue (it happens after only two suspend cycles here),
maybe make sure that S0Ix sleep is actually reached during suspend by
checking if
/sys/devices/system/cpu/cpuidle/low_power_idle_system_residency_us and
/sys/devices/system/cpu/cpuidle/low_power_idle_cpu_residency_us are not
0.

The command timeout should happen quite quickly (less than 5 minutes)
when downloading data, although I can't say anything for devices other
than my Pro 2017, the occurrences might be a lot rarer on other devices.

You can check which L-states and substates are enabled by executing
"lspci -vvv" as root. The L0s and L1 state can be found under
"Capabilities: Express (v2) Endpoint -> LnkCtl" and the L1-substates can
be found under "Capabilities: L1 PM Substates -> L1SubCtl1" (enabled
substates are marked with a "+" after the state, disabled ones with a
"-"). Or you can compile your kernel with CONFIG_PCIEASPM_DEBUG and read
the value from /sys/bus/pci/devices/PARENT_BRIDGE/power/link_state

Thanks,
Jonas

-- 
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
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to