linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 77631] task scsi_eh_6:537 blocked for more than 120 seconds.
Date: Tue, 10 Jun 2014 20:55:56 +0000	[thread overview]
Message-ID: <bug-77631-11613-2OZDY3BHgB@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-77631-11613@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=77631

--- Comment #1 from Alan Stern <stern@rowland.harvard.edu> ---
On Tue, 10 Jun 2014, James Bottomley wrote:

> From the trace below, this looks to be a USB issue (USB added to cc):
> the scsi error handler thread is waiting for usb storage to complete the
> reset.  It's a 3.14.5 kernel, so the previous reset hang because of
> spurious sense requests should be fixed.
> 
> James
> 
> 
> On Tue, 2014-06-10 at 16:50 +0000, bugzilla-daemon@bugzilla.kernel.org
> wrote:
> > https://bugzilla.kernel.org/show_bug.cgi?id=77631
> > 
> >             Bug ID: 77631
> >            Summary: task scsi_eh_6:537 blocked for more than 120 seconds.
> >            Product: IO/Storage
> >            Version: 2.5
> >     Kernel Version: 3.14.6
> >           Hardware: All
> >                 OS: Linux
> >               Tree: Mainline
> >             Status: NEW
> >           Severity: normal
> >           Priority: P1
> >          Component: SCSI
> >           Assignee: linux-scsi@vger.kernel.org
> >           Reporter: mikhail.v.gavrilov@gmail.com
> >         Regression: No
> > 
> > Created attachment 138941
> >   --> https://bugzilla.kernel.org/attachment.cgi?id=138941&action=edit
> > kernel log
> > 
> > task scsi_eh_6:537 blocked for more than 120 seconds.

This line from earlier in the kernel log is highly suspicious:

> [   46.330470] usb-storage: Error in queuecommand_lck: us->srb = ffff88080c532600

This means that the SCSI midlayer called the queuecommand routine twice 
with no intervening completion, even though the maximum queue depth is 
only 1.

Mikhail, is this bug reproducible?  If it is, can you post a usbmon 
trace showing the events leading up to the bug?

Does the bug occur if the device is plugged into a USB-2 bus rather 
than a USB-3 bus?

Alan Stern

-- 
You are receiving this mail because:
You are the assignee for the bug.

  parent reply	other threads:[~2014-06-10 20:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-10 16:50 [Bug 77631] New: task scsi_eh_6:537 blocked for more than 120 seconds bugzilla-daemon
     [not found] ` <bug-77631-11613-3bo0kxnWaOQUvHkbgXJLS5sdmw4N0Rt+2LY78lusg7I@public.gmane.org/>
2014-06-10 17:31   ` James Bottomley
2014-06-10 20:49     ` Alan Stern
2014-06-10 20:55 ` bugzilla-daemon [this message]
2014-06-10 21:44 ` [Bug 77631] " bugzilla-daemon
2014-06-10 21:49 ` bugzilla-daemon
2014-06-10 21:50 ` bugzilla-daemon

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=bug-77631-11613-2OZDY3BHgB@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    /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).