iwlwifi connection problem

Bug #370236 reported by Antony Hussi
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Undecided
Unassigned

Bug Description

Ubuntu release 9.04 and kernel image 2.6.28-11.42
Problem is occuring during first bootup and sometimes during wakeup from suspend. Device is unable to connect wireless router and require series manual retry to connect wireless router.

Device:
  *-network
       description: Wireless interface
       product: PRO/Wireless 5100 AGN [Shiloh] Network Connection
       vendor: Intel Corporation
       physical id: 0
       bus info: pci@0000:04:00.0
       logical name: wmaster0
       version: 00
       serial: 00:22:fa:42:f6:18
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list logical ethernet physical wireless
       configuration: broadcast=yes driver=iwlagn ip=88.112.206.194 latency=0 module=iwlagn multicast=yes wireless=IEEE 802.11abgn

dmesg error
[26448.549049] iwlagn: Removing wrong key 1 0x410b
[26448.549172] ------------[ cut here ]------------
[26448.549177] WARNING: at /build/buildd/linux-2.6.28/drivers/net/wireless/iwlwifi/iwl-sta.c:708 iwl_set_dynamic_key+0x1aa/0x1b0 [iwlcore]()
[26448.549181] no space for new kewModules linked in: nvidia(P) aes_x86_64 aes_generic ppdev bridge stp bnep input_polldev dm_crypt lp parport joydev snd_hda_intel snd_pcm_oss arc4 snd_mixer_oss ecb snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi iwlagn iwlcore snd_rawmidi led_class snd_seq_midi_event snd_seq mac80211 psmouse uvcvideo snd_timer snd_seq_device pcspkr video serio_raw compat_ioctl32 videodev v4l1_compat snd soundcore snd_page_alloc iTCO_wdt iTCO_vendor_support cfg80211 sdhci_pci sdhci output btusb intel_agp usbhid tg3 fbcon tileblit font bitblit softcursor [last unloaded: nvidia]
[26448.549257] Pid: 10, comm: events/1 Tainted: P W 2.6.28-11-generic #42-Ubuntu
[26448.549261] Call Trace:
[26448.549273] [<ffffffff80250927>] warn_slowpath+0xb7/0xf0
[26448.549280] [<ffffffff802fca21>] ? alloc_inode+0x1f1/0x220
[26448.549285] [<ffffffff802fca21>] ? alloc_inode+0x1f1/0x220
[26448.549292] [<ffffffff8031765e>] ? inotify_d_instantiate+0x4e/0x60
[26448.549305] [<ffffffffa0ba52b0>] ? iwl4965_mac_set_key+0x0/0x160 [iwlagn]
[26448.549312] [<ffffffff803bff62>] ? debugfs_mknod+0xd2/0x130
[26448.549316] [<ffffffff802fb499>] ? dput+0xb9/0x190
[26448.549321] [<ffffffff803c0108>] ? debugfs_create_by_name+0x148/0x220
[26448.549328] [<ffffffff8022f669>] ? default_spin_lock_flags+0x9/0x10
[26448.549342] [<ffffffffa0b909da>] iwl_set_dynamic_key+0x1aa/0x1b0 [iwlcore]
[26448.549354] [<ffffffffa0ba53dc>] iwl4965_mac_set_key+0x12c/0x160 [iwlagn]
[26448.549381] [<ffffffffa0b2bd83>] ieee80211_key_enable_hw_accel+0x83/0x160 [mac80211]
[26448.549387] [<ffffffff803bfe85>] ? debugfs_remove+0x65/0x70
[26448.549409] [<ffffffffa0b2c120>] __ieee80211_key_todo+0x130/0x1b0 [mac80211]
[26448.549431] [<ffffffffa0b2c300>] ? key_todo+0x0/0x10 [mac80211]
[26448.549452] [<ffffffffa0b2c2e5>] ieee80211_key_todo+0x15/0x30 [mac80211]
[26448.549473] [<ffffffffa0b2c309>] key_todo+0x9/0x10 [mac80211]
[26448.549479] [<ffffffff8026430a>] run_workqueue+0xba/0x190
[26448.549486] [<ffffffff802645e7>] worker_thread+0xa7/0x120
[26448.549492] [<ffffffff80268930>] ? autoremove_wake_function+0x0/0x40
[26448.549497] [<ffffffff80264540>] ? worker_thread+0x0/0x120
[26448.549503] [<ffffffff802684c9>] kthread+0x49/0x90
[26448.549509] [<ffffffff80213979>] child_rip+0xa/0x11
[26448.549515] [<ffffffff80268480>] ? kthread+0x0/0x90
[26448.549520] [<ffffffff8021396f>] ? child_rip+0x0/0x11
[26448.549523] ---[ end trace 7052151cbb8cfea8 ]---

Revision history for this message
deFINE (define) wrote :

I've got the very same problem.

Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.
Is this bug reproducible with the latest Lucid packages ?
Thanks in advance.

Changed in ubuntu:
status: New → Incomplete
Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

 Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage .

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://help.ubuntu.com/community/ReportingBugs.

Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in ubuntu:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.