From mboxrd@z Thu Jan 1 00:00:00 1970 From: joel silvestre Subject: 2.6.29.1-rt9 INFO: possible circular locking dependency detected Date: Sun, 26 Apr 2009 14:09:46 +0200 Message-ID: <1240747786.9289.7.camel@zordi2> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit To: rt-users Return-path: Received: from smtp2a.orange.fr ([80.12.242.138]:63074 "EHLO smtp2a.orange.fr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753074AbZDZMJt (ORCPT ); Sun, 26 Apr 2009 08:09:49 -0400 Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf2a02.orange.fr (SMTP Server) with ESMTP id 5C11480000AE for ; Sun, 26 Apr 2009 14:09:48 +0200 (CEST) Received: from [192.168.0.3] (AAnnecy-256-1-91-179.w90-10.abo.wanadoo.fr [90.10.170.179]) by mwinf2a02.orange.fr (SMTP Server) with ESMTP id 1E7C380000AA for ; Sun, 26 Apr 2009 14:09:48 +0200 (CEST) Sender: linux-rt-users-owner@vger.kernel.org List-ID: Hi, I get this message at boot time on i386: All the best. ======================================================= [ INFO: possible circular locking dependency detected ] 2.6.29.1-rt9-moa1-debug #1 ------------------------------------------------------- alsactl/2244 is trying to acquire lock: (&ice->gpio_mutex){+.+.+.}, at: [] wm_master_mute_put +0x2c/0x109 [snd_ice1724] but task is already holding lock: ((struct rw_semaphore *)(&card->controls_rwsem)){++++.+}, at: [] rt_down_read+0xa/0xc which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 ((struct rw_semaphore *)(&card->controls_rwsem)){++++.+}: [] __lock_acquire+0x105d/0x1397 [] lock_acquire+0xaf/0xcc [] rt_down_write+0x1b/0x2a [] snd_ctl_add+0x3a/0x17b [snd] [] aureon_add_controls+0x169/0x1cd [snd_ice1724] [] snd_vt1724_probe+0xba9/0xcf9 [snd_ice1724] [] local_pci_probe+0xe/0x10 [] pci_device_probe+0x46/0x69 [] driver_probe_device+0xa2/0x13e [] __driver_attach+0x4f/0x71 [] bus_for_each_dev+0x40/0x6a [] driver_attach+0x14/0x16 [] bus_add_driver+0xfa/0x216 [] driver_register+0x87/0xe4 [] __pci_register_driver+0x49/0x75 [] 0xf85bb017 [] do_one_initcall+0x4a/0x111 [] sys_init_module+0x87/0x186 [] sysenter_do_call+0x12/0x36 [] 0xffffffff -> #0 (&ice->gpio_mutex){+.+.+.}: [] __lock_acquire+0xdc3/0x1397 [] lock_acquire+0xaf/0xcc [] _mutex_lock+0x1b/0x2a [] wm_master_mute_put+0x2c/0x109 [snd_ice1724] [] snd_ctl_ioctl+0x926/0xd7f [snd] [] vfs_ioctl+0x22/0x69 [] do_vfs_ioctl+0x46a/0x4a3 [] sys_ioctl+0x40/0x5a [] sysenter_do_call+0x12/0x36 [] 0xffffffff other info that might help us debug this: 2 locks held by alsactl/2244: #0: (&card->power_lock){+.+...}, at: [] snd_ctl_ioctl +0x878/0xd7f [snd] #1: ((struct rw_semaphore *)(&card->controls_rwsem)){++++.+}, at: [] rt_down_read+0xa/0xc stack backtrace: Pid: 2244, comm: alsactl Not tainted 2.6.29.1-rt9-moa1-debug #1 Call Trace: [] ? printk+0xf/0x13 [] print_circular_bug_tail+0xaa/0xb5 [] __lock_acquire+0xdc3/0x1397 [] lock_acquire+0xaf/0xcc [] ? wm_master_mute_put+0x2c/0x109 [snd_ice1724] [] _mutex_lock+0x1b/0x2a [] ? wm_master_mute_put+0x2c/0x109 [snd_ice1724] [] wm_master_mute_put+0x2c/0x109 [snd_ice1724] [] snd_ctl_ioctl+0x926/0xd7f [snd] [] ? __lock_acquire+0x137e/0x1397 [] ? wakeup_softirqd+0x11/0x36 [] ? __do_softirq+0x32/0x196 [] ? snd_ctl_ioctl+0x0/0xd7f [snd] [] vfs_ioctl+0x22/0x69 [] do_vfs_ioctl+0x46a/0x4a3 [] ? trace_hardirqs_on_thunk+0xc/0x10 [] ? restore_nocheck_notrace+0x0/0xe [] ? fget_light+0x1a/0x95 [] sys_ioctl+0x40/0x5a [] sysenter_do_call+0x12/0x36