Kernel 3.0 wireless Warning bug

[Bruno Finger]

I'm using Ubuntu 11.10 64-bits.
My hardware is an Acer Aspire 5630 notebook. Wi-fi card has 802.11 B/G support (no N), and is connected to a router running a G+N network. All other devices can connect to it with no problem, and the same notebook also have no problems in windows with the network.

The following problem keeps occurring repeatedly:

The notebook can connect to the wireless network in G mode and browse the web without any problems, but at certain point (can be after 5 minutes of use, or also 2 hours of use, really random) it disconnects and can't connect to it anymore. The window to enter network password pops-up and then I enter the password and still it can't connect (same window pops-up again). It keeps going like this also for a random time (5min.~2hours) until it suddenly can connect again. Restarting seems to solve the not able to connect problem but doesn't keep it from occurring again. Dmesg shows the following trace:

~~~~~~~~~~~~~~~~

[ 233.380172] ieee80211 phy0: wlan0: No probe response from AP 00:1e:ab:05:7a:72 after 500ms, disconnecting.
[ 233.404351] cfg80211: All devices are disconnected, going to restore regulatory settings
[ 233.404362] cfg80211: Restoring regulatory settings
[ 233.404372] cfg80211: Calling CRDA to update world regulatory domain
[ 233.411231] cfg80211: Ignoring regulatory request Set by core since the driver uses its own custom regulatory domain
[ 233.411239] cfg80211: World regulatory domain updated:
[ 233.411243] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 233.411250] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 233.411256] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 233.411262] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 233.411267] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 233.411273] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 234.715144] wlan0: authenticate with 00:1e:ab:05:7a:72 (try 1)
[ 234.724381] wlan0: authenticated
[ 234.725847] wlan0: associate with 00:1e:ab:05:7a:72 (try 1)
[ 234.924165] wlan0: associate with 00:1e:ab:05:7a:72 (try 2)
[ 235.124153] wlan0: associate with 00:1e:ab:05:7a:72 (try 3)
[ 235.324181] wlan0: association with 00:1e:ab:05:7a:72 timed out
[ 241.550941] wlan0: direct probe to 00:1e:ab:05:7a:72 (try 1/3)
[ 241.748185] wlan0: direct probe to 00:1e:ab:05:7a:72 (try 2/3)
[ 241.948167] wlan0: direct probe to 00:1e:ab:05:7a:72 (try 3/3)
[ 242.148063] wlan0: direct probe to 00:1e:ab:05:7a:72 timed out
[ 242.148157] ------------[ cut here ]------------
[ 242.148198] WARNING: at /build/buildd/linux-3.0.0/net/wireless/mlme.c:307 __cfg80211_auth_remove+0x70/0xd0 [cfg80211]()
[ 242.148204] Hardware name: Aspire 5630
[ 242.148207] Modules linked in: snd_hrtimer bnep rfcomm bluetooth parport_pc ppdev binfmt_misc nls_iso8859_1 nls_cp437 vfat fat arc4 snd_hda_codec_realtek iwl3945 i915 gspca_vc032x gspca_main videodev snd_hda_intel snd_hda_codec iwl_legacy usbhid v4l2_compat_ioctl32 hid snd_hwdep snd_pcm mac80211 snd_seq_midi drm_kms_helper pcmcia joydev snd_rawmidi snd_seq_midi_event yenta_socket snd_seq drm snd_timer pcmcia_rsrc snd_seq_device psmouse serio_raw pcmcia_core cfg80211 snd i2c_algo_bit soundcore snd_page_alloc wmi video lp parport usb_storage uas sdhci_pci sdhci b44 ssb
[ 242.148293] Pid: 14, comm: kworker/u:1 Not tainted 3.0.0-13-generic #22-Ubuntu
[ 242.148298] Call Trace:
[ 242.148311] [<ffffffff8105e8af>] warn_slowpath_common+0x7f/0xc0
[ 242.148319] [<ffffffff8105e90a>] warn_slowpath_null+0x1a/0x20
[ 242.148337] [<ffffffffa00a74b0>] __cfg80211_auth_remove+0x70/0xd0 [cfg80211]
[ 242.148356] [<ffffffffa00a75a1>] cfg80211_send_auth_timeout+0x71/0xd0 [cfg80211]
[ 242.148381] [<ffffffffa01a0407>] ? ieee80211_hw_config+0x117/0x220 [mac80211]
[ 242.148406] [<ffffffffa01acee4>] ieee80211_probe_auth_done+0xa4/0xb0 [mac80211]
[ 242.148431] [<ffffffffa01b07c6>] ieee80211_work_work+0x1e6/0x640 [mac80211]
[ 242.148456] [<ffffffffa01b05e0>] ? ieee80211_work_rx_queued_mgmt+0x2d0/0x2d0 [mac80211]
[ 242.148466] [<ffffffff8107c04a>] process_one_work+0x11a/0x480
[ 242.148472] [<ffffffff8107cdf5>] worker_thread+0x165/0x370
[ 242.148479] [<ffffffff8107cc90>] ? manage_workers.isra.30+0x130/0x130
[ 242.148486] [<ffffffff8108129c>] kthread+0x8c/0xa0
[ 242.148494] [<ffffffff815f38e4>] kernel_thread_helper+0x4/0x10
[ 242.148501] [<ffffffff81081210>] ? flush_kthread_worker+0xa0/0xa0
[ 242.148508] [<ffffffff815f38e0>] ? gs_change+0x13/0x13
[ 242.148512] ---[ end trace 8ff7b81e7e1c03c8 ]---
[ 248.371800] wlan0: direct probe to 00:1e:ab:05:7a:72 (try 1/3)
[ 248.568133] wlan0: direct probe to 00:1e:ab:05:7a:72 (try 2/3)
[ 248.768075] wlan0: direct probe to 00:1e:ab:05:7a:72 (try 3/3)
[ 248.968171] wlan0: direct probe to 00:1e:ab:05:7a:72 timed out

~~~~~~~~~~~~~~~~~~~~~~

bruno@bruno-laptop ~ $ uname -a
Linux bruno-laptop 3.0.0-13-generic #22-Ubuntu SMP Wed Nov 2 13:27:26 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux

~~~~~~~~~~~~~~~~~~~~~~

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/975975/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Bruno Finger (brunofin)]

Set affected package to linux-image-generic.

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 975975

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.4kernel[1] (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-rc2-precise/

[Bruno Finger (brunofin)]

Upstream kernel seems to have fixed the problem of disconnections (although all of those cgf80211 messages still appears in dmesg). Should I still mark as "Confirmed"?

[penalvch (penalvch)]

brunofin, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

[Bruno Finger (brunofin)]

This problem is not occurring anymore since a long time, if I remember well it was fixed after upgrading the system to a newer version of Ubuntu, probably 12.04.

[penalvch (penalvch)]

burnofin, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/975975/comments/7 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

[Charkel (charkel)]

I have this problem! Cannot use WiFi