public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Zephaniah E. Hull" <warp@babylon.d2dc.net>
To: Greg KH <greg@kroah.com>,
	linux-kernel@vger.kernel.org,
	"David A. Desrosiers" <desrod@gnu-designs.com>,
	linux-usb-devel@lists.sourceforge.net
Subject: Re: USBDEVFS_RESET deadlocks USB bus.
Date: Fri, 4 Jun 2004 16:05:30 -0400	[thread overview]
Message-ID: <20040604200530.GC3261@babylon.d2dc.net> (raw)
In-Reply-To: <20040604200211.GB3261@babylon.d2dc.net>

[-- Attachment #1: Type: text/plain, Size: 1493 bytes --]

On Fri, Jun 04, 2004 at 04:02:11PM -0400, Zephaniah E. Hull wrote:
> On Fri, Jun 04, 2004 at 12:52:47PM -0700, Greg KH wrote:
> > On Fri, Jun 04, 2004 at 03:39:11PM -0400, Zephaniah E. Hull wrote:
> > > Starting at 2.6.7-rc1 or so (that is when we first noticed it) the new
> > > pilot-link libusb back end started deadlocking the entire USB bus that
> > > the palm device was on.
> > > 
> > > I have finally tracked it down to happening when we make the
> > > USBDEVFS_RESET ioctl, we never return from it and from that point on the
> > > bus in question is completely dead, no processing is done, no
> > > notifications of devices being plugged in or unplugged.
> > > 
> > > This is still happening in 2.6.7-rc2-mm1.
> > > 
> > > It seems to happen with both the UHCI and OHCI back ends, so it is
> > > probably above that.
> > > 
> > > Given that there were heavy locking changes, I suspect that the case in
> > > question got screwed up somehow.

Further details, existing links with devices remain functional (IE, the
HID layer continues to get data from already connected mice), however
all processing or new devices or removed devices seems to be just gone,
on all USB busses.

-- 
	1024D/E65A7801 Zephaniah E. Hull <warp@babylon.d2dc.net>
	   92ED 94E4 B1E6 3624 226D  5727 4453 008B E65A 7801
	    CCs of replies from mailing lists are requested.

"And now, little kittens, we're going to run across red-hot
motherboards, with our bare feet." -- Buzh.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-06-04 20:05 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 [this message]
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
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=20040604200530.GC3261@babylon.d2dc.net \
    --to=warp@babylon.d2dc.net \
    --cc=desrod@gnu-designs.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.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