=======================================================
[ INFO: possible circular locking dependency detected ]
2.6.31-rc7Y-00012-g3edf2fb #1
-------------------------------------------------------
pvrusb2-context/969 is trying to acquire lock:
 (cpu_add_remove_lock){+.+.+.}, at: [<c1033f3f>] cpu_maps_update_begin
+0xf/0x20

but task is already holding lock:
 (&hdw->big_lock_mutex){+.+.+.}, at: [<f92ed0e2>] pvr2_hdw_initialize
+0x22/0xde0 [pvrusb2]

which lock already depends on the new lock.


I've attached the complete printed kernel dmesg info.

-- 
Roger
http://rogerx.freeshell.org
cx25840 1-0044: loaded v4l-cx25840.fw firmware (16382 bytes)

=======================================================
[ INFO: possible circular locking dependency detected ]
2.6.31-rc7Y-00012-g3edf2fb #1
-------------------------------------------------------
pvrusb2-context/969 is trying to acquire lock:
 (cpu_add_remove_lock){+.+.+.}, at: [<c1033f3f>] cpu_maps_update_begin+0xf/0x20

but task is already holding lock:
 (&hdw->big_lock_mutex){+.+.+.}, at: [<f92ed0e2>] pvr2_hdw_initialize+0x22/0xde0 [pvrusb2]

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #3 (&hdw->big_lock_mutex){+.+.+.}:
       [<c1056405>] validate_chain+0xa75/0xfd0
       [<c1056d3a>] __lock_acquire+0x3da/0xa00
       [<c10573dc>] lock_acquire+0x7c/0x100
       [<c143c115>] mutex_lock_nested+0x45/0x300
       [<f92ebc49>] pvr2_hdw_worker_poll+0x19/0x310 [pvrusb2]
       [<c1043d09>] worker_thread+0x1f9/0x320
       [<c104704a>] kthread+0x7a/0x90
       [<c100392b>] kernel_thread_helper+0x7/0x1c
       [<ffffffff>] 0xffffffff

-> #2 (&hdw->workpoll){+.+.+.}:
       [<c1056405>] validate_chain+0xa75/0xfd0
       [<c1056d3a>] __lock_acquire+0x3da/0xa00
       [<c10573dc>] lock_acquire+0x7c/0x100
       [<c1043d04>] worker_thread+0x1f4/0x320
       [<c104704a>] kthread+0x7a/0x90
       [<c100392b>] kernel_thread_helper+0x7/0x1c
       [<ffffffff>] 0xffffffff

-> #1 ((hdw->name)){+.+.+.}:
       [<c1056405>] validate_chain+0xa75/0xfd0
       [<c1056d3a>] __lock_acquire+0x3da/0xa00
       [<c10573dc>] lock_acquire+0x7c/0x100
       [<c1043236>] cleanup_workqueue_thread+0x46/0xd0
       [<c1043350>] destroy_workqueue+0x60/0xa0
       [<f92eb8e2>] pvr2_hdw_destroy+0x32/0x120 [pvrusb2]
       [<f92f337e>] pvr2_context_destroy+0x1e/0xd0 [pvrusb2]
       [<f92f3757>] pvr2_context_thread_func+0xc7/0x2d0 [pvrusb2]
       [<c104704a>] kthread+0x7a/0x90
       [<c100392b>] kernel_thread_helper+0x7/0x1c
       [<ffffffff>] 0xffffffff

-> #0 (cpu_add_remove_lock){+.+.+.}:
       [<c1055f36>] validate_chain+0x5a6/0xfd0
       [<c1056d3a>] __lock_acquire+0x3da/0xa00
       [<c10573dc>] lock_acquire+0x7c/0x100
       [<c143c115>] mutex_lock_nested+0x45/0x300
       [<c1033f3f>] cpu_maps_update_begin+0xf/0x20
       [<c1043309>] destroy_workqueue+0x19/0xa0
       [<f95b2969>] cx25840_initialize+0x279/0x3c0 [cx25840]
       [<f95b345b>] cx25840_load_fw+0x3b/0x70 [cx25840]
       [<f92ed554>] pvr2_hdw_initialize+0x494/0xde0 [pvrusb2]
       [<f92f3705>] pvr2_context_thread_func+0x75/0x2d0 [pvrusb2]
       [<c104704a>] kthread+0x7a/0x90
       [<c100392b>] kernel_thread_helper+0x7/0x1c
       [<ffffffff>] 0xffffffff

other info that might help us debug this:

1 lock held by pvrusb2-context/969:
 #0:  (&hdw->big_lock_mutex){+.+.+.}, at: [<f92ed0e2>] pvr2_hdw_initialize+0x22/0xde0 [pvrusb2]

stack backtrace:
Pid: 969, comm: pvrusb2-context Not tainted 2.6.31-rc7Y-00012-g3edf2fb #1
Call Trace:
 [<c105582c>] print_circular_bug_tail+0x7c/0xd0
 [<c1053634>] ? print_circular_bug_entry+0x44/0x50
 [<c1055f36>] validate_chain+0x5a6/0xfd0
 [<c1056d3a>] __lock_acquire+0x3da/0xa00
 [<c143e0b2>] ? _spin_unlock_irq+0x22/0x50
 [<c10573dc>] lock_acquire+0x7c/0x100
 [<c1033f3f>] ? cpu_maps_update_begin+0xf/0x20
 [<c143b1e8>] ? schedule+0x238/0x8e0
 [<c143c115>] mutex_lock_nested+0x45/0x300
 [<c1033f3f>] ? cpu_maps_update_begin+0xf/0x20
 [<c1043921>] ? __queue_work+0x31/0x40
 [<c1033f3f>] cpu_maps_update_begin+0xf/0x20
 [<c1043309>] destroy_workqueue+0x19/0xa0
 [<f95b2969>] cx25840_initialize+0x279/0x3c0 [cx25840]
 [<c1047130>] ? autoremove_wake_function+0x0/0x50
 [<f95b345b>] cx25840_load_fw+0x3b/0x70 [cx25840]
 [<f92ed554>] pvr2_hdw_initialize+0x494/0xde0 [pvrusb2]
 [<c105465f>] ? trace_hardirqs_on_caller+0xef/0x150
 [<c143be85>] ? __mutex_unlock_slowpath+0xb5/0x170
 [<c105465f>] ? trace_hardirqs_on_caller+0xef/0x150
 [<c10546cb>] ? trace_hardirqs_on+0xb/0x10
 [<f92f3690>] ? pvr2_context_thread_func+0x0/0x2d0 [pvrusb2]
 [<c143bf48>] ? mutex_unlock+0x8/0x10
 [<f92f308a>] ? pvr2_context_set_notify+0xca/0x100 [pvrusb2]
 [<f92f3690>] ? pvr2_context_thread_func+0x0/0x2d0 [pvrusb2]
 [<f92f3705>] pvr2_context_thread_func+0x75/0x2d0 [pvrusb2]
 [<c1047130>] ? autoremove_wake_function+0x0/0x50
 [<c104704a>] kthread+0x7a/0x90
 [<c1046fd0>] ? kthread+0x0/0x90
 [<c100392b>] kernel_thread_helper+0x7/0x1c

Attachment: signature.asc
Description: This is a digitally signed message part

_______________________________________________
pvrusb2 mailing list
[email protected]
http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2

Reply via email to