FS#30319 - [linux] 3.4.2 can't connect to a wifi with WPA2 encryption

Attached to Project: Arch Linux
Opened by Pablo (belerofonte) - Saturday, 16 June 2012, 16:47 GMT
Last edited by Tobias Powalowski (tpowa) - Monday, 05 November 2012, 15:19 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

After upgrading to kernel 3.4.2 I can no longer connect to a wifi with WPA2 encryption. I have no problems connecting to a Wifi with WEP.

dmesg output:

[ 2248.881918] iwlwifi 0000:03:00.0: ACTIVATE a non DRIVER active station id 0 addr c0:3f:0e:f3:f9:27
[ 2248.881940] ------------[ cut here ]------------
[ 2248.881959] WARNING: at drivers/net/wireless/iwlwifi/iwl-agn-sta.c:809 iwl_send_lq_cmd+0x202/0x210 [iwlwifi]()
[ 2248.881963] Hardware name: Precision M4500
[ 2248.881966] Modules linked in: aes_x86_64 cryptd aes_generic btusb bluetooth snd_hda_codec_hdmi usbhid hid usb_storage cdc_acm uas uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core videodev media vboxnetflt(O) vboxdrv(O) joydev pcmcia arc4 snd_hda_codec_idt iwlwifi snd_hda_intel mac80211 snd_hda_codec ppdev nouveau snd_hwdep dell_wmi snd_pcm firewire_ohci sparse_keymap sdhci_pci cfg80211 yenta_socket ehci_hcd snd_page_alloc serio_raw parport_pc firewire_core sdhci dell_laptop iTCO_wdt snd_timer pcmcia_rsrc i7core_edac mxm_wmi microcode coretemp snd evdev e1000e crc32c_intel usbcore edac_core rfkill dcdbas mmc_core psmouse soundcore i2c_i801 pcspkr iTCO_vendor_support crc_itu_t usb_common pcmcia_core wmi parport i2c_algo_bit battery drm_kms_helper ttm drm video ac button i2c_core cpufreq_powersave acpi_cpufreq mperf processor ext4 crc16 jbd2 mbcache sr_mod sd_mod cdrom ahci libahci libata scsi_mod
[ 2248.882068] Pid: 2163, comm: kworker/u:1 Tainted: G O 3.4.2-2-ARCH #1
[ 2248.882071] Call Trace:
[ 2248.882080] [<ffffffff810515cf>] warn_slowpath_common+0x7f/0xc0
[ 2248.882086] [<ffffffff8105162a>] warn_slowpath_null+0x1a/0x20
[ 2248.882097] [<ffffffffa0445ab2>] iwl_send_lq_cmd+0x202/0x210 [iwlwifi]
[ 2248.882109] [<ffffffffa04460b1>] iwl_restore_stations+0x381/0x400 [iwlwifi]
[ 2248.882120] [<ffffffffa044fa11>] iwlagn_commit_rxon+0x2e1/0x830 [iwlwifi]
[ 2248.882130] [<ffffffffa043e757>] ? iwlagn_set_rxon_chain+0x177/0x2b0 [iwlwifi]
[ 2248.882141] [<ffffffffa04505bd>] iwlagn_bss_info_changed+0x1cd/0x630 [iwlwifi]
[ 2248.882154] [<ffffffffa0535900>] ? __sta_info_destroy+0x370/0x570 [mac80211]
[ 2248.882164] [<ffffffffa0531815>] ieee80211_bss_info_change_notify+0x135/0x2f0 [mac80211]
[ 2248.882179] [<ffffffffa05674d0>] ieee80211_destroy_auth_data+0x50/0x80 [mac80211]
[ 2248.882193] [<ffffffffa056be42>] ieee80211_sta_work+0x7e2/0xc80 [mac80211]
[ 2248.882200] [<ffffffff8107f0f9>] ? finish_task_switch+0x49/0xd0
[ 2248.882206] [<ffffffff814683d1>] ? __schedule+0x431/0x900
[ 2248.882219] [<ffffffffa053fe69>] ieee80211_iface_work+0x2c9/0x360 [mac80211]
[ 2248.882226] [<ffffffff8106d4ca>] process_one_work+0x12a/0x440
[ 2248.882239] [<ffffffffa053fba0>] ? ieee80211_teardown_sdata+0xf0/0xf0 [mac80211]
[ 2248.882245] [<ffffffff8106dd2e>] worker_thread+0x12e/0x2d0
[ 2248.882250] [<ffffffff8106dc00>] ? manage_workers.isra.25+0x1f0/0x1f0
[ 2248.882256] [<ffffffff810731d3>] kthread+0x93/0xa0
[ 2248.882262] [<ffffffff8146baa4>] kernel_thread_helper+0x4/0x10
[ 2248.882268] [<ffffffff81073140>] ? kthread_freezable_should_stop+0x70/0x70
[ 2248.882273] [<ffffffff8146baa0>] ? gs_change+0x13/0x13
[ 2248.882276] ---[ end trace cc381ada84eca730 ]---
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Monday, 05 November 2012, 15:19 GMT
Reason for closing:  Fixed
Comment by Mike DeTuri (Scrivener) - Saturday, 16 June 2012, 20:03 GMT
I'm not sure if my problem is related. I'm using a wireless USB adapter (ath9k_htc) over WPA2 and it won't obtain an IP address. I reverted back to my the old kernel and works fine.
Comment by Jiri Wiesner (jiriwiesner) - Sunday, 17 June 2012, 06:01 GMT
I had a similar problem with exactly the same kernel (linux-3.4.2-2) and driver (iwlwifi) - authentication with wpa_supplicant fails. The output of lspci, iwconfig, kernel messages and wpa_supplicant -iwlan0 -c/etc/wpa_supplicant.conf is attached. I solved the problem by temporarily reverting to 3.3.7 so I got my connetion back and now, I'm running the linux-lts kernel which works just fine :-).
   wpa_issue_3.4.2.log (40.2 KiB)
Comment by bminaker (dr.dynamics) - Tuesday, 19 June 2012, 03:08 GMT
Also not sure if this is related, but I can report that using any of the stock Arch Linux kernels 3.4-1, 3.4.2-2 or 3.4.3-1, (or Fedora 17 with kernel 3.4.2), breaks the Realtek rtl8192cu driver, at least with WEP on. Times out trying to connect (using NetworkManager in KDE). Reverting to 3.3.8-1 solves the problem.
Comment by Pablo (belerofonte) - Tuesday, 19 June 2012, 21:20 GMT
Still present in 3.4.3. Although I can connect to some WLAN with WPA2 encryption, I can not connect to others. Dmesg message is iwlwifi 0000:03:00.0: ACTIVATE a non DRIVER active station id 0 addr c0:3f:0e:f3:f9:27.

This issue is not present in kernel 3.3.8
Comment by Pablo (belerofonte) - Thursday, 21 June 2012, 14:05 GMT
Should I report upstream?
Comment by bminaker (dr.dynamics) - Saturday, 23 June 2012, 17:50 GMT
I've just tried kernel 3.4.4, and my rtl8192cu still won't connect. Not sure if this is related:
https://bugzilla.kernel.org/show_bug.cgi?id=43044
Comment by Pablo (belerofonte) - Tuesday, 26 June 2012, 11:20 GMT
For me is solved on 3.4.4.

I think the problem with rtl8192cu is a different problem.
Comment by Mike DeTuri (Scrivener) - Tuesday, 26 June 2012, 13:29 GMT
I might have a different issue then. 3.4.4 didn't fix the "cannot obtain IP address" issue with my ath9k_htc USB device.
Comment by Kevin Murphy (kemurphy) - Thursday, 28 June 2012, 09:47 GMT
  • Field changed: Percent Complete (100% → 0%)
Still not fixed for me with 3.4.4-2
Comment by Peter Wu (Lekensteyn) - Thursday, 28 June 2012, 12:27 GMT
The upstream bug is possibly http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2363
Comment by Jiri Wiesner (jiriwiesner) - Friday, 29 June 2012, 15:16 GMT
With linux 3.4.4-2, I no longer experience any problems with wifi connectivity. I'm impressed by the speedy resolution in less than two weeks!
Comment by Kai Hendry (hendry) - Monday, 02 July 2012, 10:17 GMT
I think I see this problem.
iwlwifi 0000:03:00.0: ACTIVATE a non DRIVER active station

It says wlan0: authenticated, but I'm Access Point: Not-Associated and I can't get an IP.

Comment by Kai Hendry (hendry) - Monday, 02 July 2012, 10:23 GMT
Using the LTS kernel now makes my wireless work btw.
Comment by Peter Wu (Lekensteyn) - Monday, 02 July 2012, 10:27 GMT
Kai, that was exactly the issue that I experienced. The latest wireless testing tree solved it for me as can be seen in the upstream bug report. It'll probably be in kernel 3.6 unless it gets backported.
Comment by Kai Hendry (hendry) - Tuesday, 10 July 2012, 09:37 GMT
My wireless is working after a firmware upgrade to a ubnt.com router. =)
Comment by Kevin Murphy (kemurphy) - Tuesday, 10 July 2012, 09:44 GMT
Kai: That's not a possibility for some, like me.... The network I have the most trouble with is the one at my workplace.
Comment by Peter Wu (Lekensteyn) - Tuesday, 10 July 2012, 11:57 GMT
@Kai: maybe the changelog details of your fw can help the iwlwifi guys if this is not already fixed.

It is supposed to be fixed in the latest tree at http://git.kernel.org/?p=linux/kernel/git/iwlwifi/iwlwifi.git;a=summary which will likely hit 3.6 or a future stable backport to 3.5.
Comment by Greg (dolby) - Monday, 15 October 2012, 11:40 GMT
Is this fixed in 3.6.2?
Comment by Tobias Powalowski (tpowa) - Monday, 05 November 2012, 15:04 GMT
Status 3.6.6?
Comment by Peter Wu (Lekensteyn) - Monday, 05 November 2012, 15:12 GMT
I haven't seen the error from the OP in a while in 3.6. Looks fixed to me?

Loading...