Bug#628444: iwlagn - MAC is in deep sleep, cannot restore wifi operation
Hi Juha, Mar 22 20:13:47 rigel kernel: [1259943.614216] iwlwifi :03:00.0: RF_KILL bit toggled to disable radio. Mar 22 20:13:47 rigel kernel: [1259943.614350] iwlwifi :03:00.0: Not sending command - RF KILL [MV] These are not technically error messages, and we had a patch fixing these error messages in the recent past. What kernel version are you running? Mar 22 20:13:47 rigel kernel: [1259943.624242] ieee80211 phy0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-5) [MV] This could potentially be an issue -- we'll look into this. After switching the radios back on, I get Mar 22 20:14:22 rigel kernel: [1259978.719860] iwlwifi :03:00.0: RF_KILL bit toggled to enable radio. but *absolutely* *nothing* *else*. No RF LED, nothing. [MV] Ouch. This is likely also a bug in mac80211/driver...can you file a separate bug for this on the intel linux wireless bugzilla: http://bugzilla.intellinuxwireless.org/; so we can have someone look at it? Thanks, Meenakshi
Bug#628444: iwlagn - MAC is in deep sleep, cannot restore wifi operation
Hi, Dafydd Harries wrote: I've been seeing similar problems with my Intel Corporation Centrino Ultimate-N 6300. Like others, the problems seemed to start around 2.6.39. Odd. What kernel did you use before then? (/var/log/dpkg.log might tell.) Like othes, the card flakes out a day or two after booting, and a reboot always fixes the problem. Occasionally it stays working for longer. [MV] what platform are you using? And does your problem appear after a system hibernate? Like others, I've added RAM. But as far as I can recall the upgrade happened well before any poblems started appearing. Interesting and useful. Any ASPM settings are at their default. [MV] Can you try pcie_aspm=off during boot? Meenakshi, will the patch you mentioned be applied in 3.3? [MV] Yes...it should be applied to 3.3 as well (it is also slated to be backported to stable kernels); but it is a fairly recent fix, so it will take some time before it gets accepted to the other Linux trees. Below is a syslog excerpt from around the time of failue. It seems to support Meenakshi's suggestion that it's related to the queue getting stuck. [...] iwlwifi :02:00.0: Queue 4 stuck for 2000 ms. [MV] Any idea what happened before this? Did you see any error sending host commands? Did you resume from a hibernate? Can you send me the log? Thanks for your patience, Meenakshi -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4595b4d22ab93c4fabba84aad5aa37fd0dc...@orsmsx103.amr.corp.intel.com
Bug#628444: iwlagn - MAC is in deep sleep, cannot restore wifi operation
Hi, what platform are you using? And does your problem appear after a system hibernate? Linux nia 3.2.0-2-amd64 #1 SMP Sun Mar 4 22:48:17 UTC 2012 x86_64 GNU/Linux The system is Debian unstable. Maybe lspci -vvnn output (as an attachment) and dmesg output from booting if you have it could help to pin down the setup a little more. (If I understand correctly, Meenakshi is dreaming of a reliable reproduction recipe. ;-)) [MV] That's correct! :-) Meenakshi -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4595b4d22ab93c4fabba84aad5aa37fd0dc...@orsmsx103.amr.corp.intel.com
Bug#628444: iwlagn - MAC is in deep sleep, cannot restore wifi operation
Hi Dafydd, I've been seeing similar problems with my Intel Corporation Centrino Ultimate-N 6300. Like others, the problems seemed to start around 2.6.39. [MV] Hmm...this is interesting. Can you load the iwlwifi module with bt_coex_active=0 and see if it changes anything? One of the patches that went in between 2.6.38 and 2.6.39 changed the behaviour of coexistence with Bluetooth devices on some platforms, and caused users some grief; although their symptoms were different. The module parameter I mention above solved this problem for them. Odd. What kernel did you use before then? (/var/log/dpkg.log might tell.) Sadly, my dpkg.log only goes back to 3.0, which was installed last July (!). I could try installing e.g. 2.6.32 from snapshot.debian.org if other things don't help. But that would be a lot of patches to bisect, especially when reproduction iterations are so long... [MV] No...let's leave bisecting as the last option for this problem. [MV] what platform are you using? And does your problem appear after a system hibernate? Linux nia 3.2.0-2-amd64 #1 SMP Sun Mar 4 22:48:17 UTC 2012 x86_64 GNU/Linux [MV] Oh...I was asking about hardware...who is the manufacturer of your system? I don't use hibernation. I do suspend regularly, but I haven't noticed any correlation with suspend/resume. [MV] Interesting as well. [MV] Any idea what happened before this? Did you see any error sending host commands? Did you resume from a hibernate? Can you send me the log? I haven't noticed any pattern. The first thing that happens is that the NetworkManager applet seems to be trying to reconnect to the wireless. [MV] Hmm...the queue stuck patch could potentially help here, but only provided that a queue was stuck prior to the reconnect. Your log doesn't run that far back, so I'm not able to say. :-) Thanks, Meenakshi -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4595b4d22ab93c4fabba84aad5aa37fd0dc...@orsmsx103.amr.corp.intel.com
Bug#628444: Info received (iwlagn - MAC is in deep sleep, cannot restore wifi operation)
Hi Shannon and others, First up, my sincere apologies for not responding earlier. I've been swamped with other work, and have had a chance to look at this only now. I just got caught up with the email thread, and it appears that you're seeing a problem with the following configuration most frequently: 1) Enable power saving in the driver (power_save) 2) Enabling 11n 3) Leaving aspm at its default 4) wd_disable=0 (the default) Our devices are known to have issues with being in L1 (a PCIe sleep state), and so we use L0S by default - this is a lower latency and higher power state. We've also not been able to reproduce the MAC in deep sleep problem at our end, so not sure at the moment what is causing it. However, there was one issue with queue-stuck detection that we found and fixed very recently. The patch is available in the wireless-next tree, and will likely improve the situation if a stuck queue was the initial cause of your problem. You can get the source here: http://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-next.git And the patch I'm talking about is this: git.kernel.org/?p=linux/kernel/git/linville/wireless-next.git;a=commit;h=342bbf3fee2fa9a18147e74b2e3c4229a4564912 My suggestion is to load the module with power_save=0, wd_disable=1. Enabling 11n should not be a problem, but if it is, then please let us know. You should not need to use the wd_disable=1 in the upcoming versions of the kernel, but for now, I'd suggest using it. Since your problem seems to be reducing significantly by using pcie_aspm=off, I would appreciate it much if you could tell us what the behaviour is with all other parameters being the same (power_save=0, wd_disable=1), and just toggling the state of this variable. We'll try to reproduce the suspend/hibernate/resume issue in-house and let you know if we were able to reproduce the problem at our end. If not, we'd like you to try out a newer WiFi card; as the 5100 is a fairly old device, and will likely not get any firmware updates (if it is some weird firmware/driver combo that produced the PCIe error). Thanks! Meenakshi Venkataraman
Bug#641424: iwlagn: fails to reconnect to WPA2-enterprise (Reason: 23)
Hi Miguel, I have already built kernel 3.0.0-1-amd64 with the required debugging symbols. I've rebooted into the debug kernel, and loaded the iwlagn module with debugging symbols enabled. Or so I think. [MV] I don't see much iwlagn debugging information in the log you sent me. Can you please load the iwlagn module with the following parameters: modprobe iwlagn debug=0x43FFF Thanks, Meenakshi -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/c5a7fb31fd9aea42b600bdc3c74f8e0014ad3...@orsmsx511.amr.corp.intel.com
Bug#641424: iwlagn: fails to reconnect to WPA2-enterprise (Reason: 23)
Hi Miguel, 1) Enable debugging for the iwlwifi driver like so: I've tried to do that after installing linux-image-3.0.0-1-amd64-dbg, but modprobing with the debug option failed. Is there a lazy Debian way to get the debug symbols without going all out compiling? Check the kernel config file for the above kernel, and make sure that the following two options are set for the iwlwifi driver. # # Debugging Options # CONFIG_IWLWIFI_DEBUG=y CONFIG_IWLWIFI_DEBUGFS=y And that there is debugging for mac80211 as well. CONFIG_MAC80211_DEBUGFS=y CONFIG_MAC80211_DEBUG_MENU=y CONFIG_MAC80211_NOINLINE=y CONFIG_MAC80211_VERBOSE_DEBUG=y CONFIG_MAC80211_HT_DEBUG=y CONFIG_MAC80211_TKIP_DEBUG=y CONFIG_MAC80211_IBSS_DEBUG=y CONFIG_MAC80211_VERBOSE_PS_DEBUG=y CONFIG_MAC80211_DEBUG_COUNTERS=y CONFIG_MAC80211_DRIVER_API_TRACER=y If they're not set - you'll have to resort to compiling the kernel with debugging enabled. 2) A wireless sniffer log would also be useful (not sure you're in a position to gather this log). I fear I have no experience with sniffers. Also, I wouldn't like to do anything that could be interpreted as computer misuse, since this is my workplace after all. Should this be okay, I'd need some guidance. Don't worry about this for now. Try to get debugging information for the iwlwifi driver, mac80211, and network-manager (if possible). Also, what kernel version is your Ubuntu 10.10 system using? Thanks, Meenakshi
Bug#641424: iwlagn: fails to reconnect to WPA2-enterprise (Reason: 23)
Thanks for the reason code info, Ben, I meant that we could continue on the Debian bugzilla. Or, you can post it to: http://bugzilla.intellinuxwireless.org/ -- the bugzilla for the iwlwifi driver + currently supported devices. Thanks, meenakshi -Original Message- From: Ben Hutchings [mailto:b...@decadent.org.uk] Sent: Tuesday, September 13, 2011 4:41 PM To: Venkataraman, Meenakshi Cc: Miguel Martinez; 641...@bugs.debian.org; linux-wireless Subject: RE: Bug#641424: iwlagn: fails to reconnect to WPA2-enterprise (Reason: 23) On Tue, 2011-09-13 at 16:33 -0700, Venkataraman, Meenakshi wrote: Hi Miguel, It looks like the AP you're connected to at the University is a Cisco AP. I'm not sure what reason code 23 is, will need to research it some. WLAN_REASON_IEEE8021X_FAILED = 23, In the meantime, can you do the following so we can see what's going on in the iwlwifi driver: 1) Enable debugging for the iwlwifi driver like so: modprobe iwlagn debug=0x47fff You'll need to enable debugging for iwlwifi while building the kernel. 2) A wireless sniffer log would also be useful (not sure you're in a position to gather this log). Please send me (only) the log. We can take this to bugzilla as well. [...] If you mean bugzilla.kernel.org, that is currently down along with much of the kernel.org infrastructure. Ben. -- Ben Hutchings All extremists should be taken out and shot.
Bug#641424: iwlagn: fails to reconnect to WPA2-enterprise (Reason: 23)
Hi Miguel,
It looks like the AP you're connected to at the University is a Cisco AP. I'm
not sure what reason code 23 is, will need to research it some.
In the meantime, can you do the following so we can see what's going on in the
iwlwifi driver:
1) Enable debugging for the iwlwifi driver like so:
modprobe iwlagn debug=0x47fff
You'll need to enable debugging for iwlwifi while building the kernel.
2) A wireless sniffer log would also be useful (not sure you're in a position
to gather this log).
Please send me (only) the log. We can take this to bugzilla as well.
Thanks,
Meenakshi
-Original Message-
From: linux-wireless-ow...@vger.kernel.org [mailto:linux-wireless-
ow...@vger.kernel.org] On Behalf Of Ben Hutchings
Sent: Tuesday, September 13, 2011 3:29 PM
To: Miguel Martinez
Cc: 641...@bugs.debian.org; linux-wireless
Subject: Re: Bug#641424: iwlagn: fails to reconnect to WPA2-enterprise
(Reason: 23)
[The previous message is logged at http://bugs.debian.org/641424.]
On Tue, 2011-09-13 at 12:15 +0100, Miguel Martinez wrote:
Package: linux-2.6
Version: 3.0.0-3
Severity: normal
Dear Maintainer,
My laptop (T400, Intel WiFi Link 5300) is connected at university
using Eduroam, an WPA2-enterprise network. After configuring the
interface (either KDE or Gnome2 versions of network-manager), a
connection will be established. After a while, however, the connection
will be dropped (local reason 3), and will not be reestablished
(Reason: 23) after an indefinite number of attempts. Apparently, nm is
not able to renew the IP.
From the dmesg output, it seems the wifi card is struggling to decide
which of two AP it should connect to. Extract from dmesg right after
the first disconnect:
I think that's a symptom, not a cause of the failure.
[ 817.555025] wlan0: deauthenticating from 00:16:9d:7c:97:02 by local
choice (reason=3) [ 817.565665] cfg80211: Calling CRDA to update
world regulatory domain [ 817.575513] wlan0: authenticate with
00:16:c7:71:a1:42 (try 1) [ 817.578148] wlan0: authenticated [
817.579185] cfg80211: World regulatory domain updated:
[ 817.579192] cfg80211: (start_freq - end_freq @ bandwidth),
(max_antenna_gain, max_eirp)
[ 817.579200] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300
mBi, 2000 mBm)
[ 817.579209] cfg80211: (2457000 KHz - 2482000 KHz @ 2 KHz), (300
mBi, 2000 mBm)
[ 817.579216] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300
mBi, 2000 mBm)
[ 817.579224] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300
mBi, 2000 mBm)
[ 817.579232] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300
mBi, 2000 mBm)
[ 817.580656] wlan0: associate with 00:16:c7:71:a1:42 (try 1) [
817.583046] wlan0: RX AssocResp from 00:16:c7:71:a1:42 (capab=0x431
status=0 aid=78) [ 817.583049] wlan0: associated [ 818.626062]
wlan0: deauthenticated from 00:16:c7:71:a1:42 (Reason: 23) [
818.634705] cfg80211: Calling CRDA to update world regulatory domain [
818.644952] cfg80211: World regulatory domain updated:
[ 818.644960] cfg80211: (start_freq - end_freq @ bandwidth),
(max_antenna_gain, max_eirp)
[ 818.644969] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300
mBi, 2000 mBm)
[ 818.644977] cfg80211: (2457000 KHz - 2482000 KHz @ 2 KHz), (300
mBi, 2000 mBm)
[ 818.644985] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300
mBi, 2000 mBm)
[ 818.644993] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300
mBi, 2000 mBm)
[ 818.645000] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300
mBi, 2000 mBm)
[ 821.971502] wlan0: authenticate with 00:16:9d:7c:97:02 (try 1) [
821.974151] wlan0: authenticated [ 821.977578] wlan0: associate with
00:16:9d:7c:97:02 (try 1) [ 821.979659] wlan0: RX AssocResp from
00:16:9d:7c:97:02 (capab=0x431 status=0 aid=205) [ 821.979668] wlan0:
associated [ 823.018591] wlan0: deauthenticated from
00:16:9d:7c:97:02 (Reason: 23)
Disabling and reenabling the network helps to reconnect to Eduroam,
but will not last for long, repeating the pattern described above.
I first thought it was an issue with knetwork-manager in Wheezy's KDE
[1], so I upgraded to testing.
'wheezy' is the testing suite at the moment. Did you start from an earlier
installation of testing, or from stable ('squeeze')?
The issue remains in all kernels I've
tried. I've also tried installing Gnome 2.32 from testing and using
nm-applet.
Following suggestions in some bug reports [2], I've tried disabling
11n and/or disabling power management (seems to be off in any case),
but it doesn't help. This is all more puzzling, since my Ubuntu 10.10
partition has no such problems with Eduroam. I should note that Ubuntu
10.10 does disable 11n, but it's reenabled for 11.04 and later. I will
try OpenSUSE
11.4 from a live USB to see if the problem also exists there.
Finally, it should be mentioned that WPA2 at home works without
issues, and with 11n
