All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ming Lei <ming.lei@redhat.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: Hang with blk-mq map series (block/008)
Date: Wed, 11 Apr 2018 10:30:59 +0800	[thread overview]
Message-ID: <20180411023059.GE4494@ming.t460p> (raw)
In-Reply-To: <6e1d9201-e0f6-cdf4-9572-c67bf5a7e06e@kernel.dk>

On Tue, Apr 10, 2018 at 08:08:43PM -0600, Jens Axboe wrote:
> On 4/10/18 8:02 PM, Ming Lei wrote:
> > On Tue, Apr 10, 2018 at 09:51:41AM -0600, Jens Axboe wrote:
> >> Hi Ming,
> >>
> >> Ran the above blktests on the current tree, and we end up getting
> >> a hang that we never recover from. There's on request perpetually
> >> stuck:
> >>
> >> root@dell:/sys/kernel/debug/block/nvme0n1/hctx2# cat busy 
> >> 000000005e2b09fe {.op=READ, .cmd_flags=, .rq_flags=DONTPREP|IO_STAT|STATS, .state=in_flight, .tag=313, .internal_tag=-1}
> >>
> >> and no amount of manual running or kicking the queue will bring it
> >> back to life. If I run it on 'master', it works fine.
> >>
> >> Did you run blktests on your series?
> > 
> > Not yet.
> > 
> > Will take a look at it, but this seems related with driver, since
> > the request has been submitted to hardware already.
> 
> It might be, but it repeatedly failed for me on for-linus, and not on
> master. I can try doing some more runs just to gain more confidence.

Looks it is one IO vs CPU hotplug test, which was done before posting.
Not reproduce it on NVMe inside KVM.

Will install a kernel and run it on real HW.

BTW, could you share your lscpu info?

Thanks,
Ming

  reply	other threads:[~2018-04-11  2:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-10 15:51 Hang with blk-mq map series (block/008) Jens Axboe
2018-04-11  2:02 ` Ming Lei
2018-04-11  2:08   ` Jens Axboe
2018-04-11  2:30     ` Ming Lei [this message]
2018-04-11  2:33       ` 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=20180411023059.GE4494@ming.t460p \
    --to=ming.lei@redhat.com \
    --cc=axboe@kernel.dk \
    --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 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.