From: Felix Yan <felixonmars@archlinux.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@kernel.dk>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
Claudio Sampaio <patola@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Regressions <regressions@lists.linux.dev>,
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: Thu, 7 Sep 2023 20:50:06 +0300 [thread overview]
Message-ID: <64c88fce-9745-4dfa-be65-75994b05817f@archlinux.org> (raw)
In-Reply-To: <8af186ba-5f64-2102-8f9c-3969b0906893@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 949 bytes --]
On 9/4/23 14:07, Bagas Sanjaya wrote:
> Hi,
>
> I notice a regression report on Bugzilla [1]. Quoting from it:
>
>> I bought a new 4 TB Lexar NM790 and I was using kernel 6.3.13 at the time. It wasn't recognized, with these messages in dmesg:
>>
>> [ 358.950147] nvme nvme0: pci function 0000:06:00.0
>> [ 358.958327] nvme nvme0: Device not ready; aborting initialisation, CSTS=0x0
Hi,
This looks very much the same as the other MAXIO MAP1602 issue mentioned
in:
https://lore.kernel.org/lkml/7cd693dd-a6d7-4aab-aef0-76a8366ceee6@archlinux.org/
and Lexar NM790 is indeed also using the same controller.
And as I have mentioned there, 6.1 LTS kernels work without a problem
because there are some differences at calculating the resulting timeout
value. Latest kernels including the 6.5.x branch makes the ending result
zero and breaks all 4 TiB SSDs with this controller as far as I know.
--
Regards,
Felix Yan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
prev parent reply other threads:[~2023-09-07 17:50 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
[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 [this message]
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=64c88fce-9745-4dfa-be65-75994b05817f@archlinux.org \
--to=felixonmars@archlinux.org \
--cc=axboe@kernel.dk \
--cc=bagasdotme@gmail.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--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