From: Duncan Sands <baldrick@free.fr>
To: linux-usb-devel@lists.sourceforge.net
Cc: "Zephaniah E. Hull" <warp@babylon.d2dc.net>,
Greg KH <greg@kroah.com>,
linux-kernel@vger.kernel.org,
"David A. Desrosiers" <desrod@gnu-designs.com>
Subject: Re: [linux-usb-devel] Re: USBDEVFS_RESET deadlocks USB bus.
Date: Mon, 7 Jun 2004 21:11:32 +0200 [thread overview]
Message-ID: <200406072111.32827.baldrick@free.fr> (raw)
In-Reply-To: <20040607154310.GA10404@babylon.d2dc.net>
> To give some background, the libusb backend of pilot-link is a slightly
> odd design, we do the init work, reset the device, and then setup a read
> thread, which basicly does a continuous loop of bulk no-timeout reads
> from USB.
>
> In the primary thread we do most of the work, including doing the USB
> bulk writes to do things like ask the pilot for information.
>
> Which, once I had things working again, sometimes resulted in the
> following issue:
>
> lt-pilot-xfer D 00000010 0 3351 3097 3398 (NOTLB)
> ca93dec0 00000082 00000001 00000010 cdaa434c caac11e8 cdaa43ec caac11a0
> ca93ded4 ce8b4318 c03a2fc0 00000000 3904f0c0 000f42ec cb7fe398 ca913c24
> 00000246 ca93c000 ca93defc c0336735 ca913c2c cb7fe1f0 00000001 cb7fe1f0
> Call Trace:
> [<c0336735>] __down+0x85/0x120
> [<c033692f>] __down_failed+0xb/0x14
> [<c0273245>] .text.lock.devio+0xe5/0x120
> [<c015a45d>] file_ioctl+0x5d/0x170
> [<c015a686>] sys_ioctl+0x116/0x250
> [<c0103f8f>] syscall_call+0x7/0xb
>
> lt-pilot-xfer D 00000001 0 3398 3351 (NOTLB)
> ca8ebe1c 00000082 00000000 00000001 0ca97854 ce5bca08 d7d85000 00000001
> ce5bca08 00000246 ca8ebe2c 00000000 38200f00 000f42ec cb7fe938 ca8ebeac
> ca8ea000 ca8ea000 ca8ebe70 c0336eb8 00000000 cb7fe790 c01146a0 00000000
> Call Trace:
> [<c0336eb8>] wait_for_completion+0x78/0xf0
> [<c026cc0a>] usb_start_wait_urb+0x7a/0xc0
> [<c0271866>] proc_bulk+0x116/0x220
> [<c0272f61>] usbdev_ioctl+0x581/0x710
> [<c015a45d>] file_ioctl+0x5d/0x170
> [<c015a686>] sys_ioctl+0x116/0x250
> [<c0103f8f>] syscall_call+0x7/0xb
>
> With the device not sending us any more data until it receives the
> write, and the write not getting to send until the bulk read finishes or
> the device goes away.
>
> With the predictable annoyance this causes, of course.
This is my fault. I will fix it.
Ciao,
Duncan.
next prev parent reply other threads:[~2004-06-07 19:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-04 19:39 USBDEVFS_RESET deadlocks USB bus Zephaniah E. Hull
2004-06-04 19:52 ` Greg KH
2004-06-04 20:02 ` Zephaniah E. Hull
2004-06-04 20:05 ` Zephaniah E. Hull
2004-06-04 20:07 ` Greg KH
2004-06-04 20:28 ` David A. Desrosiers
2004-06-04 21:06 ` Zephaniah E. Hull
2004-06-04 20:40 ` [linux-usb-devel] " Duncan Sands
2004-06-04 21:30 ` Zephaniah E. Hull
2004-06-05 7:55 ` Duncan Sands
2004-06-06 6:35 ` Zephaniah E. Hull
2004-06-07 7:05 ` Duncan Sands
2004-06-07 15:43 ` Zephaniah E. Hull
2004-06-07 19:11 ` Duncan Sands [this message]
2004-06-07 23:13 ` Zephaniah E. Hull
2004-06-08 20:19 ` Duncan Sands
2004-06-18 20:02 ` Ian Morgan
2004-06-19 13:48 ` Duncan Sands
2004-07-02 20:47 ` Zephaniah E. Hull
2004-07-02 21:11 ` Alan Stern
2004-07-02 21:52 ` Zephaniah E. Hull
2004-07-03 8:28 ` Duncan Sands
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=200406072111.32827.baldrick@free.fr \
--to=baldrick@free.fr \
--cc=desrod@gnu-designs.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=warp@babylon.d2dc.net \
/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