From: Greg KH <gregkh@linuxfoundation.org>
To: "Schmid, Carsten" <Carsten_Schmid@mentor.com>
Cc: Alan Stern <stern@rowland.harvard.edu>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: Crash/hung task in usb-storage thread
Date: Fri, 24 May 2019 16:59:35 +0200 [thread overview]
Message-ID: <20190524145935.GA9757@kroah.com> (raw)
In-Reply-To: <b4d08a84df3d45bfa77d27d411a17578@SVR-IES-MBX-03.mgc.mentorg.com>
On Fri, May 24, 2019 at 01:33:14PM +0000, Schmid, Carsten wrote:
> > On Thu, 23 May 2019, Schmid, Carsten wrote:
> >
> > > Hi USB maintainers,
> > >
> > > we recently have seen a problem with usb-storage when trying to read
> > from a device.
> > > This happened on a 4.14.86 kernel.
> > >
> > > The kernel's dmesg shows: (log has been submitted via DLT)
> > > 1200.862250 kernel: usb 1-3.1: reset high-speed USB device number 10
> > using xhci_hcd
> > > 1285.466289 kernel: usb 1-3.1: reset high-speed USB device number 10
> > using xhci_hcd
> > > 1291.911286 kernel: usb-storage: Error in queuecommand_lck: us->srb =
> > ffff9d66b02e3528
> > > 1292.018079 kernel: usb-storage: Error in queuecommand_lck: us->srb =
> > ffff9d66b02e3528
> > > 1292.043073 kernel: usb-storage: Error in queuecommand_lck: us->srb =
> > ffff9d66b02e3528
> > > 1292.069078 kernel: usb-storage: Error in queuecommand_lck: us->srb =
> > ffff9d66b02e3528
> > > 1292.093066 kernel: usb-storage: Error in queuecommand_lck: us->srb =
> > ffff9d66b02e3528
> >
> > Since there haven't been any substantive change to usb-storage since
> > 4.14 was released, there's a good chance this is a problem with
> > xhci-hcd.
> >
> > Is this problem repeatable? Can you collect a usbmon trace showing
> > what happens when the problem occurs?
> >
> Unfortunately this happened in the field on a test drive.
> I don't have access to the device.
> So, no, can't be reproduced by now.
>
> > > There has been a similar bug being fixed in 3.17 kernel series, maybe the
> > bug has been re-introduced?
> > > https://bugzilla.kernel.org/show_bug.cgi?id=88341
> >
> > That is _extremely_ unlikely.
> >
> Looked into the history of that bug report.
> Strange: no fix is menioned.
> Reported: 2014-17-11
> Remark on 2019-02-26
> No hint to a real fix.
> It simply disappeared ...
We do not track USB bugs in bugzilla.kernel.org, so NEVER treat that as
the state of anything with regards to USB and Linux, sorry. Ask here on
the mailing list instead.
The fact that nothing else is shown on that bug is to be expected, and
is normal.
thanks,
greg k-h
next prev parent reply other threads:[~2019-05-24 14:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 11:57 Crash/hung task in usb-storage thread Schmid, Carsten
2019-05-23 12:04 ` Greg KH
2019-05-23 12:16 ` AW: " Schmid, Carsten
2019-05-23 12:26 ` Greg KH
2019-05-23 12:30 ` AW: " Schmid, Carsten
2019-05-23 12:35 ` Greg KH
2019-05-23 13:16 ` AW: " Schmid, Carsten
2019-05-23 18:05 ` Greg KH
2019-05-23 16:50 ` Alan Stern
2019-05-24 13:33 ` AW: " Schmid, Carsten
2019-05-24 14:59 ` Greg KH [this message]
2019-05-24 15:24 ` Alan Stern
2019-05-24 15:47 ` AW: " Schmid, Carsten
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=20190524145935.GA9757@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Carsten_Schmid@mentor.com \
--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 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).