From: Keith Busch <kbusch@kernel.org>
To: Linux regressions mailing list <regressions@lists.linux.dev>
Cc: Bagas Sanjaya <bagasdotme@gmail.com>,
Jens Axboe <axboe@kernel.dk>, Christoph Hellwig <hch@lst.de>,
Sagi Grimberg <sagi@grimberg.me>,
Claudio Sampaio <patola@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux NVMe <linux-nvme@lists.infradead.org>,
Linux Stable <stable@vger.kernel.org>
Subject: Re: Fwd: Lexar NM790 SSDs are not recognized anymore after 6.1.50 LTS
Date: Tue, 5 Sep 2023 09:14:38 -0600 [thread overview]
Message-ID: <ZPdF3uqbJNSZADzv@kbusch-mbp> (raw)
In-Reply-To: <2a379b3a-6ff3-444b-bbad-0fba0bc3a28b@leemhuis.info>
On Tue, Sep 05, 2023 at 04:49:11PM +0200, Linux regression tracking (Thorsten Leemhuis) wrote:
> But what can Claudio do to find the root cause? Check hardware
> (especially the connectors), update firmware, ...? And if that doesn't
> lead to anything, bisect the issue?
Try the current 6.5.1 as-is where the failure was previously seen and
verify if this observation is indeed 100% reproducible with the "device
not ready" kernel message. Full system power cycle between tests, too.
If this is truly a regression, my only guess is some platform power
setting that a newer kernel changed. I am currently suspicious of that
right now since 6.5.1 was reported to fail but succeed with a "quirk"
that doesn't accomplish anything. I'm more leaning toward my "device is
not reliable" theory.
next prev parent reply other threads:[~2023-09-05 15:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 11:07 Fwd: Lexar NM790 SSDs are not recognized anymore after 6.1.50 LTS Bagas Sanjaya
2023-09-05 11:37 ` Linux regression tracking (Thorsten Leemhuis)
2023-09-05 14:35 ` Keith Busch
2023-09-05 14:49 ` Linux regression tracking (Thorsten Leemhuis)
2023-09-05 15:14 ` Keith Busch [this message]
[not found] ` <CA+4wXKCi+idhPQHx3ywdEDHqRmOyBbhz4Gj4gGr_dDvWBWohQQ@mail.gmail.com>
2023-09-05 16:34 ` Keith Busch
2023-09-05 16:44 ` Cláudio Sampaio
2023-09-12 8:08 ` Cláudio Sampaio
2023-09-07 17:50 ` Felix Yan
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=ZPdF3uqbJNSZADzv@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=axboe@kernel.dk \
--cc=bagasdotme@gmail.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=patola@gmail.com \
--cc=regressions@lists.linux.dev \
--cc=sagi@grimberg.me \
--cc=stable@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