From: Jens Axboe <axboe@kernel.dk>
To: Hannes Reinecke <hare@suse.de>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-scsi@vger.kernel.org" <Linux-scsi@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>
Subject: Re: requeue failure with blk-mq-sched
Date: Thu, 19 Jan 2017 06:09:13 -0800 [thread overview]
Message-ID: <8b7436c0-91c4-0b70-071c-364abe1f24f5@kernel.dk> (raw)
In-Reply-To: <fb509d83-c895-ba78-e181-145c77542eac@suse.de>
On 01/19/2017 04:27 AM, Hannes Reinecke wrote:
> Hi Jens,
>
> upon further testing with your blk-mq-sched branch I hit a queue stall
> during requeing:
>
> [ 202.340959] sd 3:0:4:1: tag#473 Send: scmd 0xffff880422e7a440
> [ 202.340962] sd 3:0:4:1: tag#473 CDB: Test Unit Ready 00 00 00 00 00 00
> [ 202.341161] sd 3:0:4:1: tag#473 Done: ADD_TO_MLQUEUE Result:
> hostbyte=DID_OK driverbyte=DRIVER_OK
> [ 202.341164] sd 3:0:4:1: tag#473 CDB: Test Unit Ready 00 00 00 00 00 00
> [ 202.341167] sd 3:0:4:1: tag#473 Sense Key : Unit Attention [current]
> [ 202.341171] sd 3:0:4:1: tag#473 Add. Sense: Power on, reset, or bus
> device reset occurred
> [ 202.341173] sd 3:0:4:1: tag#473 scsi host busy 1 failed 0
> [ 202.341176] sd 3:0:4:1: tag#473 Inserting command ffff880422e7a440
> into mlqueue
>
> ... and that is the last ever heard of that device.
> The 'device_busy' count remains at '1' and no further commands will be
> sent to the device.
If device_busy is at 1, then it should have a command pending. Where did
you log this - it would be bandy if you attached whatever debug patch
you put in, so we can see where the printks are coming from. If we get a
BUSY with nothing pending, the driver should be ensuring that the queue
gets run again later through blk_mq_delay_queue(), for instance.
When the device is stuck, does it restart if you send it IO?
--
Jens Axboe
next prev parent reply other threads:[~2017-01-19 14:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-19 12:27 requeue failure with blk-mq-sched Hannes Reinecke
2017-01-19 14:09 ` Jens Axboe [this message]
2017-01-19 14:24 ` Hannes Reinecke
2017-01-19 14:35 ` Jens Axboe
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=8b7436c0-91c4-0b70-071c-364abe1f24f5@kernel.dk \
--to=axboe@kernel.dk \
--cc=Linux-scsi@vger.kernel.org \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=linux-block@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