Warning from wireless intel 4965 : no space for a new key

Bug #594172 reported by Graziano
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

[ 5911.870130] WARNING: at /build/buildd/linux-2.6.35/drivers/net/wireless/iwlwifi/iwl-sta.c:952 iwl_set_tkip_dynamic_key_info+0x161/0x170 [iwlcore]()
[ 5911.870135] Hardware name: N/A
[ 5911.870138] no space for a new key
[ 5911.870140] Modules linked in: cryptd aes_x86_64 aes_generic binfmt_misc rfcomm sco bridge stp ppdev bnep l2cap nvidia(P) snd_hda_codec_si3054 arc4 snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_seq_midi psmouse snd_rawmidi snd_seq_midi_event iwlagn iwlcore vga16fb btusb sdhci_pci sdhci joydev serio_raw led_class usbhid hid snd_seq vgastate uvcvideo lp parport video snd_timer snd_seq_device intel_agp mac80211 videodev cfg80211 snd soundcore bluetooth snd_page_alloc output v4l1_compat v4l2_compat_ioctl32 ohci1394 ieee1394 tg3
[ 5911.870207] Pid: 9, comm: events/0 Tainted: P W 2.6.35-2-generic #3-Ubuntu
[ 5911.870211] Call Trace:
[ 5911.870225] [<ffffffff8105e68f>] warn_slowpath_common+0x7f/0xc0
[ 5911.870228] [<ffffffff8105e786>] warn_slowpath_fmt+0x46/0x50
[ 5911.870232] [<ffffffff81034d89>] ? default_spin_lock_flags+0x9/0x10
[ 5911.870238] [<ffffffffa01dd3e1>] iwl_set_tkip_dynamic_key_info+0x161/0x170 [iwlcore]
[ 5911.870245] [<ffffffffa01de318>] iwl_set_dynamic_key+0x88/0xb0 [iwlcore]
[ 5911.870251] [<ffffffffa02370f7>] iwl_mac_set_key+0x157/0x180 [iwlagn]
[ 5911.870265] [<ffffffffa0160bba>] ieee80211_key_enable_hw_accel+0x8a/0x150 [mac80211]
[ 5911.870274] [<ffffffffa0160f30>] __ieee80211_key_todo+0x140/0x1f0 [mac80211]
[ 5911.870283] [<ffffffffa01610d0>] ? key_todo+0x0/0x10 [mac80211]
[ 5911.870291] [<ffffffffa01610ba>] ieee80211_key_todo+0x1a/0x30 [mac80211]
[ 5911.870300] [<ffffffffa01610de>] key_todo+0xe/0x10 [mac80211]
[ 5911.870303] [<ffffffff81078695>] run_workqueue+0xc5/0x1a0
[ 5911.870306] [<ffffffff81078813>] worker_thread+0xa3/0x110
[ 5911.870309] [<ffffffff8107d510>] ? autoremove_wake_function+0x0/0x40
[ 5911.870312] [<ffffffff81078770>] ? worker_thread+0x0/0x110
[ 5911.870314] [<ffffffff8107cfb6>] kthread+0x96/0xa0
[ 5911.870318] [<ffffffff8100aee4>] kernel_thread_helper+0x4/0x10
[ 5911.870320] [<ffffffff8107cf20>] ? kthread+0x0/0xa0
[ 5911.870323] [<ffffffff8100aee0>] ? kernel_thread_helper+0x0/0x10
[ 5911.870325] ---[ end trace 340be0a4ed0c507b ]---

ProblemType: KernelOops
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-2-generic 2.6.35-2.3
Regression: No
Reproducible: No
ProcVersionSignature: Ubuntu 2.6.35-2.3-generic 2.6.35-rc2
Uname: Linux 2.6.35-2-generic x86_64
NonfreeKernelModules: nvidia
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: amd64
Date: Mon Jun 14 16:10:32 2010
Failure: oops
SourcePackage: linux
Title: WARNING: at /build/buildd/linux-2.6.35/drivers/net/wireless/iwlwifi/iwl-sta.c:952 iwl_set_tkip_dynamic_key_info+0x161/0x170 [iwlcore]()

Revision history for this message
Graziano (graziano-giuliani-gmail) wrote :
tags: added: kj-triage
Revision history for this message
Graziano (graziano-giuliani-gmail) wrote :

This kernel warning, without being a real oops, is very annoying as it pops up frequently triggering the apport reporting tool.
It seemed to disappear using 2.6.35-3 up to 2.6.35-6, but it is still here as of 2.6.35-7 with at least two oops per day.

Revision history for this message
Kim Nguyễn (kim.nguyen) wrote :

Hi,

it seems that this bug has been reported in the upstream bugzilla:
https://bugzilla.kernel.org/show_bug.cgi?id=16232

A patch is attached to the bugzilla entry and has been submitted upstream but it does not seem
to have been merged yet.
http://article.gmane.org/gmane.linux.kernel.wireless.general/52893

Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

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

apport-collect 594172

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.

Changed in linux (Ubuntu):
status: New → Incomplete
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.