← Back to team overview

tiomap-dev team mailing list archive

[Bug 879693] [NEW] Beagle xM: recursive lock while using network

 

You have been subscribed to a public bug:

Got while installing a package at the console and copying another file with scp (from my host to the device):
[ 2778.849121] =============================================
[ 2778.856353] [ INFO: possible recursive locking detected ]
[ 2778.862030] 3.1.0-2-linaro-omap #2~ppa~oneiric-Ubuntu
[ 2778.867340] ---------------------------------------------
[ 2778.873016] http/5380 is trying to acquire lock:
[ 2778.877868]  (&(&parent->list_lock)->rlock){-.-.-.}, at: [<803d213f>] cache_flusharray+0x1f/0x78
[ 2778.887145] 
[ 2778.887145] but task is already holding lock:
[ 2778.893280]  (&(&parent->list_lock)->rlock){-.-.-.}, at: [<803d213f>] cache_flusharray+0x1f/0x78
[ 2778.902557] 
[ 2778.902557] other info that might help us debug this:
[ 2778.909423]  Possible unsafe locking scenario:
[ 2778.909423] 
[ 2778.915649]        CPU0
[ 2778.918212]        ----
[ 2778.920776]   lock(&(&parent->list_lock)->rlock);
[ 2778.925720]   lock(&(&parent->list_lock)->rlock);
[ 2778.930694] 
[ 2778.930694]  *** DEADLOCK ***
[ 2778.930694] 
[ 2778.936920]  May be due to missing lock nesting notation
[ 2778.936920] 
[ 2778.944061] 2 locks held by http/5380:
[ 2778.947998]  #0:  (sk_lock-AF_INET){+.+.+.}, at: [<8034ee45>] tcp_recvmsg+0x1b/0x55a
[ 2778.956176]  #1:  (&(&parent->list_lock)->rlock){-.-.-.}, at: [<803d213f>] cache_flusharray+0x1f/0x78
[ 2778.965911] 
[ 2778.965911] stack backtrace:
[ 2778.970550] [<80010c5d>] (unwind_backtrace+0x1/0x90) from [<80056cb7>] (print_deadlock_bug+0x7b/0xa4)
[ 2778.980255] [<80056cb7>] (print_deadlock_bug+0x7b/0xa4) from [<80057d0d>] (validate_chain.isra.24+0x351/0x370)
[ 2778.990753] [<80057d0d>] (validate_chain.isra.24+0x351/0x370) from [<80058637>] (__lock_acquire+0x4d9/0x552)
[ 2779.001098] [<80058637>] (__lock_acquire+0x4d9/0x552) from [<80058aa7>] (lock_acquire+0xbb/0xd8)
[ 2779.010345] [<80058aa7>] (lock_acquire+0xbb/0xd8) from [<803df5ab>] (_raw_spin_lock+0x2b/0x36)
[ 2779.019409] [<803df5ab>] (_raw_spin_lock+0x2b/0x36) from [<803d213f>] (cache_flusharray+0x1f/0x78)
[ 2779.028839] [<803d213f>] (cache_flusharray+0x1f/0x78) from [<800a8fd9>] (kmem_cache_free+0x3d/0xc0)
[ 2779.038360] [<800a8fd9>] (kmem_cache_free+0x3d/0xc0) from [<800a9143>] (free_block+0xa3/0xdc)
[ 2779.047332] [<800a9143>] (free_block+0xa3/0xdc) from [<803d2177>] (cache_flusharray+0x57/0x78)
[ 2779.056365] [<803d2177>] (cache_flusharray+0x57/0x78) from [<800a8f67>] (kfree+0xc1/0xf6)
[ 2779.065002] [<800a8f67>] (kfree+0xc1/0xf6) from [<80325a79>] (__kfree_skb+0x15/0x1e)
[ 2779.073150] [<80325a79>] (__kfree_skb+0x15/0x1e) from [<8034f293>] (tcp_recvmsg+0x469/0x55a)
[ 2779.082031] [<8034f293>] (tcp_recvmsg+0x469/0x55a) from [<80363ebd>] (inet_recvmsg+0x8d/0xac)
[ 2779.091003] [<80363ebd>] (inet_recvmsg+0x8d/0xac) from [<8031fdcb>] (do_sock_read+0x83/0x8a)
[ 2779.099884] [<8031fdcb>] (do_sock_read+0x83/0x8a) from [<80320c13>] (sock_aio_read+0x4f/0x68)
[ 2779.108825] [<80320c13>] (sock_aio_read+0x4f/0x68) from [<800ab83b>] (do_sync_read+0x63/0x8c)
[ 2779.117797] [<800ab83b>] (do_sync_read+0x63/0x8c) from [<800abd5f>] (vfs_read+0x67/0xc4)
[ 2779.126312] [<800abd5f>] (vfs_read+0x67/0xc4) from [<800abde9>] (sys_read+0x2d/0x4e)
[ 2779.134460] [<800abde9>] (sys_read+0x2d/0x4e) from [<8000bfe1>] (ret_fast_syscall+0x1/0x52)

Kernel: linux-image-3.1.0-2-linaro-omap  3.1.0-2.2~ppa~oneiric
Hwpack: hwpack_linaro-omap3-x11-base_20111021-2_armel_supported.tar.gz
Rootfs: linaro-o-ubuntu-desktop-tar-20111021-0.tar.gz

** Affects: linaro-ubuntu
     Importance: Medium
         Status: Won't Fix

** Affects: linaro-landing-team-ti
     Importance: Undecided
         Status: Incomplete


** Tags: beagle
-- 
Beagle xM: recursive lock while using network
https://bugs.launchpad.net/bugs/879693
You received this bug notification because you are a member of TI OMAP Developers, which is subscribed to linaro-landing-team-ti.