After the upgrade wireless connection often don't get established at all and if it takes several retries before it works. Downgrade to 3.1 makes this go away again. Reproducible: Always
lspci 00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 02) 00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02) 00:19.0 Ethernet controller: Intel Corporation 82577LM Gigabit Network Connection (rev 05) 00:1a.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05) 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05) 00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 05) 00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 2 (rev 05) 00:1c.2 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 3 (rev 05) 00:1c.3 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 4 (rev 05) 00:1d.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a5) 00:1f.0 ISA bridge: Intel Corporation 5 Series/3400 Series Chipset LPC Interface Controller (rev 05) 00:1f.2 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller [RAID mode] (rev 05) 00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 05) 00:1f.6 Signal processing controller: Intel Corporation 5 Series/3400 Series Chipset Thermal Subsystem (rev 05) 02:00.0 Network controller: Intel Corporation Centrino Advanced-N 6200 (rev 35) 03:00.0 SD Host controller: Ricoh Co Ltd MMC/SD Host Controller (rev 01) 3f:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers (rev 02) 3f:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 02) 3f:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 02) 3f:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 02) 3f:02.2 Host bridge: Intel Corporation Core Processor Reserved (rev 02) 3f:02.3 Host bridge: Intel Corporation Core Processor Reserved (rev 02)
one more important thing, even once connected the connection is very flacky, reconnects often and the traffic is very very slow. reboot in old kernel and every thing is fine!
Created attachment 323656 [details] messages file
I use net-wireless/wpa_supplicant-1.0 because the stable version didn't work with roaming wifi. sys-firmware/iwl6000-ucode-9.221.4.1
I actually suffer problems with 3.1 on this now too, albeit the connection works fine, the connection is very flacky on some specific networks getting errors like this in the log Sep 13 15:45:50 mkopp kernel: iwlagn 0000:02:00.0: Queue 2 stuck for 2000 ms. Sep 13 15:45:50 mkopp kernel: iwlagn 0000:02:00.0: Queue 2 stuck for 2000 ms. Sep 13 15:45:53 mkopp kernel: iwlagn 0000:02:00.0: Queue 2 stuck for 2000 ms. Sep 13 15:45:53 mkopp kernel: iwlagn 0000:02:00.0: On demand firmware reload Sep 13 15:45:53 mkopp kernel: ieee80211 phy0: Hardware restart was requested Sep 13 15:45:53 mkopp kernel: iwlagn 0000:02:00.0: L1 Enabled; Disabling L0S Sep 13 15:45:53 mkopp kernel: iwlagn 0000:02:00.0: Radio type=0x1-0x3-0x1 Sep 13 15:46:00 mkopp kernel: iwlagn 0000:02:00.0: Queue 2 stuck for 2000 ms. Sep 13 15:46:00 mkopp kernel: iwlagn 0000:02:00.0: On demand firmware reload Sep 13 15:46:00 mkopp kernel: ieee80211 phy0: Hardware restart was requested Sep 13 15:46:00 mkopp kernel: iwlagn 0000:02:00.0: L1 Enabled; Disabling L0S Sep 13 15:46:00 mkopp kernel: iwlagn 0000:02:00.0: Radio type=0x1-0x3-0x1 Sep 13 15:46:00 mkopp kernel: iwlagn 0000:02:00.0: Queue 2 stuck for 2000 ms. Sep 13 15:46:03 mkopp kernel: iwlagn 0000:02:00.0: Queue 2 stuck for 2000 ms. Sep 13 15:46:03 mkopp kernel: iwlagn 0000:02:00.0: Queue 2 stuck for 2000 ms. Sep 13 15:46:08 mkopp kernel: iwlagn 0000:02:00.0: Queue 2 stuck for 2000 ms. Sep 13 15:46:08 mkopp kernel: iwlagn 0000:02:00.0: On demand firmware reload Sep 13 15:46:08 mkopp kernel: ieee80211 phy0: Hardware restart was requested Sep 13 15:46:08 mkopp kernel: iwlagn 0000:02:00.0: L1 Enabled; Disabling L0S Sep 13 15:46:08 mkopp kernel: iwlagn 0000:02:00.0: Radio type=0x1-0x3-0x1 Sep 13 15:46:09 mkopp kernel: iwlagn 0000:02:00.0: Queue 2 stuck for 2000 ms. Sep 13 15:46:09 mkopp kernel: iwlagn 0000:02:00.0: Queue 2 stuck for 2000 ms. Sep 13 15:46:10 mkopp kernel: iwlagn 0000:02:00.0: Queue 2 stuck for 2000 ms. Sep 13 15:46:10 mkopp kernel: iwlagn 0000:02:00.0: Queue 2 stuck for 2000 ms. Sep 13 15:46:37 mkopp kernel: iwlagn 0000:02:00.0: Tx aggregation enabled on ra = 98:fc:11:48:ca:12 tid = 0 Sep 13 15:46:59 mkopp kernel: iwlagn 0000:02:00.0: Queue 10 stuck for 2000 ms. Sep 13 15:46:59 mkopp kernel: iwlagn 0000:02:00.0: On demand firmware reload Sep 13 15:46:59 mkopp kernel: ieee80211 phy0: Hardware restart was requested Sep 13 15:46:59 mkopp kernel: iwlagn 0000:02:00.0: L1 Enabled; Disabling L0S Sep 13 15:46:59 mkopp kernel: iwlagn 0000:02:00.0: Radio type=0x1-0x3-0x1 Sep 13 15:47:00 mkopp kernel: iwlagn 0000:02:00.0: Stopping AGG while state not ON or starting Sep 13 15:47:00 mkopp kernel: iwlagn 0000:02:00.0: queue number out of range: 0, must be 10 to 19 Sep 13 15:47:02 mkopp kernel: iwlagn 0000:02:00.0: Queue 2 stuck for 2000 ms.
Uhm can kernel team look into this? Because I seriously doubt that the firmware by itself is at fault, and I have no clue about the driver.
Can you test with vanilla sources 3.5.4 or later (if available) and tell me if anything gets better?
Hi, The best I can get right now is 3.5.3, and I found that this problem is worse the more APs I see in the same network, meaning the more roaming potentially is going on. In my current system it connects after the second or third attempt (there are 3 APs availabile) it however does disconnect and reconnect several times an hour. I will test this with 3.5.4 as soon as its available in my distro (which is gentoo so it shouldn't take long for vanilla to be there).
Any report here?
oh sorry, almost forgot about this. i am back on 3.3.8, as long as there aren't too many AP's with the same SSID it works nearly fine disconnects now and again. Didn't have a chance to test 3.5 yet
It's been awhile here. Please comment if there are still issues with the latest kernels.
