From: Christoph Hellwig <hch@lst.de>
To: Michael Kropaczek <michael.kropaczek@solidigm.com>
Cc: linux-nvme@lists.infradead.org, Keith Busch <kbusch@kernel.org>,
Jens Axboe <axboe@fb.com>, Christoph Hellwig <hch@lst.de>,
Sagi Grimberg <sagi@grimberg.me>
Subject: Re: [PATCH v2 0/1] nvme: Fix problem when booting from NVMe drive was leading to a hang.
Date: Tue, 5 Mar 2024 14:51:00 +0100 [thread overview]
Message-ID: <20240305135100.GC2063@lst.de> (raw)
In-Reply-To: <20240304182507.2601387-1-michael.kropaczek@solidigm.com>
On Mon, Mar 04, 2024 at 10:25:07AM -0800, Michael Kropaczek wrote:
> Description:
>
> During endurance test, when a system was rebooted from NVMe drive, boot
> process hung occasionally. The number of reboot cycles was set to 1000,
> with interval of 120s. Hang occurred after ~300 reboot cycles.
> After investigating the cause, it was established that NVMe driver
> did not disable host memory during shutdown leaving NVMe controller
> in a state preventing proper initialization in BIOS pre-boot stage.
> Adding of the call to nvme_set_host_mem(dev, 0) when in shutdown
> fixed the issue.
Something odd is going on with your patch submissions, as you seem
to send a single mail with a cover letter and the actual patch.
That's why I missed the last one as I've been waiting for the actual
patch mail which never arrived.
> + /*
> + * On certain host architectures/HW, DRAM was keeping memory contents over reboot-cycles.
> + * It was observed that certain controllers were accessing host memory after
> + * resetting which led to undefined state preventing proper initialization.
> + */
Block comments should never span 80 characters. But more importantly
I don't even think we need this comment at all, this is a clear bug
fix and the code is self-describing.
next prev parent reply other threads:[~2024-03-05 13:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 18:25 [PATCH v2 0/1] nvme: Fix problem when booting from NVMe drive was leading to a hang Michael Kropaczek
2024-03-05 13:51 ` Christoph Hellwig [this message]
2024-03-05 15:17 ` Keith Busch
2024-03-05 17:49 ` Michael Kropaczek
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=20240305135100.GC2063@lst.de \
--to=hch@lst.de \
--cc=axboe@fb.com \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=michael.kropaczek@solidigm.com \
--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 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.