From: Niklas Cassel <cassel@kernel.org>
To: Salvatore Bonaccorso <carnil@debian.org>
Cc: Mario Limonciello <mario.limonciello@amd.com>,
Christoph Hellwig <hch@infradead.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Damien Le Moal <dlemoal@kernel.org>,
Jian-Hong Pan <jhp@endlessos.org>,
Eric Degenetais <eric.4.debian@grabatoulnz.fr>,
regressions@lists.linux.dev, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, linux-ide@vger.kernel.org,
Dieter Mummenschanz <dmummenschanz@web.de>
Subject: Re: Regression from 7627a0edef54 ("ata: ahci: Drop low power policy board type") on reboot (but not cold boot)
Date: Sun, 2 Mar 2025 20:32:38 +0100 [thread overview]
Message-ID: <Z8SyVnXZ4IPZtgGN@ryzen> (raw)
In-Reply-To: <Z8SBZMBjvVXA7OAK@eldamar.lan>
On Sun, Mar 02, 2025 at 05:03:48PM +0100, Salvatore Bonaccorso wrote:
> Hi Mario et al,
>
> Eric Degenetais reported in Debian (cf. https://bugs.debian.org/1091696) for
> his report, that after 7627a0edef54 ("ata: ahci: Drop low power policy board
> type") rebooting the system fails (but system boots fine if cold booted).
>
> His report mentions that the SSD is not seen on warm reboots anymore.
>
> Does this ring some bell which might be caused by the above bisected[1] commit?
>
> #regzbot introduced: 7627a0edef54
> #regzbot link: https://bugs.debian.org/1091696
>
> What information to you could be helpful to identify the problem?
The model and fw version of the SSD.
Anyway, I found it in the bug report:
Device Model: Samsung SSD 870 QVO 2TB
Firmware Version: SVQ02B6Q
The firmware for this SSD is not great, and has caused us a lot of pain
recently:
https://web.git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/ata?id=cc77e2ce187d26cc66af3577bf896d7410eb25ab
https://lore.kernel.org/linux-ide/Z7xk1LbiYFAAsb9p@ryzen/T/#m831645f6cf2e6b528a8d531fa9b9f929dbf3d602
https://web.git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/ata?id=a2f925a2f62254119cdaa360cfc9c0424bccd531
Basically, older firmware versions for this SSD have broken LPM, but from
user reports, the latest firmware version (which Eric is using) is
apparently working:
https://bugzilla.kernel.org/show_bug.cgi?id=219747
https://lore.kernel.org/stable/93c10d38-718c-459d-84a5-4d87680b4da7@debian.org/
Eric is using the latest SSD fimware version. So from other peoples reports,
I would expect things to work for him as well.
However, no one has reported that their UEFI does not detect their SSD.
This seems to be either SSD firmware bug or UEFI bug.
I would expect your UEFI to send a COMRESET even during a reboot, and a
according to AHCI spec a COMRESET shall take the decide out of sleep states.
Considering that no one else seems to have any problem when using the latest
firmware version for this SSD, this seems to be a problem specific to Eric.
So... UEFI bug?
Have you tried updating your BIOS?
Kind regards,
Niklas
next prev parent reply other threads:[~2025-03-02 19:32 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-02 16:03 Regression from 7627a0edef54 ("ata: ahci: Drop low power policy board type") on reboot (but not cold boot) Salvatore Bonaccorso
2025-03-02 16:20 ` Christian Heusel
2025-03-02 19:28 ` Salvatore Bonaccorso
2025-03-02 19:32 ` Niklas Cassel [this message]
2025-03-02 20:32 ` Eric
2025-03-03 6:25 ` Niklas Cassel
[not found] ` <8b1cbfd4-6877-48ef-b17d-fc10402efbf7@grabatoulnz.fr>
2025-03-03 18:04 ` Eric
2025-03-06 10:37 ` Niklas Cassel
2025-03-06 10:40 ` Niklas Cassel
2025-03-06 12:27 ` Eric
2025-03-07 9:53 ` Niklas Cassel
2025-03-08 10:05 ` Eric
2025-03-08 18:20 ` Eric
2025-03-10 16:24 ` Niklas Cassel
2025-03-17 16:33 ` Mario Limonciello
2025-03-10 9:34 ` Hans de Goede
2025-03-10 18:13 ` Niklas Cassel
2025-03-10 20:12 ` Hans de Goede
2025-03-11 14:14 ` Niklas Cassel
2025-03-12 17:11 ` Eric
2025-03-12 21:39 ` Eric
2025-03-13 12:21 ` Niklas Cassel
2025-03-13 10:04 ` Hans de Goede
2025-03-13 12:48 ` Niklas Cassel
2025-03-13 15:13 ` Hans de Goede
2025-03-13 15:28 ` Niklas Cassel
2025-03-13 18:47 ` Hans de Goede
2025-03-17 17:09 ` Niklas Cassel
2025-03-17 19:15 ` Eric
2025-03-18 0:04 ` Eric
2025-03-18 9:10 ` Niklas Cassel
2025-03-22 19:11 ` Eric
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=Z8SyVnXZ4IPZtgGN@ryzen \
--to=cassel@kernel.org \
--cc=carnil@debian.org \
--cc=dlemoal@kernel.org \
--cc=dmummenschanz@web.de \
--cc=eric.4.debian@grabatoulnz.fr \
--cc=hch@infradead.org \
--cc=jhp@endlessos.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=mika.westerberg@linux.intel.com \
--cc=regressions@lists.linux.dev \
--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