Hi Verdre, >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 OK; Thanks for this; I read it as 'these two issues have different root causes';
>The L0s and L1 state can be found under "Capabilities: Express (v2) Endpoint >-> LnkCtl" --- LnkCtl: ASPM L0s L1 Enabled; --- >the L1-substates can be found under "Capabilities: L1 PM Substates -> >L1SubCtl1" --- L1SubCtl1: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ --- >make sure L1.2 is enabled and can be entered it is enabled(above output of lspci -vvv); but is there a seperate check to know if it could be *entered*; >maybe make sure that S0Ix sleep is actually reached during suspend by checking cat /sys/devices/system/cpu/cpuidle/low_power_idle_system_residency_us cat: /sys/devices/system/cpu/cpuidle/low_power_idle_system_residency_us: No such file or directory cat /sys/devices/system/cpu/cpuidle/low_power_idle_cpu_residency_us 3565055 >Your testing setup sounds correct and should trigger the "Firmware wakeup >failed" issue >The command timeout should happen quite quickly I am doing different try outs, I will update as soon I could recreate these; Regards, Ganapathi -- 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
