Hi Tsuchiya/Verdre, >- "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
1. Command timeout after second suspend could be recreated in my Surface 4; 2. Logs were similar to the one in #91 & #92 by Verdre; 3. It is found that the command, which timed out did not reach the firmware at all and am trying to understand more; 4. Once a command times out, driver dumps few scratch registers and also it triggers the firmware dump; 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; Note that, when the dump is uploaded to user-space, dmesg will say: "== mwifiex dump information to /sys/class/devcoredump end" Could you please share the dump(along with dmesg), which is saved in below file(it is automatically deleted after 5 minutes): ******************************************** /sys/devices/virtual/devcoredump/devcd1/data ******************************************** >- "Firmware wakeup failed" This could also be recreated for the first time now; I kept Surface 4 connected to AP and PING overnight; But I have no much detail yet; I will comeback soon on remaining two concerns you raised in comment#95; Regards, Ganapathi 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
