public inbox for linux-nvme@lists.infradead.org
 help / color / mirror / Atom feed
From: Jonathan Derrick <jonathan.derrick@linux.dev>
To: Sagi Grimberg <sagi@grimberg.me>, Keith Busch <kbusch@fb.com>,
	hch@lst.de, linux-nvme@lists.infradead.org
Subject: Re: Resets during user commands leads to hung task and controller stuck in connecting
Date: Mon, 14 Nov 2022 16:09:08 -0700	[thread overview]
Message-ID: <65816415-303d-5579-4878-d8cba766f797@linux.dev> (raw)
In-Reply-To: <1ffea25b-6f67-a1e6-5b96-22bf3b4d89ec@grimberg.me>



On 11/13/2022 4:03 AM, Sagi Grimberg wrote:
> 
> 
> On 11/11/22 23:50, Jonathan Derrick wrote:
>> Hi,
>>
>> I'm (again) seeing a hung task when doing resets and formats simultaneously.
>> Controller state is left in 'connecting'
>>
>> Using nvme.git/nvme-6.2 as of 'nvme: implement the DEAC bit for the Write Zeroes command',
>> but I have also repro'd with Christoph's latest reset/probe-split set
>>
>>
>> ctrl="nvme0"
>> nsid=1
>> pci="/sys/block/${ctrl}n${nsid}/device/"
>> echo 30 > /proc/sys/kernel/hung_task_timeout_secs
>> while true; do
>>          nvme format -f /dev/${ctrl}n${nsid} &
> 
> How long to it take the format to complete?
Well it's pretty immediate but I'm under the impression that the
nvme_dev_disable path leads to CC_EN disabling, interrupting any formats

> 
>>          echo 1 > $pci/reset_controller &
>> done
> 
> What happens if you set io_timeout to 20 instead of 30? (given
> that you bound hung tasks at 30 seconds...
It occurs with the standard 120s task timeout too
Also there's no I/O occurring at the moment; just admin work

I added a blktests for this:
http://lists.infradead.org/pipermail/linux-nvme/2022-November/036475.html


  reply	other threads:[~2022-11-14 23:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-11 21:50 Resets during user commands leads to hung task and controller stuck in connecting Jonathan Derrick
2022-11-13 11:03 ` Sagi Grimberg
2022-11-14 23:09   ` Jonathan Derrick [this message]
2022-11-15  7:46     ` Sagi Grimberg
2022-11-15 16:34       ` Keith Busch

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=65816415-303d-5579-4878-d8cba766f797@linux.dev \
    --to=jonathan.derrick@linux.dev \
    --cc=hch@lst.de \
    --cc=kbusch@fb.com \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    /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