Created attachment 275033 [details] dmesg output Hi, lately I'm experiencing a lot of firmware crashes on my Thinkpad T470. I've read some posts about Bluetooth being somehow involved in these issues but it doesn't seem to affect the behavior in my case (I'm experiencing these errors with Bluetooth on and off). Please find the dmesg output attached; let me know if I can help somehow. Thank you, lorenzo
Please check if the latest firmware versions still exhibit the same problem. You can download the latest firmware version from here: https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git/
Sorry for the late reply. Issue seems to be still here with firmware 36 (kernel 4.16.6-1-ARCH). dmesg output attached. Thank you, lorenzo
Created attachment 275795 [details] dmesg output with firmware v36
Created attachment 275883 [details] 8265 firmware with debug enabled Hello, please run with the firmware attached and follow the steps here [1]. Please take the time to read the privacy notice here [2]. [1] https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/debugging#firmware_debugging [2] https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/debugging#privacy_aspects Thank you.
One more thing: can you please try our latest driver? There was a fix for channel switch that can be relevant: https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/backport-iwlwifi.git/ thanks.
Ping?
Hi Emmanuel, sorry for not coming back to you. Since I couldn't live without wifi, last week I did some tests with Ubuntu 18.04 live image and since I was not experiencing any issue with wifi I decided to switch distro. I'm now running kernel 4.15.0-20-generic with firmware 34.0.1 and (finger crossed) everything is working ok. I can try to boot a live Antergos image to perform tests with debug enabled using kernel 4.16.6-1-ARCH and firmware 36 (my previous configuration). Thank you, lorenzo
Hi Lorenzo, Ok, so this teaches me that we have a regression... Which makes the bug even worse. One day or another you'll hit it again when you'll update the kernel and firmware. We are really interested in fixing the problems you have. We'll be glad to get the data required.
Hello, I have been having some issues since a few month after some upgrade of Ubuntu on my laptop, namely coming to 18.10, so coming from 4.15 to 4.18, as documented here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802306 Symptom involves random but recurrent high latencies, especially visible when DNS reoslution happens. HW is a ThinkPad T480s, with Intel 8265 card. Issue gets reproduced at home (Livebox 4 gateway, Netgear R7000 WiFi AP, several versions of firmware tested) as well as Office network (Aruba AP225 on ArubaOS v6.5.3.3). Issue is still present in current Ubuntu Disco, based on kernel 5.0. Current workaround is to make firmware v36 file unreadable (rename, delete) so that v34 is picked. Connection works very well for a long time with v34. As much as I can tell, there was no dmesg error, but maybe I need to pass specific flags when loading iwlwifi driver? I did test several versions of the v36 firmware: > -rw-r--r-- 1 root root 2,4M nov. 8 12:34 > /lib/firmware/iwlwifi-8265-36.ucode_36.7596afd4.0.broken > -rw-r--r-- 1 root root 2,4M janv. 9 13:49 > /lib/firmware/iwlwifi-8265-36.ucode_36.9f0a2d68.0.broken > -rw-r--r-- 1 root root 2,4M mai 18 2018 > /lib/firmware/iwlwifi-8265-36.ucode_36.e91976c0.0.broken
(In reply to lissyx+kernel from comment #9) [...] > > Symptom involves random but recurrent high latencies, especially visible > when DNS reoslution happens. > Forgot to add that it's just the most obvious symptom, and that after some time (a few minutes in general, and more on the office's wifi than at time), it's getting completely locked up and no packet can make it, wifi is completely not working.
please open a new bug. This has probably nothing to do with this ticket.
(In reply to Emmanuel Grumbach from comment #11) > please open a new bug. This has probably nothing to do with this ticket. Will do. Any hints on useful informations / debug bits I should track down and produce in a new bug?