linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: QiuLaibin <qiulaibin@huawei.com>,
	"Alex Xu (Hello71)" <alex_y_xu@yahoo.ca>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	linux-block@vger.kernel.org
Cc: john.garry@huawei.com, ming.lei@redhat.com,
	martin.petersen@oracle.com, hare@suse.de,
	akpm@linux-foundation.org, bvanassche@acm.org,
	linux-kernel@vger.kernel.org
Subject: Re: "blk-mq: fix tag_get wait task can't be awakened" causes hangs
Date: Wed, 26 Jan 2022 06:38:31 -0700	[thread overview]
Message-ID: <723815a5-f716-499a-acce-15028a629f3a@kernel.dk> (raw)
In-Reply-To: <78cafe94-a787-e006-8851-69906f0c2128@huawei.com>

On 1/24/22 9:08 PM, QiuLaibin wrote:
> Hi Alex
> 
> 1、Please help to import this structure:
> 
> blk_mq_tags <= request_queue->blk_mq_hw_ctx->blk_mq_tags
> 
> If there is no kernel dump, help to see the value of
> 
> cat /sys/block/sda/mq/0/nr_tags
>                 __ <= Change it to the problem device
> 
> And how many block devices in total by lsblk.
> 
> 2、Please describe in detail how to reproduce the issue,
> 
> And what type of USB device?
> 
> 3、Please help to try the attachment patch and see if it can be reproduced.

Any progress on this? I strongly suspect that any QD=1 setup would
trivially show the issue, based on the reports.

-- 
Jens Axboe


  parent reply	other threads:[~2022-01-26 13:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1643040870.3bwvk3sis4.none.ref@localhost>
2022-01-24 16:24 ` "blk-mq: fix tag_get wait task can't be awakened" causes hangs Alex Xu (Hello71)
2022-01-25  4:08   ` QiuLaibin
2022-01-25 15:15     ` Alex Xu (Hello71)
2022-01-26 13:38     ` Jens Axboe [this message]
2022-01-27  1:24       ` QiuLaibin
2022-01-25 11:38   ` Daniel Palmer

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=723815a5-f716-499a-acce-15028a629f3a@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=akpm@linux-foundation.org \
    --cc=alex_y_xu@yahoo.ca \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=bvanassche@acm.org \
    --cc=hare@suse.de \
    --cc=john.garry@huawei.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=ming.lei@redhat.com \
    --cc=qiulaibin@huawei.com \
    /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).