public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
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: Thu, 6 Mar 2025 11:37:08 +0100	[thread overview]
Message-ID: <Z8l61Kxss0bdvAQt@ryzen> (raw)
In-Reply-To: <8b1cbfd4-6877-48ef-b17d-fc10402efbf7@grabatoulnz.fr>

On Mon, Mar 03, 2025 at 03:58:30PM +0100, Eric wrote:
> Hi Niklas
> 
> Le 03/03/2025 à 07:25, Niklas Cassel a écrit :
> > So far, this just sounds like a bug where UEFI cannot detect your SSD.
> Bit it is detected during cold boot, though.
> > UEFI problems should be reported to your BIOS vendor.
> I'll try to see what can be done, however I am not sure how responsive they
> will be for this board...
> > 
> > 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?
> 
> Sorry, I've tried that using several methods (systemctl kexec / kexec --load
> + kexec -e / kexec --load + shutdown --reboot now) and it failed each time.
> I *don't* think it is related to this bug, however, because each time the
> process got stuck just after displaying "kexec_core: Starting new kernel".

I just tired (as root):
# kexec -l /boot/vmlinuz-6.13.5-200.fc41.x86_64 --initrd=/boot/initramfs-6.13.5-200.fc41.x86_64.img --reuse-cmd
# kexec -e

and FWIW, kexec worked fine.

Did you specify an initrd ? did you specify --reuse-cmd ?

If not, please try it.


It would be interesting to see if Linux can detect your SATA drive after
a kexec. If it can't, then we need to report the issue to your drive
vendor (Samsung).


Kind regards,
Niklas

  parent reply	other threads:[~2025-03-06 10:37 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
     [not found]       ` <8b1cbfd4-6877-48ef-b17d-fc10402efbf7@grabatoulnz.fr>
2025-03-03 18:04         ` Eric
2025-03-06 10:37         ` Niklas Cassel [this message]
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=Z8l61Kxss0bdvAQt@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