From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out-173.mta0.migadu.com (out-173.mta0.migadu.com [91.218.175.173]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id A0DEF1F9A83 for ; Tue, 14 Jan 2025 13:16:15 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=91.218.175.173 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1736860580; cv=none; b=UvvcMIEAti4RZLH3Ii3FuD88MV1ckBZbxjI2CiqxDB2T+Mh7dmEp7G7zyq2x3j9GwOVlGGgZSlp+G/b3EZypdHYTBG7c3v5tGSodjHyVhVcVsxfo9hkzgp0r5bCK7ZXvCThFFVcYxtXHv+pu76qGrASlQZeOkmvs2RvVrdZpPOU= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1736860580; c=relaxed/simple; bh=yJ6+iSSlxlpXZF5d9b9jgHbAMnHYxtVOIx+qxoE1WB8=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=noQlGXcnQ7bzD5U0N4A642qRKRnhe1aE+Af/xSslJWwaXEsHXymhYxoXxzHj/Dpuk5IBLerDMr1slMywlnWDIouwTsljc8HbkqdrhcdeHe5voPv+t4dXcKjkBPD3+l1BDddJ9XP8ZX/06zisDSKKQR5tHIM7zrBbYKfib1iAxFM= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=r-ricci.it; spf=pass smtp.mailfrom=r-ricci.it; dkim=pass (2048-bit key) header.d=r-ricci.it header.i=@r-ricci.it header.b=Imheh64u; arc=none smtp.client-ip=91.218.175.173 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=r-ricci.it Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=r-ricci.it Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=r-ricci.it header.i=@r-ricci.it header.b="Imheh64u" Date: Tue, 14 Jan 2025 14:16:10 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=r-ricci.it; s=key1; t=1736860573; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=GmRf/WPiVxAimIYsZVKC5WhgZrbd93EcpRocS2JRKMg=; b=Imheh64uhV65zTPsP5pL+DbNtlZOJIhz+GWVcf5nzPFNmx/tWaRo5XbKBF7mX+jOMSCxb4 zLymQF9ATUH7J5YuJv1Zowpwh/vopW4juRzuU8VH4u3IgG0YgWJifClm2xS8jGZFBfsr1+ a+0EG5VeFVD353yOZHrpYWSzcVs1kK7NT74Vom0rCh5hhm6FrV80GxkuA6jcBgY/iEYP1o oPXlB0+P3JelpTPDz30zRyDmEIXMmlTBWdBiApL5mgWtFPWQvqOKhNFpLBPrfIqdzJrlSM 9f2qoRDFwcxUwzu7TspBcjq0of6b/QG9Gh65B2HVZ67e3EWYhut8xzzStCggUA== X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Roberto Ricci To: ebiederm@xmission.com, rafael@kernel.org, pavel@ucw.cz, ytcoode@gmail.com Cc: kexec@lists.infradead.org, linux-pm@vger.kernel.org, akpm@linux-foundation.org, regressions@lists.linux.dev, linux-kernel@vger.kernel.org Subject: Re: [REGRESSION] Kernel booted via kexec fails to resume from hibernation Message-ID: References: Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Migadu-Flow: FLOW_OUT On 2025-01-13 Mon 22:28:48 +0100, Roberto Ricci wrote: > I can reproduce this with kernel 6.13-rc7 in a qemu x86_64 virtual machine > running Void Linux, with the following commands: > > ``` > # kexec -l /boot/vmlinuz-6.13.0-rc7 --initrd=/boot/initramfs-6.13.0-rc7 --reuse-cmdline > # reboot > # printf reboot >/sys/power/disk > # printf disk >/sys/power/state > ``` Looks like it's the kernel performing the kexec which causes the issue, not the target one. E.g.: kexec-ing 6.7 from 6.13-rc7 makes resume from hibernation fail; but if I kexec 6.13-rc7 from 6.7, then it works fine.