From: Jade Lovelace <lists@jade.fyi>
To: Gene <lists@sapience.com>, Ricky WU <ricky_wu@realtek.com>,
Keith Busch <kbusch@kernel.org>,
Thorsten Leemhuis <regressions@leemhuis.info>,
linux-kernel@vger.kernel.org
Cc: regressions@lists.linux.dev, Alyssa Ross <hi@alyssa.is>,
Michal Suchanek <msuchanek@suse.de>,
"axboe @ kernel . dk " <axboe@kernel.dk>,
"sagi @ grimberg . me " <sagi@grimberg.me>,
"linux-nvme @ lists . infradead . org "
<linux-nvme@lists.infradead.org>, "hch@lst.de" <hch@lst.de>,
"arnd@arndb.de" <arnd@arndb.de>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
stable@vger.kernel.org
Subject: [Revert] Re: Possible nvme regression in 6.4.11
Date: Mon, 18 Sep 2023 10:07:38 -0700 [thread overview]
Message-ID: <20230918170831.1677690-2-lists@jade.fyi> (raw)
In-Reply-To: <66bc5229-8131-4111-96fe-bd5ee90314b0@leemhuis.info>
This regression affects all copies of the Dell XPS 15 9560 and Dell Precision
5520 with any SSD including aftermarket ones.
Per the bugzilla discussion here:
https://bugzilla.kernel.org/show_bug.cgi?id=217802 this regression has
been confirmed to also affect 6.5.2 and 6.6-rc1, and affects several
distros.
Known affected branches: 6.1, 6.4, 6.5, 6.6.
It has already been reverted by OpenSUSE and is soon to be reverted in
NixOS. A patch follows, hopefully with the right metadata tags.
I have compiled a kernel 6.1 with the revert and confirmed it now boots
again.
p.s. this is my first time pointing git-send-email at this particular
list, so I'm sorry if I got anything wrong.
Jade
next parent reply other threads:[~2023-09-18 17:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <66bc5229-8131-4111-96fe-bd5ee90314b0@leemhuis.info>
2023-09-18 17:07 ` Jade Lovelace [this message]
2023-09-18 17:07 ` [PATCH] Revert "misc: rtsx: judge ASPM Mode to set PETXCFG Reg" Jade Lovelace
2023-09-18 17:11 ` kernel test robot
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=20230918170831.1677690-2-lists@jade.fyi \
--to=lists@jade.fyi \
--cc=arnd@arndb.de \
--cc=axboe@kernel.dk \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=hi@alyssa.is \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=lists@sapience.com \
--cc=msuchanek@suse.de \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=ricky_wu@realtek.com \
--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