From: Andreas Reis <andreas.reis@gmail.com>
To: Alan Stern <stern@rowland.harvard.edu>, Hannes Reinecke <hare@suse.de>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
SCSI development list <linux-scsi@vger.kernel.org>,
USB list <linux-usb@vger.kernel.org>
Subject: Re: [PATCH 0/3] Fix USB deadlock caused by SCSI error handling
Date: Thu, 10 Apr 2014 12:58:24 +0200 [thread overview]
Message-ID: <53467950.3010403@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1404091358340.28384-100000@netrider.rowland.org>
That patch appears to work in preventing the crashes, judged on one
repeated appearance of the bug.
dmesg had the usual
[ 215.229903] usb 4-2: usb_disable_lpm called, do nothing
[ 215.336941] usb 4-2: reset SuperSpeed USB device number 3 using xhci_hcd
[ 215.350296] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called
with disabled ep ffff880427b829c0
[ 215.350305] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called
with disabled ep ffff880427b82a08
[ 215.350621] usb 4-2: usb_enable_lpm called, do nothing
repeated five times, followed by one
[ 282.795801] sd 8:0:0:0: Device offlined - not ready after error recovery
and then as often as something tried to read from it:
[ 295.585472] sd 8:0:0:0: rejecting I/O to offline device
The stick could then be properly un- and remounted (the latter if it had
been physically replugged) without issue — for the bug to reoccur after
one to three minutes. I tried this three times, no dmesg difference
except the ep addresses varied on two of that.
Andreas Reis
On 09.04.2014 20:02, Alan Stern wrote:
> On Wed, 9 Apr 2014, Hannes Reinecke wrote:
>
>>> I finally got a chance to try it out. It does seem to do what we want.
>>> I didn't track the flow of control in complete detail, but the command
>>> definitely got aborted both times it was issued.
>>>
>> Good, so it is as I thought. James, can we include this patch instead of
>> your prior solution?
>
> First, we should have the original bug reporter try it out.
>
> Andreas, the patch in question can be found here:
>
> http://marc.info/?l=linux-usb&m=139627666606597&w=2
>
> Can you try this in place of the 1/3 patch posted by James? It should
> have the same effect, of preventing your system from crashing when the
> READ command fails.
>
> Alan Stern
>
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-04-10 10:58 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-28 17:47 [PATCH 0/3] Fix USB deadlock caused by SCSI error handling James Bottomley
2014-03-28 17:49 ` [PATCH 1/3] [SCSI] Fix abort state memory problem James Bottomley
2014-03-31 6:58 ` Hannes Reinecke
2014-03-31 13:06 ` Alan Stern
2014-03-28 17:50 ` [PATCH 2/3] [SCSI] Fix spurious request sense in error handling James Bottomley
2014-03-31 6:59 ` Hannes Reinecke
2014-03-28 17:51 ` [PATCH 3/3] [SCSI] Fix command result state propagation James Bottomley
2014-03-31 7:00 ` Hannes Reinecke
2014-03-28 19:29 ` [PATCH 0/3] Fix USB deadlock caused by SCSI error handling Alan Stern
2014-03-31 7:22 ` Hannes Reinecke
2014-03-31 13:33 ` Alan Stern
2014-03-31 14:37 ` Hannes Reinecke
[not found] ` <53397DAE.9010801-l3A5Bk7waGM@public.gmane.org>
2014-03-31 15:03 ` James Bottomley
2014-03-31 22:41 ` Alan Stern
[not found] ` <1396278224.3152.26.camel-sFMDBYUN5F8GjUHQrlYNx2Wm91YjaHnnhRte9Li2A+AAvxtiuMwx3w@public.gmane.org>
2014-04-01 6:14 ` Hannes Reinecke
2014-03-31 22:29 ` Alan Stern
2014-04-01 15:37 ` Hannes Reinecke
[not found] ` <533ADD26.1030300-l3A5Bk7waGM@public.gmane.org>
2014-04-01 21:28 ` Alan Stern
[not found] ` <Pine.LNX.4.44L0.1404011718350.7652-100000-pYrvlCTfrz9XsRXLowluHWD2FQJk+8+b@public.gmane.org>
2014-04-02 6:03 ` Hannes Reinecke
2014-04-07 15:26 ` Alan Stern
[not found] ` <Pine.LNX.4.44L0.1404071125220.20747-100000-pYrvlCTfrz9XsRXLowluHWD2FQJk+8+b@public.gmane.org>
2014-04-09 17:42 ` Hannes Reinecke
[not found] ` <53458680.4090500-l3A5Bk7waGM@public.gmane.org>
2014-04-09 18:02 ` Alan Stern
2014-04-10 10:58 ` Andreas Reis [this message]
2014-04-10 11:37 ` Hannes Reinecke
2014-04-10 12:26 ` Andreas Reis
2014-04-10 12:29 ` Hannes Reinecke
2014-04-10 15:31 ` Alan Stern
2014-04-10 17:52 ` Hannes Reinecke
[not found] ` <5346DA43.4010603-l3A5Bk7waGM@public.gmane.org>
2014-04-10 20:36 ` James Bottomley
2014-04-11 5:52 ` Hannes Reinecke
[not found] ` <53468297.1040909-l3A5Bk7waGM@public.gmane.org>
2014-04-11 19:08 ` Andreas Reis
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=53467950.3010403@gmail.com \
--to=andreas.reis@gmail.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=hare@suse.de \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.