From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] USB deadlock in v2.5.67
Date: Fri, 18 Apr 2003 02:02:07 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590723705558@msgid-missing> (raw)
So my 2.5.67 kernel was humming along nicely when I got the idea to
unplug a USB keyboard. Instant deadlock. The backtrace shows this:
Call Trace:
[<e0000000048c4260>] hcd_free_dev+0x140/0x240
[<e0000000048b96e0>] usb_release_dev+0x100/0x140
[<e000000004743420>] device_release+0x80/0xa0
[<e000000004697600>] kobject_cleanup+0x100/0x120
[<e0000000048c34d0>] urb_unlink+0x110/0x1a0
[<e0000000048c4390>] usb_hcd_giveback_urb+0x30/0x1a0
[<e0000000048da730>] dl_done_list+0x230/0x2a0
[<e0000000048dbfd0>] ohci_irq+0x290/0x340
[<e0000000048c4580>] usb_hcd_irq+0x80/0x100
[<e000000004414e00>] handle_IRQ_event+0xa0/0x120
[<e0000000044155e0>] do_IRQ+0x360/0x460
[<e0000000044174b0>] ia64_handle_irq+0x70/0x140
[<e000000004411e40>] ia64_leave_kernel+0x0/0x240
<hcd_free_dev+0x140> translates into line 1249 in hcd.c, where it
does:
spin_lock_irqsave (&hcd_data_lock, flags);
The deadlock is pretty obvious: the same lock has already been
acquired urb_unlink(), 4 levels up in the call-chain.
Anybody have a fix for this?
--david
reply other threads:[~2003-04-18 2:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-linux-ia64-105590723705558@msgid-missing \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox