Comment 20 for bug 1034740

Revision history for this message
JD Rogers (rogersjd) wrote :

I know this bug is old, but I think I'm having similar problems, and I would love to make some progress on this.

My problem is a little different, so I may need to file a new bug (Christopher?). While Alexander's bug appears to connect and then slow down eventually failing with packet loss, my problem is almost the opposite. If I can connect, it seems to work fine indefinitely, but initial connections (after suspend, or right after a reboot) only occasionally works. Sometimes, if I wait long enough the connection starts working after several minutes, sometimes it works if I turn off wireless and turn it back on, but often it just never works.

My intel wireless "Intel Corporation Centrino Ultimate-N 6300 (rev 3e)" works fine on 802.11g networks. When using 802.11n, not so much.

The worst part is that I am at a loss on what is actually failing. iwconfig reports that I am associated. No obvious errors in dmesg or syslog. Yet if I try to ping my access point, I get "network is unreachable".

# dmesg |tail
[101704.467324] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[101704.474053] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[101704.621429] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[101704.717787] wlan0: authenticate with xx:xx:xx:xx:xx:xx
[101704.780532] wlan0: send auth to xx:xx:xx:xx:xx:xx (try 1/3)
[101704.793246] wlan0: authenticated
[101704.797390] wlan0: associate with xx:xx:xx:xx:xx:xx (try 1/3)
[101704.798226] wlan0: RX AssocResp from xx:xx:xx:xx:xx:xx (capab=0x1011 status=0 aid=1)
[101704.802300] wlan0: associated
[101704.802347] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

If I load the iwlwifi module using "11n_disable=1" everything works fine, but then I don't get 802.11n speed. The problem exists on my home router and on a commercial router at work.

# uname -a
Linux zem 3.11.0-15-generic #25-Ubuntu SMP Thu Jan 30 17:22:01 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux