From: Bill Nottingham <notting@redhat.com>
To: linux-kernel@vger.kernel.org
Subject: lockdep warning w/2.6.18rc3-git3, ipw2200
Date: Fri, 4 Aug 2006 17:21:49 -0400 [thread overview]
Message-ID: <20060804212149.GA2889@nostromo.devel.redhat.com> (raw)
eth1: no IPv6 routers present
eee80211_crypt: registered algorithm 'WEP'
=================================
[ INFO: inconsistent lock state ]
---------------------------------
inconsistent {in-softirq-W} -> {softirq-on-W} usage.
ip/2759 [HC0[0]:SC0[0]:HE1:SE1] takes:
(&ifa->lock){-+..}, at: [<f8b2d836>] inet6_addr_add+0xf8/0x13e [ipv6]
{in-softirq-W} state was registered at:
[<c043bfb9>] lock_acquire+0x4b/0x6a
[<c0608d48>] _spin_lock_bh+0x1e/0x2d
[<f8b2e757>] addrconf_dad_timer+0x3a/0xe2 [ipv6]
[<c042dbc0>] run_timer_softirq+0x108/0x167
[<c04293ab>] __do_softirq+0x78/0xf2
[<c0406673>] do_softirq+0x5a/0xbe
irq event stamp: 3479
hardirqs last enabled at (3479): [<c04291bf>] local_bh_enable_ip+0xc6/0xcf
hardirqs last disabled at (3477): [<c0429152>] local_bh_enable_ip+0x59/0xcf
softirqs last enabled at (3478): [<f8b2a9ce>] ipv6_add_addr+0x210/0x254 [ipv6]
softirqs last disabled at (3466): [<c0608e17>] _read_lock_bh+0xb/0x2d
other info that might help us debug this:
1 lock held by ip/2759:
#0: (rtnl_mutex){--..}, at: [<c0607c98>] mutex_lock+0x21/0x24
stack backtrace:
[<c04051ee>] show_trace_log_lvl+0x58/0x159
[<c04057ea>] show_trace+0xd/0x10
[<c0405903>] dump_stack+0x19/0x1b
[<c043a402>] print_usage_bug+0x1ca/0x1d7
[<c043a8eb>] mark_lock+0x239/0x353
[<c043b50a>] __lock_acquire+0x459/0x997
[<c043bfb9>] lock_acquire+0x4b/0x6a
[<c0608d1b>] _spin_lock+0x19/0x28
[<f8b2d836>] inet6_addr_add+0xf8/0x13e [ipv6]
[<f8b2da39>] inet6_rtm_newaddr+0x1bd/0x1d2 [ipv6]
[<c05b8f13>] rtnetlink_rcv_msg+0x1b3/0x1d6
[<c05c479b>] netlink_run_queue+0x69/0xfe
[<c05b8d16>] rtnetlink_rcv+0x29/0x42
[<c05c4c28>] netlink_data_ready+0x12/0x50
[<c05c3c90>] netlink_sendskb+0x1f/0x37
[<c05c4569>] netlink_unicast+0x1a1/0x1bb
[<c05c4c09>] netlink_sendmsg+0x275/0x282
[<c05a823a>] sock_sendmsg+0xe8/0x103
[<c05a8a49>] sys_sendmsg+0x14d/0x1a8
[<c05a9c1b>] sys_socketcall+0x16b/0x186
[<c0403faf>] syscall_call+0x7/0xb
DWARF2 unwinder stuck at syscall_call+0x7/0xb
Leftover inexact backtrace:
[<c04057ea>] show_trace+0xd/0x10
[<c0405903>] dump_stack+0x19/0x1b
[<c043a402>] print_usage_bug+0x1ca/0x1d7
[<c043a8eb>] mark_lock+0x239/0x353
[<c043b50a>] __lock_acquire+0x459/0x997
[<c043bfb9>] lock_acquire+0x4b/0x6a
[<c0608d1b>] _spin_lock+0x19/0x28
[<f8b2d836>] inet6_addr_add+0xf8/0x13e [ipv6]
[<f8b2da39>] inet6_rtm_newaddr+0x1bd/0x1d2 [ipv6]
[<c05b8f13>] rtnetlink_rcv_msg+0x1b3/0x1d6
[<c05c479b>] netlink_run_queue+0x69/0xfe
[<c05b8d16>] rtnetlink_rcv+0x29/0x42
[<c05c4c28>] netlink_data_ready+0x12/0x50
[<c05c3c90>] netlink_sendskb+0x1f/0x37
[<c05c4569>] netlink_unicast+0x1a1/0x1bb
[<c05c4c09>] netlink_sendmsg+0x275/0x282
[<c05a823a>] sock_sendmsg+0xe8/0x103
[<c05a8a49>] sys_sendmsg+0x14d/0x1a8
[<c05a9c1b>] sys_socketcall+0x16b/0x186
[<c0403faf>] syscall_call+0x7/0xb
Is this the same as the netlink/wireless event one discussed for
orinoco?
Bill
reply other threads:[~2006-08-04 21:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20060804212149.GA2889@nostromo.devel.redhat.com \
--to=notting@redhat.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®