Thanks Andy, indeed with new kernels all the stability issues should be
gone.
What remains unsolved are all the firmware bugs without workarounds (see
the list I put together in this email: https://lore.kernel.org/linux-
wireless/771f1f07-882b-2eeb-36fa-126c9b8d5...@v0yd.nl/) and the patch to
Hi everyone,
so Tsuchiya and I have been looking into this quite a lot for the last
few weeks and we've identified several issues and tried to find the
underlying reasons as far as possible.
We hope this information will be helpful for you in indentifying issues
with the firmware and the driver
Hi everyone,
a few months have passed, any news about this bug?
Regards,
Jonas
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1730924
Title:
Wifi does down "crash" in Surface Pro 4
Sorry, last comment was sent accidentally...
Hi Ganapathi,
so I've been running a 5.4 kernel with your changes from comment#105 for
some time now, and I'm still seeing the "Refused to change power state,
currently in D3" messages after resuming from the second suspend.
It seems like the
Hi Ganapathi,
so I've been running a 5.4 kernel with your changes from
https://bugzilla.kernel.org/show_bug.cgi?id=109681#c105 for some time
now,
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hi Ganapathi,
since you can now reproduce the issues, are there any updates on a
proper fix in the firmware or the kernel driver?
Regards,
Jonas
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Created attachment 285447
firmware dump of command timeout issue
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1730924
Title:
Wifi does down "crash" in Surface Pro 4
Status in Linux:
Created attachment 285445
dmesg of command timeout issue
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1730924
Title:
Wifi does down "crash" in Surface Pro 4
Status in Linux:
Hi Ganapathi and Tsuchiya,
here's a dmesg and a firmware dump of the command timeout issue. It
wasn't hard to get it, the devcoredump entry appeared as soon as
"mwifiex dump information to /sys/class/devcoredump end" was written to
the log.
Regards,
Jonas
--
You received this bug notification
Created attachment 285335
systemd journal kernel log from boot until command timeout issue
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1730924
Title:
Wifi does down "crash" in
Hi Ganapathi,
getting the logs turned out to be harder than I expected, with the
while-loop method the issue didn't happen (while the download speed of
wget, which I used to reproduce the issue, sometimes dropped to near 0,
it always managed to recover and went back up again).
Since the
Created attachment 285333
dmesg of command timeout issue
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1730924
Title:
Wifi does down "crash" in Surface Pro 4
Status in Linux:
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
> Could you give inputs on how did you get Fedora 30 installed on Surface 4; I
> created the image using 'dd' and tried to boot from it;It would get to grub,
> after I was getting the _ cursor forever;
That's weird, not sure why that wouldn't be working, if you get to grub
you probably did
Hi Ganapathi,
> OK; Thanks for this; I read it as 'these two issues have different root
> causes';
Not sure if that's the case since we enable link power saving after
every suspend again.
> it is enabled(above output of lspci -vvv); but is there a seperate check to
> know if it could be
Hi Ganapathi,
thank you for picking this up again. To reproduce the issue it should be
enough to make sure L1.2 is enabled and can be entered (all other
L-states are enabled), that should be the case by default when using
Fedora 30. The issue might then appear at any time, although it seems to
I've been looking into this for the last few days and it turns out the
issue is definitely caused by PCI link power management: Using the
CONFIG_PCIEASPM_DEBUG config option of the kernel I was able to track
the issue down to the PCI ASPM L1.2 power saving state (set link_state
of the parent PCI
Hi,
this still seems to be an issue on a lot of Surface devices and I'm not
sure if it was ever solved.
I own a Surface Pro 2017 and I'm seeing the same issues as in
#Comment74, the issue happens randomly after some time (sometimes hours,
sometimes minutes) and is easily reproducible by
18 matches
Mail list logo
