2.6.20-rc6: LOCKDEP: possible recursive locking detected
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I am not sure if I have seen it before, possibly yes.
Bluetooth: Core ver 2.11
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP ver 2.8
Bluetooth: L2CAP socket layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM ver 1.8
Bluetooth: L2CAP ver 2.8
Bluetooth: L2CAP socket layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM ver 1.8
usb 1-1: new full speed USB device using ohci_hcd and address 2
usb 1-1: configuration #1 chosen from 1 choice
Bluetooth: HCI USB driver ver 2.9
usbcore: registered new interface driver hci_usb
=
[ INFO: possible recursive locking detected ]
2.6.20-rc6-1avb #12
- -
kio_obex/8530 is trying to acquire lock:
(sk_lock-AF_BLUETOOTH){--..}, at: [] l2cap_sock_bind+0x3f/0xe0
[l2cap]
but task is already holding lock:
(sk_lock-AF_BLUETOOTH){--..}, at: [] rfcomm_sock_connect+0x45/0xd0
[rfcomm]
other info that might help us debug this:
2 locks held by kio_obex/8530:
#0: (sk_lock-AF_BLUETOOTH){--..}, at: []
rfcomm_sock_connect+0x45/0xd0 [rfcomm]
#1: (rfcomm_mutex){--..}, at: [] mutex_lock+0x21/0x30
stack backtrace:
[] show_trace_log_lvl+0x1a/0x30
[] show_trace+0x12/0x20
[] dump_stack+0x16/0x20
[] __lock_acquire+0xad5/0xdb0
[] lock_acquire+0x57/0x70
[] lock_sock_nested+0xe8/0x100
[] l2cap_sock_bind+0x3f/0xe0 [l2cap]
[] rfcomm_dlc_open+0xaf/0x220 [rfcomm]
[] rfcomm_sock_connect+0xa9/0xd0 [rfcomm]
[] sys_connect+0x5d/0x90
[] sys_socketcall+0xbd/0x280
[] sysenter_past_esp+0x5f/0x99
===
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFvJDBR6LMutpd94wRAtIwAKDIpbGrwv4OWwr4Y1nMTsyUmHi63QCePElg
oRkNKcxrdHdiJjfn5deCBA4=
=RGl9
-END PGP SIGNATURE-
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
2.6.20-rc6: LOCKDEP: possible recursive locking detected
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I am not sure if I have seen it before, possibly yes.
Bluetooth: Core ver 2.11
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP ver 2.8
Bluetooth: L2CAP socket layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM ver 1.8
Bluetooth: L2CAP ver 2.8
Bluetooth: L2CAP socket layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM ver 1.8
usb 1-1: new full speed USB device using ohci_hcd and address 2
usb 1-1: configuration #1 chosen from 1 choice
Bluetooth: HCI USB driver ver 2.9
usbcore: registered new interface driver hci_usb
=
[ INFO: possible recursive locking detected ]
2.6.20-rc6-1avb #12
- -
kio_obex/8530 is trying to acquire lock:
(sk_lock-AF_BLUETOOTH){--..}, at: [dfed181f] l2cap_sock_bind+0x3f/0xe0
[l2cap]
but task is already holding lock:
(sk_lock-AF_BLUETOOTH){--..}, at: [dfef7035] rfcomm_sock_connect+0x45/0xd0
[rfcomm]
other info that might help us debug this:
2 locks held by kio_obex/8530:
#0: (sk_lock-AF_BLUETOOTH){--..}, at: [dfef7035]
rfcomm_sock_connect+0x45/0xd0 [rfcomm]
#1: (rfcomm_mutex){--..}, at: [c02a2fc1] mutex_lock+0x21/0x30
stack backtrace:
[c0103fea] show_trace_log_lvl+0x1a/0x30
[c01045f2] show_trace+0x12/0x20
[c01046a6] dump_stack+0x16/0x20
[c0134585] __lock_acquire+0xad5/0xdb0
[c01348b7] lock_acquire+0x57/0x70
[c0237d48] lock_sock_nested+0xe8/0x100
[dfed181f] l2cap_sock_bind+0x3f/0xe0 [l2cap]
[dfef489f] rfcomm_dlc_open+0xaf/0x220 [rfcomm]
[dfef7099] rfcomm_sock_connect+0xa9/0xd0 [rfcomm]
[c023685d] sys_connect+0x5d/0x90
[c0236fbd] sys_socketcall+0xbd/0x280
[c010300e] sysenter_past_esp+0x5f/0x99
===
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFvJDBR6LMutpd94wRAtIwAKDIpbGrwv4OWwr4Y1nMTsyUmHi63QCePElg
oRkNKcxrdHdiJjfn5deCBA4=
=RGl9
-END PGP SIGNATURE-
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[LOCKDEP] Possible recursive locking detected
.config: http://www.msxnet.org/config-2.6.20-rc5
=
[ INFO: possible recursive locking detected ]
2.6.20-rc5 #1
-
swapper/0 is trying to acquire lock:
(>lock){++..}, at: [] __wake_up+0x18/0x43
but task is already holding lock:
(>lock){++..}, at: [] __wake_up+0x18/0x43
other info that might help us debug this:
3 locks held by swapper/0:
#0: (slock-AF_INET/1){-+..}, at: [] tcp_v4_rcv+0x673/0x85b
#1: (af_callback_keys + sk->sk_family#2){-.-?}, at: []
sock_def_readable+0x15/0x6e
#2: (>lock){++..}, at: [] __wake_up+0x18/0x43
stack backtrace:
[] __lock_acquire+0xab7/0xd7b
[] add_lock_to_list+0x36/0x8f
[] lock_acquire+0x57/0x6f
[] __wake_up+0x18/0x43
[] _spin_lock_irqsave+0x32/0x41
[] __wake_up+0x18/0x43
[] __wake_up+0x18/0x43
[] ep_poll_safewake+0x9b/0xd4
[] ep_poll_callback+0x83/0xb4
[] __wake_up_common+0x39/0x59
[] __wake_up+0x32/0x43
[] sock_def_readable+0x6c/0x6e
[] tcp_data_queue+0x421/0xbd1
[] tcp_v4_rcv+0x673/0x85b
[] tcp_rcv_established+0x360/0x68b
[] tcp_v4_do_rcv+0x95/0x2d9
[] tcp_v4_rcv+0x673/0x85b
[] _spin_lock_nested+0x27/0x32
[] tcp_v4_rcv+0x849/0x85b
[] ip_local_deliver+0x100/0x268
[] _spin_lock+0x29/0x34
[] ip_rcv+0x263/0x467
[] enable_8259A_irq+0xd/0x4b
[] enable_8259A_irq+0xd/0x4b
[] netif_receive_skb+0x1f3/0x2e7
[] trace_hardirqs_on+0x76/0x14a
[] process_backlog+0x79/0xf3
[] net_rx_action+0x97/0x167
[] __do_softirq+0x4b/0x9c
[] do_softirq+0x3f/0x41
[] do_IRQ+0x52/0x8a
[] common_interrupt+0x24/0x34
[] common_interrupt+0x2e/0x34
[] acpi_processor_idle+0x1bc/0x356 [processor]
[] acpi_processor_idle+0x1bf/0x356 [processor]
[] cpu_idle+0x39/0x4e
[] start_kernel+0x28f/0x32a
[] unknown_bootoption+0x0/0x259
===
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[LOCKDEP] Possible recursive locking detected
.config: http://www.msxnet.org/config-2.6.20-rc5
=
[ INFO: possible recursive locking detected ]
2.6.20-rc5 #1
-
swapper/0 is trying to acquire lock:
(q-lock){++..}, at: [c0114dc0] __wake_up+0x18/0x43
but task is already holding lock:
(q-lock){++..}, at: [c0114dc0] __wake_up+0x18/0x43
other info that might help us debug this:
3 locks held by swapper/0:
#0: (slock-AF_INET/1){-+..}, at: [c02d9ed8] tcp_v4_rcv+0x673/0x85b
#1: (af_callback_keys + sk-sk_family#2){-.-?}, at: [c029d137]
sock_def_readable+0x15/0x6e
#2: (q-lock){++..}, at: [c0114dc0] __wake_up+0x18/0x43
stack backtrace:
[c0130f78] __lock_acquire+0xab7/0xd7b
[c012e86a] add_lock_to_list+0x36/0x8f
[c0131293] lock_acquire+0x57/0x6f
[c0114dc0] __wake_up+0x18/0x43
[c0306f7a] _spin_lock_irqsave+0x32/0x41
[c0114dc0] __wake_up+0x18/0x43
[c0114dc0] __wake_up+0x18/0x43
[c017fd65] ep_poll_safewake+0x9b/0xd4
[c0180d5f] ep_poll_callback+0x83/0xb4
[c0114a1b] __wake_up_common+0x39/0x59
[c0114dda] __wake_up+0x32/0x43
[c029d18e] sock_def_readable+0x6c/0x6e
[c02d0562] tcp_data_queue+0x421/0xbd1
[c02d9ed8] tcp_v4_rcv+0x673/0x85b
[c02d22a5] tcp_rcv_established+0x360/0x68b
[c02d7c73] tcp_v4_do_rcv+0x95/0x2d9
[c02d9ed8] tcp_v4_rcv+0x673/0x85b
[c0306c43] _spin_lock_nested+0x27/0x32
[c02da0ae] tcp_v4_rcv+0x849/0x85b
[c02bf8f8] ip_local_deliver+0x100/0x268
[c0306c77] _spin_lock+0x29/0x34
[c02bf5f4] ip_rcv+0x263/0x467
[c0106c97] enable_8259A_irq+0xd/0x4b
[c0106c97] enable_8259A_irq+0xd/0x4b
[c02a34ca] netif_receive_skb+0x1f3/0x2e7
[c012ff8e] trace_hardirqs_on+0x76/0x14a
[c02a4d69] process_backlog+0x79/0xf3
[c02a4f7c] net_rx_action+0x97/0x167
[c011d0f7] __do_softirq+0x4b/0x9c
[c011d187] do_softirq+0x3f/0x41
[c0105228] do_IRQ+0x52/0x8a
[c0103708] common_interrupt+0x24/0x34
[c0103712] common_interrupt+0x2e/0x34
[e1a88e4a] acpi_processor_idle+0x1bc/0x356 [processor]
[e1a88e4d] acpi_processor_idle+0x1bf/0x356 [processor]
[c010133a] cpu_idle+0x39/0x4e
[c040a6b5] start_kernel+0x28f/0x32a
[c040a1cd] unknown_bootoption+0x0/0x259
===
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
