lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z8l7paeRL9szo0C0@ryzen>
Date: Thu, 6 Mar 2025 11:40:37 +0100
From: Niklas Cassel <cassel@...nel.org>
To: Eric <eric.4.debian@...batoulnz.fr>
Cc: Salvatore Bonaccorso <carnil@...ian.org>,
	Mario Limonciello <mario.limonciello@....com>,
	Christoph Hellwig <hch@...radead.org>,
	Mika Westerberg <mika.westerberg@...ux.intel.com>,
	Damien Le Moal <dlemoal@...nel.org>,
	Jian-Hong Pan <jhp@...lessos.org>, regressions@...ts.linux.dev,
	linux-kernel@...r.kernel.org, stable@...r.kernel.org,
	linux-ide@...r.kernel.org,
	Dieter Mummenschanz <dmummenschanz@....de>
Subject: Re: Regression from 7627a0edef54 ("ata: ahci: Drop low power policy
 board type") on reboot (but not cold boot)

On Thu, Mar 06, 2025 at 11:37:08AM +0100, Niklas Cassel wrote:
> 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 ?

Sorry, typo:

s/--reuse-cmd/--reuse-cmdline/


Kind regards,
Niklas

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ