Bug 108271
| Summary: | iwlwifi-7265: connection freezes with firmware version 17.246894.0 | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | Stijn Tintel (stijn+bugs) |
| Component: | network-wireless | Assignee: | DO NOT USE - assign "network-wireless-intel" component instead (linuxwifi) |
| Status: | CLOSED DUPLICATE | ||
| Severity: | normal | ||
| Priority: | P1 | ||
| Hardware: | Intel | ||
| OS: | Linux | ||
| See Also: |
https://bugzilla.kernel.org/show_bug.cgi?id=97291 https://bugzilla.kernel.org/show_bug.cgi?id=107861 https://bugzilla.kernel.org/show_bug.cgi?id=103531 https://bugzilla.kernel.org/show_bug.cgi?id=107471 |
||
| Kernel Version: | 4.3.0 | Subsystem: | |
| Regression: | Yes | Bisected commit-id: | |
| Attachments: |
trace.dat
trace.dat with uapsd_disable=1 trace.dat with uapsd_disable=1 |
||
|
Description
Stijn Tintel
2015-11-21 21:33:29 UTC
Please run tracing as explained here: https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/debugging Thanks. If you need hours to reproduce the problem, tracing might not be the right tool. Let's start with a dmesg output. You don't see anything special from iwlwifi there? (In reply to Emmanuel Grumbach from comment #2) > Let's start with a dmesg output. You don't see anything special from iwlwifi > there? Nothing in dmesg at all, just RF_KILL when I disable wireless to solve the problem: nov 19 06:17:25 sylvester.nomad.adlevio.net kernel: kvm: zapping shadow pages for mmio generation wraparound nov 19 06:22:36 sylvester.nomad.adlevio.net kernel: iwlwifi 0000:02:00.0: RF_KILL bit toggled to disable radio. I will install the v17 firmware again, try to reproduce it and run tracing when it happens. Any news? Did you try to disable 11n (11n_disable=1 as a module parameter to iwlwifi)? Created attachment 195551 [details]
trace.dat
After installing the v17 firmware again, I was unable to reproduce the problem. I then remembered I had enabled U-APSD again to test if the latency spikes I had on my AP (DAP-2695) would be fixed. It still took a while, but today the problem happened twice. The laptop is in a different location than where I usually use it, so it's possible that uapsd_disable=1 is unrelated, not sure. I ran "trace-cmd record -e iwlwifi" and ran a ping to the def gw when I noticed the connection hang. Ok thanks. I'll take a look. Note that there are serious interrop issues with uAPSD, this is why it is disable by default. If the problem doesn't reproduce with uapsd_disable=1 (as default), please close this issue. Problem just happened again with uapsd_disable=1. sylvester ~ # cat /sys/module/iwlwifi/parameters/uapsd_disable Y Created attachment 196161 [details]
trace.dat with uapsd_disable=1
I don't see anything bad in this tracing. What are the symptoms? You run pings and the pings stop? Associated but unable to ping default gateway. I only start the trace when I notice the problem (ssh sessions no longer respond, websites no longer open). Are you using Bluetooth? Can you try to disable Bluetooth? Please let trace-cmd run for more time and do some network operations while it is running. Thanks Created attachment 196401 [details]
trace.dat with uapsd_disable=1
Still associated, unable to ping anything in local subnet
Tried disconnect + reconnect -> network not found
Toggle rfkill on/off -> reconnected fine
Missed the bluetooth part. I am using bluetooth, and I need it (working remote), so disabling it is difficult. Did you mean to completely disable bluetooth, or just disable bt_coex_active? I meant completely disable BT. Please try with firmware -16.ucode. Please remove the -17.ucode version before doing so. I also recommend you install the latest BT firmware from linux-firmware.git. *** This bug has been marked as a duplicate of bug 107471 *** |