From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Takashi Iwai <tiwai@suse.de>
Cc: Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org, Wu Fengguang <wfg@linux.intel.com>
Subject: Re: [bug] sound: INFO: possible recursive locking detected
Date: Thu, 08 Jan 2009 17:12:54 +0100 [thread overview]
Message-ID: <1231431174.11687.483.camel@twins> (raw)
In-Reply-To: <s5h63kp7p8f.wl%tiwai@suse.de>
On Thu, 2009-01-08 at 17:10 +0100, Takashi Iwai wrote:
> At Thu, 08 Jan 2009 16:39:31 +0100,
> I wrote:
> >
> > At Thu, 8 Jan 2009 16:20:37 +0100,
> > Ingo Molnar wrote:
> > >
> > > FYI, -tip testing found this new lockdep workqueue locking assert
> > > triggered by the Intel HDA sound driver:
> (snip)
> > > [ 30.718689] =============================================
> > > [ 30.718689] [ INFO: possible recursive locking detected ]
> > > [ 30.718689] 2.6.28-tip #2
> > > [ 30.718689] ---------------------------------------------
> > > [ 30.718689] events/0/7 is trying to acquire lock:
> > > [ 30.718689] (events){--..}, at: [<ffffffff80281050>] flush_workqueue+0x0/0x90
> > > [ 30.718689]
> > > [ 30.718689] but task is already holding lock:
> > > [ 30.718689] (events){--..}, at: [<ffffffff8028076a>] run_workqueue+0x14a/0x240
> > > [ 30.718689]
> > > [ 30.718689] other info that might help us debug this:
> > > [ 30.718689] 2 locks held by events/0/7:
> > > [ 30.718689] #0: (events){--..}, at: [<ffffffff8028076a>] run_workqueue+0x14a/0x240
> > > [ 30.718689] #1: (&wfc.work){--..}, at: [<ffffffff8028076a>] run_workqueue+0x14a/0x240
> > > [ 30.718689]
> > > [ 30.718689] stack backtrace:
> > > [ 30.718689] Pid: 7, comm: events/0 Not tainted 2.6.28-tip #2
> > > [ 30.718689] Call Trace:
> > > [ 30.718689] [<ffffffff80295836>] validate_chain+0xc56/0x1340
> > > [ 30.718689] [<ffffffff802974e6>] __lock_acquire+0x376/0x610
> > > [ 30.718689] [<ffffffff80297819>] lock_acquire+0x99/0xd0
> > > [ 30.718689] [<ffffffff80281050>] ? flush_workqueue+0x0/0x90
> > > [ 30.718689] [<ffffffff80281091>] flush_workqueue+0x41/0x90
> > > [ 30.718689] [<ffffffff80281050>] ? flush_workqueue+0x0/0x90
> > > [ 30.718689] [<ffffffff802810f5>] flush_scheduled_work+0x15/0x20
> > > [ 30.718689] [<ffffffff80c59794>] azx_clear_irq_pending+0x54/0x60
> > > [ 30.718689] [<ffffffff80c599ec>] azx_free+0x10c/0x160
> > > [ 30.718689] [<ffffffff80bae9ad>] ? snd_device_free+0x8d/0x100
> > > [ 30.718689] [<ffffffff80c59a52>] azx_dev_free+0x12/0x20
> > > [ 30.718689] [<ffffffff80bae9a1>] snd_device_free+0x81/0x100
> > > [ 30.718689] [<ffffffff80baea89>] snd_device_free_all+0x69/0xa0
> > > [ 30.718689] [<ffffffff80ba8a70>] snd_card_do_free+0x50/0xd0
> > > [ 30.718689] [<ffffffff80ba9602>] snd_card_free+0xa2/0xc0
> > > [ 30.718689] [<ffffffff8061115f>] ? __delay+0xf/0x20
> > > [ 30.718689] [<ffffffff80edbb6a>] azx_probe+0x38a/0x9f0
> > > [ 30.718689] [<ffffffff80c5a240>] ? azx_send_cmd+0x0/0x130
> > > [ 30.718689] [<ffffffff80c5a370>] ? azx_get_response+0x0/0x210
> > > [ 30.718689] [<ffffffff80c59b70>] ? azx_attach_pcm_stream+0x0/0x1b0
> > > [ 30.718689] [<ffffffff802804d0>] ? do_work_for_cpu+0x0/0x30
> > > [ 30.718689] [<ffffffff80634807>] local_pci_probe+0x17/0x20
> > > [ 30.718689] [<ffffffff802804e8>] do_work_for_cpu+0x18/0x30
> > > [ 30.718689] [<ffffffff802804d0>] ? do_work_for_cpu+0x0/0x30
> > > [ 30.718689] [<ffffffff802807bb>] run_workqueue+0x19b/0x240
> > > [ 30.718689] [<ffffffff8028076a>] ? run_workqueue+0x14a/0x240
> > > [ 30.718689] [<ffffffff802809cf>] worker_thread+0xaf/0x110
> > > [ 30.718689] [<ffffffff80284e20>] ? autoremove_wake_function+0x0/0x40
> > > [ 30.718689] [<ffffffff80280920>] ? worker_thread+0x0/0x110
> > > [ 30.718689] [<ffffffff802848e3>] kthread+0x53/0x80
> > > [ 30.718689] [<ffffffff8022c3aa>] child_rip+0xa/0x20
> > > [ 30.718689] [<ffffffff8022bcbe>] ? restore_args+0x0/0x30
> > > [ 30.718689] [<ffffffff80284890>] ? kthread+0x0/0x80
> > > [ 30.718689] [<ffffffff8022c3a0>] ? child_rip+0x0/0x20
>
> The backtrace implies that the probe callback is called in a
> workqueue. Is it right?
Yes, it appears a worklet tries to flush the queue he's on.
next prev parent reply other threads:[~2009-01-08 16:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-08 15:20 [bug] sound: INFO: possible recursive locking detected Ingo Molnar
2009-01-08 15:39 ` Takashi Iwai
2009-01-08 16:10 ` Takashi Iwai
2009-01-08 16:12 ` Peter Zijlstra [this message]
2009-01-08 16:17 ` Takashi Iwai
2009-01-08 16:53 ` Takashi Iwai
2009-01-09 5:06 ` Wu Fengguang
2009-01-09 7:18 ` Takashi Iwai
2009-01-09 8:45 ` [PATCH] ALSA: hda - create hda_codec.control_mutex for kcontrol->private_value Wu Fengguang
2009-01-09 9:00 ` Takashi Iwai
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=1231431174.11687.483.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tiwai@suse.de \
--cc=wfg@linux.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