Bug 208729 - locking problem with BCSP
locking problem with BCSP
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Kernel Maintainer List
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2006-09-30 20:05 EDT by David Woodhouse
Modified: 2008-08-02 19:40 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-05-06 20:54:31 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description David Woodhouse 2006-09-30 20:05:23 EDT
[ INFO: possible recursive locking detected ]
2.6.18-1.2699.fc6 #1
swapper/0 is trying to acquire lock:
 (&list->lock#3){+...}, at: [<c05ad307>] skb_dequeue+0x12/0x43

but task is already holding lock:
 (&list->lock#3){+...}, at: [<df98cd79>] bcsp_dequeue+0x6a/0x11e [hci_uart]

other info that might help us debug this:
3 locks held by swapper/0:
 #0:  (&irq_lists[i].lock){+...}, at: [<c054b36d>] serial8250_interrupt+0x18/0xe3
 #1:  (&hu->rx_lock){+...}, at: [<df98c4d1>] hci_uart_tty_receive+0x2e/0x79
 #2:  (&list->lock#3){+...}, at: [<df98cd79>] bcsp_dequeue+0x6a/0x11e [hci_uart]

stack backtrace:
 [<c0405850>] show_trace_log_lvl+0x58/0x16a
 [<c0405e58>] show_trace+0xd/0x10
 [<c0405f71>] dump_stack+0x19/0x1b
 [<c043845a>] __lock_acquire+0x77e/0x9a2
 [<c0438bef>] lock_acquire+0x4b/0x6c
 [<c060d987>] _spin_lock_irqsave+0x22/0x32
 [<c05ad307>] skb_dequeue+0x12/0x43
 [<df98cd8d>] bcsp_dequeue+0x7e/0x11e [hci_uart]
 [<df98c3af>] hci_uart_tx_wakeup+0xc8/0xfa [hci_uart]
 [<df98cf3e>] bcsp_complete_rx_pkt+0x3c/0x476 [hci_uart]
 [<df98d745>] bcsp_recv+0x3cd/0x497 [hci_uart]
 [<df98c4df>] hci_uart_tty_receive+0x3c/0x79 [hci_uart]
 [<c052d9da>] flush_to_ldisc+0x119/0x150
 [<c052da4e>] tty_flip_buffer_push+0x3d/0x53
 [<c054a6c5>] receive_chars+0x1ec/0x226
 [<c054b3c2>] serial8250_interrupt+0x6d/0xe3
 [<c044dc58>] handle_IRQ_event+0x20/0x4d
 [<c044dd19>] __do_IRQ+0x94/0xef
 [<c0406de1>] do_IRQ+0x9e/0xbd
 [<c04050a5>] common_interrupt+0x25/0x30
Comment 1 Dave Jones 2007-08-06 15:57:57 EDT
still happening ?
Comment 2 Bug Zapper 2008-04-03 14:23:08 EDT
Based on the date this bug was created, it appears to have been reported
against rawhide during the development of a Fedora release that is no
longer maintained. In order to refocus our efforts as a project we are
flagging all of the open bugs for releases which are no longer
maintained. If this bug remains in NEEDINFO thirty (30) days from now,
we will automatically close it.

If you can reproduce this bug in a maintained Fedora version (7, 8, or
rawhide), please change this bug to the respective version and change
the status to ASSIGNED. (If you're unable to change the bug's version
or status, add a comment to the bug and someone will change it for you.)

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we're following is outlined here:

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
Comment 3 Bug Zapper 2008-05-06 20:54:29 EDT
This bug has been in NEEDINFO for more than 30 days since feedback was
first requested. As a result we are closing it.

If you can reproduce this bug in the future against a maintained Fedora
version please feel free to reopen it against that version.

The process we're following is outlined here:

Note You need to log in before you can comment on or make changes to this bug.