From: Ben Greear <greearb@candelatech.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: ath5k lockdep warning in 39-rc6+
Date: Fri, 06 May 2011 15:09:57 -0700 [thread overview]
Message-ID: <4DC471B5.30609@candelatech.com> (raw)
In-Reply-To: <4DC47158.1000401@candelatech.com>
On 05/06/2011 03:08 PM, Ben Greear wrote:
> The main problem with this is that it disables lockdep
> after this...
>
> lanforge-D0-20 login: INFO: trying to register non-static key.
> the code is fine but needs lockdep annotation.
> turning off the locking correctness validator.
> Pid: 1934, comm: net.hotplug Not tainted 2.6.39-rc6-wlc3+ #6
> Call Trace:
> [<c0448994>] register_lock_class+0x102/0x277
> [<c044a4d0>] __lock_acquire+0x8e/0xb78
> [<c0625bf3>] ? __ata_qc_complete+0xca/0xcf
> [<c062767a>] ? ata_qc_complete+0x15d/0x163
> [<c06353c8>] ? ata_hsm_qc_complete+0x9c/0xb5
> [<c0635954>] ? ata_sff_hsm_move+0x573/0x592
> [<c044b016>] lock_acquire+0x5c/0x70
> [<f9c2fe71>] ? ath5k_set_current_imask+0x21/0x62 [ath5k]
> [<c075d798>] _raw_spin_lock_irqsave+0x46/0x56
> [<f9c2fe71>] ? ath5k_set_current_imask+0x21/0x62 [ath5k]
> [<f9c2fe71>] ath5k_set_current_imask+0x21/0x62 [ath5k]
> [<f9c30158>] ath5k_intr+0x2a6/0x3e5 [ath5k]
> [<c0468b0f>] handle_irq_event_percpu+0x24/0x123
> [<c0468c3a>] handle_irq_event+0x2c/0x43
> [<c046a37f>] ? handle_edge_irq+0xaa/0xaa
> [<c046a3e9>] handle_fasteoi_irq+0x6a/0x88
> <IRQ> [<c040315f>] ? do_IRQ+0x34/0x95
> [<c0449990>] ? trace_hardirqs_on_caller+0xfe/0x11f
> [<c076202e>] ? common_interrupt+0x2e/0x40
>
>
Hrm, may be worse..maybe this is the cause of the deadlock
I'm seeing. This printed out shortly after:
BUG: spinlock lockup on CPU#0, net.hotplug/1934, f5acc470
Pid: 1934, comm: net.hotplug Not tainted 2.6.39-rc6-wlc3+ #6
Call Trace:
[<c057ecf7>] do_raw_spin_lock+0xea/0x108
[<c075d79f>] _raw_spin_lock_irqsave+0x4d/0x56
[<f9c2fe71>] ? ath5k_set_current_imask+0x21/0x62 [ath5k]
[<f9c2fe71>] ath5k_set_current_imask+0x21/0x62 [ath5k]
[<f9c30158>] ath5k_intr+0x2a6/0x3e5 [ath5k]
[<c0468b0f>] handle_irq_event_percpu+0x24/0x123
[<c0468c3a>] handle_irq_event+0x2c/0x43
[<c046a37f>] ? handle_edge_irq+0xaa/0xaa
[<c046a3e9>] handle_fasteoi_irq+0x6a/0x88
<IRQ> [<c040315f>] ? do_IRQ+0x34/0x95
[<c0449990>] ? trace_hardirqs_on_caller+0xfe/0x11f
[<c076202e>] ? common_interrupt+0x2e/0x40
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2011-05-06 22:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-06 22:08 ath5k lockdep warning in 39-rc6+ Ben Greear
2011-05-06 22:09 ` Ben Greear [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=4DC471B5.30609@candelatech.com \
--to=greearb@candelatech.com \
--cc=linux-wireless@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;
as well as URLs for NNTP newsgroup(s).