From: Ben Greear <greearb@candelatech.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] lockdep buglet in ath9k.
Date: Tue, 12 Oct 2010 14:36:16 -0700 [thread overview]
Message-ID: <4CB4D4D0.9000601@candelatech.com> (raw)
I see this with lockdep enabled in today's wireless-testing.
INFO: trying to register non-static key.
the code is fine but needs lockdep annotation.
turning off the locking correctness validator.
Pid: 1755, comm: ifconfig Not tainted 2.6.36-rc7-wl+ #30
Call Trace:
[<c075e490>] ? printk+0xf/0x17
[<c045507e>] register_lock_class+0x5a/0x29e
[<c0455be6>] ? mark_lock+0x1e/0x1de
[<c0456af9>] __lock_acquire+0xa2/0xb8c
[<c0455be6>] ? mark_lock+0x1e/0x1de
[<c045763d>] lock_acquire+0x5a/0x78
[<f8c06133>] ? ath9k_config+0x274/0x3d8 [ath9k]
[<c0760152>] _raw_spin_lock_irqsave+0x2f/0x3f
[<f8c06133>] ? ath9k_config+0x274/0x3d8 [ath9k]
[<f8c06133>] ath9k_config+0x274/0x3d8 [ath9k]
[<f8882a2b>] ieee80211_hw_config+0x11b/0x125 [mac80211]
[<f888ee9d>] ieee80211_do_open+0x3b4/0x455 [mac80211]
[<f888e1b2>] ? ieee80211_check_concurrent_iface+0x21/0x13a [mac80211]
[<f888ef99>] ieee80211_open+0x5b/0x5e [mac80211]
[<c06cf333>] __dev_open+0x80/0xae
[<c06cd563>] __dev_change_flags+0xa0/0x115
[<c06cf287>] dev_change_flags+0x13/0x3f
[<c0718c2c>] devinet_ioctl+0x21e/0x49d
[<c071a30c>] inet_ioctl+0x82/0x9b
[<c06c0418>] sock_ioctl+0x1ce/0x1f0
[<c06c024a>] ? sock_ioctl+0x0/0x1f0
[<c04c27df>] do_vfs_ioctl+0x4a7/0x4ec
[<c0499a16>] ? handle_mm_fault+0x41d/0x9da
[<c04b823e>] ? fcheck_files+0x81/0xb6
[<c04c2865>] sys_ioctl+0x41/0x61
[<c0402f1c>] sysenter_do_call+0x12/0x38
ADDRCONF(NETDEV_UP): wlan0: link is not ready
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
WARNING: multiple messages have this Message-ID (diff)
From: Ben Greear <greearb@candelatech.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"ath9k-devel@lists.ath9k.org" <ath9k-devel@venema.h4ckr.net>
Subject: lockdep buglet in ath9k.
Date: Tue, 12 Oct 2010 14:36:16 -0700 [thread overview]
Message-ID: <4CB4D4D0.9000601@candelatech.com> (raw)
I see this with lockdep enabled in today's wireless-testing.
INFO: trying to register non-static key.
the code is fine but needs lockdep annotation.
turning off the locking correctness validator.
Pid: 1755, comm: ifconfig Not tainted 2.6.36-rc7-wl+ #30
Call Trace:
[<c075e490>] ? printk+0xf/0x17
[<c045507e>] register_lock_class+0x5a/0x29e
[<c0455be6>] ? mark_lock+0x1e/0x1de
[<c0456af9>] __lock_acquire+0xa2/0xb8c
[<c0455be6>] ? mark_lock+0x1e/0x1de
[<c045763d>] lock_acquire+0x5a/0x78
[<f8c06133>] ? ath9k_config+0x274/0x3d8 [ath9k]
[<c0760152>] _raw_spin_lock_irqsave+0x2f/0x3f
[<f8c06133>] ? ath9k_config+0x274/0x3d8 [ath9k]
[<f8c06133>] ath9k_config+0x274/0x3d8 [ath9k]
[<f8882a2b>] ieee80211_hw_config+0x11b/0x125 [mac80211]
[<f888ee9d>] ieee80211_do_open+0x3b4/0x455 [mac80211]
[<f888e1b2>] ? ieee80211_check_concurrent_iface+0x21/0x13a [mac80211]
[<f888ef99>] ieee80211_open+0x5b/0x5e [mac80211]
[<c06cf333>] __dev_open+0x80/0xae
[<c06cd563>] __dev_change_flags+0xa0/0x115
[<c06cf287>] dev_change_flags+0x13/0x3f
[<c0718c2c>] devinet_ioctl+0x21e/0x49d
[<c071a30c>] inet_ioctl+0x82/0x9b
[<c06c0418>] sock_ioctl+0x1ce/0x1f0
[<c06c024a>] ? sock_ioctl+0x0/0x1f0
[<c04c27df>] do_vfs_ioctl+0x4a7/0x4ec
[<c0499a16>] ? handle_mm_fault+0x41d/0x9da
[<c04b823e>] ? fcheck_files+0x81/0xb6
[<c04c2865>] sys_ioctl+0x41/0x61
[<c0402f1c>] sysenter_do_call+0x12/0x38
ADDRCONF(NETDEV_UP): wlan0: link is not ready
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next reply other threads:[~2010-10-12 21:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-12 21:36 Ben Greear [this message]
2010-10-12 21:36 ` lockdep buglet in ath9k Ben Greear
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=4CB4D4D0.9000601@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath9k-devel@lists.ath9k.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.