FS#44916 - [wpa_supplicant] Wifi connection problems on Lenovo X1 Carbon 2015 // Intel Wifi 7265 / Linux 4.0.1

Attached to Project: Arch Linux
Opened by Nico Schottelius (telmich) - Saturday, 09 May 2015, 12:56 GMT
Last edited by Bartłomiej Piotrowski (Barthalion) - Friday, 10 August 2018, 14:04 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:

When running wpa_supplicant (only, no networkmanager) on this device, I experience the following problems:

* wpa_supplicant thinks it is connected to the AP, but the AP thinks there is no device connected (tested with two Android Phones)
** This happens after some minutes (~5 up to ~40)
** All network connections are not working anymore, IP is still there (from dhcp)
* Connection to some APs is established (from side of wpa_supplicant), but no IP received at all (other devices however work)
* wpa_supplicant does not scan or reassociate after waking up from suspend - I need to manually issue scan/reassociate
* wpa_supplicant disconnects from the network, claiming the key is wrong
** the key is correct
** after issueing reasscociate it usually works, however sometimes it does not
** In these case select_network XYZ sometimes solves the problem

It is possible that this is a combination problem of Linux 4.x and wpa_supplicant - however due to missing support for the mouse, I have only used this notebook with the 4.0 kernel, not with 3.x.

Additional info:
* package version(s)
* config and/or log files etc.



<3>CTRL-EVENT-DISCONNECTED bssid=44:74:6c:4f:4a:6b reason=3
<3>WPA: 4-Way Handshake failed - pre-shared key may be incorrect
<3>CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="unterwegs" auth_failures=1 duration=10 reason=WRONG_KEY


[12:45] wurzel:modprobe.d% pacman -Q | grep -e wpa_supp -e ^linux
linux 4.0.1-1
linux-api-headers 3.18.5-1
linux-firmware 20150410.ec89525-1
linux-headers 4.0.1-1
wpa_supplicant 1:2.3-1
wpa_supplicant_gui 2.3-1
[12:45] wurzel:modprobe.d%


[14:35] wurzel:~% lspci
00:00.0 Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI (rev 09)
00:02.0 VGA compatible controller: Intel Corporation Broadwell-U Integrated Graphics (rev 09)
00:03.0 Audio device: Intel Corporation Broadwell-U Audio Controller (rev 09)
00:14.0 USB controller: Intel Corporation Wildcat Point-LP USB xHCI Controller (rev 03)
00:16.0 Communication controller: Intel Corporation Wildcat Point-LP MEI Controller #1 (rev 03)
00:19.0 Ethernet controller: Intel Corporation Ethernet Connection (3) I218-V (rev 03)
00:1b.0 Audio device: Intel Corporation Wildcat Point-LP High Definition Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #2 (rev e3)
00:1c.1 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #3 (rev e3)
00:1c.5 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #6 (rev e3)
00:1d.0 USB controller: Intel Corporation Wildcat Point-LP USB EHCI Controller (rev 03)
00:1f.0 ISA bridge: Intel Corporation Wildcat Point-LP LPC Controller (rev 03)
00:1f.3 SMBus: Intel Corporation Wildcat Point-LP SMBus Controller (rev 03)
00:1f.6 Signal processing controller: Intel Corporation Wildcat Point-LP Thermal Management Controller (rev 03)
04:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
0a:00.0 SATA controller: Samsung Electronics Co Ltd Device a801 (rev 01)


[14:36] wurzel:~% lspci -vv -s 04:00.0
04:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
Subsystem: Intel Corporation Dual Band Wireless-AC 7265
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 56
Region 0: Memory at f1100000 (64-bit, non-prefetchable) [size=8K]
Capabilities: <access denied>
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi

[14:55] wurzel:~% uname -r
4.0.1-1-ARCH


Steps to reproduce:

This task depends upon

Closed by  Bartłomiej Piotrowski (Barthalion)
Friday, 10 August 2018, 14:04 GMT
Reason for closing:  None
Additional comments about closing:  The issue is long after expiry date.
Comment by plasmoid (plasmoid) - Monday, 18 May 2015, 06:04 GMT
I have a similar (the same) problem on a Dell XPS15 (Intel 7260). Everything works with linux-3.19.3
Comment by Nico Schottelius (telmich) - Tuesday, 19 May 2015, 15:18 GMT
Some more details: When pinging the next router (i.e. the hotspot) after some time the latency increases from miliseconds to seconds:

64 bytes from 192.168.43.1: icmp_seq=1103 ttl=64 time=9.64 ms
64 bytes from 192.168.43.1: icmp_seq=1104 ttl=64 time=2.45 ms
64 bytes from 192.168.43.1: icmp_seq=1105 ttl=64 time=2.29 ms
64 bytes from 192.168.43.1: icmp_seq=1106 ttl=64 time=2.29 ms
64 bytes from 192.168.43.1: icmp_seq=1107 ttl=64 time=342 ms
64 bytes from 192.168.43.1: icmp_seq=1108 ttl=64 time=2.43 ms
64 bytes from 192.168.43.1: icmp_seq=1109 ttl=64 time=2.46 ms
64 bytes from 192.168.43.1: icmp_seq=1110 ttl=64 time=2.19 ms
64 bytes from 192.168.43.1: icmp_seq=1111 ttl=64 time=2.58 ms
64 bytes from 192.168.43.1: icmp_seq=1112 ttl=64 time=20.2 ms
64 bytes from 192.168.43.1: icmp_seq=1113 ttl=64 time=1.75 ms
64 bytes from 192.168.43.1: icmp_seq=1114 ttl=64 time=2.69 ms
64 bytes from 192.168.43.1: icmp_seq=1115 ttl=64 time=3.01 ms
64 bytes from 192.168.43.1: icmp_seq=1123 ttl=64 time=3781 ms
64 bytes from 192.168.43.1: icmp_seq=1124 ttl=64 time=2795 ms
64 bytes from 192.168.43.1: icmp_seq=1125 ttl=64 time=1795 ms


After that, the connection completly stops to work
Comment by plasmoid (plasmoid) - Saturday, 04 July 2015, 14:48 GMT
For me it seems to be a problem with linux-firmware. Downgrading to 20150206.17657c3-1 fixes the problem.
Comment by Laurent Carlier (lordheavy) - Wednesday, 22 July 2015, 16:05 GMT
Please test with linux-firmware-20150722.e10097a in testing
Comment by Nico Schottelius (telmich) - Friday, 24 July 2015, 21:00 GMT
Seems to work fine for some hours so far - giving more feedback in a couple of days, watching when changing the APs
Comment by Nico Schottelius (telmich) - Sunday, 26 July 2015, 22:34 GMT
After trying this firmware, the problem has slightly changed, but not fixed: I now loose the connection to a previously stable AP after some time (~1-2 hours) and there is no scanning anymore -> the connection is dead until I manually issue "scan" in wpa_cli
Comment by Nico Schottelius (telmich) - Monday, 27 July 2015, 09:41 GMT
This problem is now biting me more than the previous one, as the connection completely aborts and never restores on its own:

<3>WPA: Group rekeying completed with d4:ca:6d:e5:d3:0b [GTK=CCMP]
<3>CTRL-EVENT-DISCONNECTED bssid=d4:ca:6d:e5:d3:0b reason=4 locally_generated=1
<3>CTRL-EVENT-SCAN-STARTED
<3>CTRL-EVENT-SCAN-RESULTS
<3>CTRL-EVENT-SCAN-STARTED
<3>CTRL-EVENT-SCAN-RESULTS
<3>CTRL-EVENT-SCAN-STARTED
<3>CTRL-EVENT-SCAN-RESULTS
> scan
OK
<3>CTRL-EVENT-SCAN-STARTED
<3>CTRL-EVENT-SCAN-RESULTS
<3>SME: Trying to authenticate with d4:ca:6d:e5:d3:0b (SSID='freiheit' freq=2412 MHz)
<3>Trying to associate with d4:ca:6d:e5:d3:0b (SSID='freiheit' freq=2412 MHz)
<3>Associated with d4:ca:6d:e5:d3:0b
<3>WPA: Key negotiation completed with d4:ca:6d:e5:d3:0b [PTK=CCMP GTK=CCMP]
<3>CTRL-EVENT-CONNECTED - Connection to d4:ca:6d:e5:d3:0b completed [id=12 id_str=freiheit]
<3>WPA: Group rekeying completed with d4:ca:6d:e5:d3:0b [GTK=CCMP]
<3>CTRL-EVENT-DISCONNECTED bssid=d4:ca:6d:e5:d3:0b reason=4 locally_generated=1
<3>CTRL-EVENT-SCAN-STARTED
<3>CTRL-EVENT-SCAN-RESULTS
<3>CTRL-EVENT-SCAN-STARTED
<3>CTRL-EVENT-SCAN-RESULTS
<3>CTRL-EVENT-SCAN-STARTED
<3>CTRL-EVENT-SCAN-RESULTS
> scan
OK

I'll downgrade to linux-firmware-20150527.3161bfa-1-any.pkg.tar.xz to get back to a better state - just needing to manually fix roughly once or twice per day.

Loading...