From: Maxim Levitsky <maximlevitsky@gmail.com>
To: reinette chatre <reinette.chatre@intel.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
iwlwifi maling list <ipw3945-devel@lists.sourceforge.net>
Subject: Re: A warning in latest -git 2.6.30-rc1
Date: Wed, 15 Apr 2009 03:48:11 +0300 [thread overview]
Message-ID: <1239756491.8954.10.camel@maxim-laptop> (raw)
In-Reply-To: <1239638705.10251.8.camel@rc-desk>
On Mon, 2009-04-13 at 09:05 -0700, reinette chatre wrote:
> Hi Maxim,
>
> On Sun, 2009-04-12 at 15:43 -0700, Maxim Levitsky wrote:
> > I have just noticed this, seems to be harmless, everything works fine:
> >
> >
> > > Apr 13 00:35:22 maxim-laptop kernel: [ 3495.250121] ------------[ cut here ]------------
> > > Apr 13 00:35:22 maxim-laptop kernel: [ 3495.250128] WARNING: at /home/maxim/software/kernel/linux-2.6/drivers/net/wireless/iwlwifi/iwl3945-base.c:496 iwl3945_mac_set_key+0x7e5/0x7f0 [iwl3945]()
> > > Apr 13 00:35:22 maxim-laptop kernel: [ 3495.250134] Hardware name: Aspire 5720
> > > Apr 13 00:35:22 maxim-laptop kernel: [ 3495.250137] no space for a new keyModules linked in: uhci_hcd af_packet nfsd exportfs nfs lockd nfs_acl auth_rpcgss sunrpc cpufreq_powersave cpufreq_conservative cpufreq_userspace acpi_cpufreq coretemp uvcvideo videodev v4l1_compat v4l2_compat_ioctl32 sbp2 joydev iwl3945 iwlcore psmouse snd_hda_codec_realtek rfkill ehci_hcd tg3 snd_hda_intel snd_hda_codec iTCO_wdt mac80211 nvidia(P) ohci1394 ricoh_mmc sdhci_pci sdhci evdev serio_raw libphy snd_hwdep iTCO_vendor_support usbcore snd_pcm snd_timer snd_page_alloc ext3 jbd mbcache fuse
> > > Apr 13 00:35:22 maxim-laptop kernel: [ 3495.250208] Pid: 8, comm: events/0 Tainted: P W 2.6.30-rc1-vanilla #5
> > > Apr 13 00:35:22 maxim-laptop kernel: [ 3495.250212] Call Trace:
> > > Apr 13 00:35:22 maxim-laptop kernel: [ 3495.250224] [<ffffffff802463f0>] warn_slowpath+0xd0/0x130
> > > Apr 13 00:35:22 maxim-laptop kernel: [ 3495.250233] [<ffffffff802c8bdf>] ? __slab_alloc+0xbf/0x760
> > > Apr 13 00:35:22 maxim-laptop kernel: [ 3495.250241] [<ffffffff802e60d1>] ? alloc_inode+0x51/0x60
> > > Apr 13 00:35:22 maxim-laptop kernel: [ 3495.250247] [<ffffffff802e3a1f>] ? __d_lookup+0xcf/0x150
> > > Apr 13 00:35:22 maxim-laptop kernel: [ 3495.250255] [<ffffffff8035988c>] ? security_inode_alloc+0x1c/0x20
> > > Apr 13 00:35:22 maxim-laptop kernel: [ 3495.250262] [<ffffffff802e5fbe>] ? inode_init_always+0x12e/0x1f0
> > > Apr 13 00:35:22 maxim-laptop kernel: [ 3495.250277] [<ffffffffa09dc100>] ? iwl3945_mac_set_key+0x0/0x7f0 [iwl3945]
> > > Apr 13 00:35:22 maxim-laptop kernel: [ 3495.250284] [<ffffffff8035a416>] ? security_d_instantiate+0x16/0x30
> > > Apr 13 00:35:22 maxim-laptop kernel: [ 3495.250291] [<ffffffff802e2d45>] ? d_instantiate+0x45/0x50
> > > Apr 13 00:35:22 maxim-laptop kernel: [ 3495.250313] [<ffffffffa09b97bd>] ? iwl_scan_cancel_timeout+0x2d/0xb0 [iwlcore]
> > > Apr 13 00:35:22 maxim-laptop kernel: [ 3495.250328] [<ffffffffa09dc8e5>] iwl3945_mac_set_key+0x7e5/0x7f0 [iwl3945]
> > > Apr 13 00:35:22 maxim-laptop kernel: [ 3495.250357] [<ffffffffa08d72fc>] __ieee80211_key_todo+0x16c/0x330 [mac80211]
> > > Apr 13 00:35:22 maxim-laptop kernel: [ 3495.250383] [<ffffffffa08d7630>] ? key_todo+0x0/0x10 [mac80211]
> > > Apr 13 00:35:22 maxim-laptop kernel: [ 3495.250408] [<ffffffffa08d7615>] ieee80211_key_todo+0x15/0x30 [mac80211]
> > > Apr 13 00:35:22 maxim-laptop kernel: [ 3495.250433] [<ffffffffa08d7639>] key_todo+0x9/0x10 [mac80211]
> > > Apr 13 00:35:22 maxim-laptop kernel: [ 3495.250441] [<ffffffff80259713>] worker_thread+0x1a3/0x2a0
> > > Apr 13 00:35:22 maxim-laptop kernel: [ 3495.250448] [<ffffffff8025e290>] ? autoremove_wake_function+0x0/0x40
> > > Apr 13 00:35:22 maxim-laptop kernel: [ 3495.250455] [<ffffffff80259570>] ? worker_thread+0x0/0x2a0
> > > Apr 13 00:35:22 maxim-laptop kernel: [ 3495.250461] [<ffffffff80259570>] ? worker_thread+0x0/0x2a0
> > > Apr 13 00:35:22 maxim-laptop kernel: [ 3495.250467] [<ffffffff8025dd96>] kthread+0x56/0x90
> > > Apr 13 00:35:22 maxim-laptop kernel: [ 3495.250475] [<ffffffff8020ceea>] child_rip+0xa/0x20
> > > Apr 13 00:35:22 maxim-laptop kernel: [ 3495.250481] [<ffffffff8025dd40>] ? kthread+0x0/0x90
> > > Apr 13 00:35:22 maxim-laptop kernel: [ 3495.250487] [<ffffffff8020cee0>] ? child_rip+0x0/0x20
> > > Apr 13 00:35:22 maxim-laptop kernel: [ 3495.250492] ---[ end trace a941121475b47e49 ]---
> > >
> > Happens often, usually after resume from disk. I have WPA2 network.
> >
> >
> > This is vanilla kernel commit b0cbc861a3c05e634520b049b5cc27ad6febb51f
>
> Sounds like you can easily reproduce it ... would it be possible to get
> us some extra logs for this problem? Could you please run with debug
> 0x400002 ?
>
> Thank you very much
>
> Reinette
>
>
It turns out that this bug doesn't show up, when I need (with debug
options you provided)
I found that I enabled hw encryption, although it is disabled by
default, and I suspect that this is due to that
I see clearly now that this warning (as expected) occures, just after
association, when wpa_supplicant sets keys.
I look at source for further information.
Best regards,
Maxim Levitsky
prev parent reply other threads:[~2009-04-15 0:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-12 22:43 A warning in latest -git 2.6.30-rc1 Maxim Levitsky
2009-04-13 16:05 ` reinette chatre
2009-04-15 0:48 ` Maxim Levitsky [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1239756491.8954.10.camel@maxim-laptop \
--to=maximlevitsky@gmail.com \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=linux-wireless@vger.kernel.org \
--cc=reinette.chatre@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox