> 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 power off) I also confirmed that by 1. adding debugfs entry for calling that function 2. and called the function via debugfs (echo 1 | sudo tee /sys/kernel/debug/mwifiex/mlan0/device_dump) Sometimes I can get the device_dump log, sometimes I can't and it prevents system power off. I will post the patch which adds the debugfs entry to the next comment. I will post the dump log (along with the dmesg log) as soon as I manage to get the logs after wifi malfunctioning. By the way, the user manual on drivers/net/wireless/marvell/mwifiex/README describes that device_dump can be obtained by `cat fw_dump` but the debugfs entry does not exist anymore. References: [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730924/comments/99 Comment #99 : Bug #1730924 “Wifi does down “crash” in Surface Pro 4” : Bugs : linux package : Ubuntu -- 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
