linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Stern <stern@rowland.harvard.edu>
To: Oliver Neukum <oneukum@suse.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	Jens Axboe <axboe@kernel.dk>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	<linux-block@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>, <linux-usb@vger.kernel.org>
Subject: Re: Lockup on USB and block devices
Date: Mon, 14 Oct 2019 11:13:18 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.44L0.1910141112031.28937-100000@netrider.rowland.org> (raw)
In-Reply-To: <1571054381.19529.16.camel@suse.com>

On Mon, 14 Oct 2019, Oliver Neukum wrote:

> Am Dienstag, den 01.10.2019, 14:31 -0400 schrieb Alan Stern:
> > It looks like a problem with your xHCI USB host controller.  Normally a
> > usb-storage transfer would be aborted after 90 seconds.  But if the
> > host controller (or its driver) isn't working right, and the abort
> > never completes, you end up with a situation like this -- usb-storage
> > and the higher SCSI and block layers waiting indefinitely for an event
> > that won't occur.
> 
> Hi,
> 
> that would imply that usb_unlink_urb() is malfunctioning
> without taking down the whole bus. Is that likely?

Mathias is a better person to ask than me.  But yes, as far as I know,
something like that can happen.

Alan Stern


  reply	other threads:[~2019-10-14 15:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-01 17:44 Steven Rostedt
2019-10-01 18:31 ` Alan Stern
2019-10-14 11:59   ` Oliver Neukum
2019-10-14 15:13     ` Alan Stern [this message]
2019-10-14 10:56 ` Oliver Neukum

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=Pine.LNX.4.44L0.1910141112031.28937-100000@netrider.rowland.org \
    --to=stern@rowland.harvard.edu \
    --cc=axboe@kernel.dk \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=oneukum@suse.com \
    --cc=rostedt@goodmis.org \
    --subject='Re: Lockup on USB and block devices' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).