From: Niklas Cassel <cassel@kernel.org>
To: Eric <eric.4.debian@grabatoulnz.fr>
Cc: Salvatore Bonaccorso <carnil@debian.org>,
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>,
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: Mon, 3 Mar 2025 07:25:40 +0100 [thread overview]
Message-ID: <Z8VLZERz0FpvpchM@x1-carbon> (raw)
In-Reply-To: <8763ed79-991a-4a19-abb6-599c47a35514@grabatoulnz.fr>
On Sun, Mar 02, 2025 at 09:32:07PM +0100, Eric wrote:
> Hi Niklas,
>
> Le 02/03/2025 à 20:32, Niklas Cassel a écrit :
> > 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).
> > >
> > >
> For what it's worth, before getting these replies I tested the
> ahci.mobile_lpm_policy=1 kernel parameter, which did work around the
> problem.
I'm glad that you have a workaround to make your system usable.
> >
> > 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?
>
> I had not tried to update my bios (bit shy on this due to a problem long ago
> with a power failure during bios update which left me with an unbootable
> machine).
>
> However, as far as I see, there is no newer version of it.
Ok.
So far, this just sounds like a bug where UEFI cannot detect your SSD.
UEFI problems should be reported to your BIOS vendor.
It would be interesting to see if _Linux_ can detect your SSD, after a
reboot, without UEFI involvement.
If you kexec into the same kernel as you are currently running:
https://manpages.debian.org/testing/kexec-tools/kexec.8.en.html
Do you see your SSD in the kexec'd kernel?
Kind regards,
Niklas
next prev parent reply other threads:[~2025-03-03 6:25 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
2025-03-02 20:32 ` Eric
2025-03-03 6:25 ` Niklas Cassel [this message]
[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=Z8VLZERz0FpvpchM@x1-carbon \
--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