From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from wp530.webpack.hosteurope.de (wp530.webpack.hosteurope.de [80.237.130.52]) (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 5C2408BF8 for ; Wed, 21 Jun 2023 08:47:00 +0000 (UTC) Received: from [2a02:8108:8980:2478:8cde:aa2c:f324:937e]; authenticated by wp530.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) id 1qBtUO-0002iS-5L; Wed, 21 Jun 2023 10:46:56 +0200 Message-ID: <9517bb70-426c-0296-b426-f5b4f075f7c8@leemhuis.info> Date: Wed, 21 Jun 2023 10:46:54 +0200 Precedence: bulk X-Mailing-List: regressions@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.12.0 Subject: Re: [REGRESSION][BISECTED] Boot stall from merge tag 'net-next-6.2' Content-Language: en-US, de-DE To: "Jason A. Donenfeld" Cc: Andrew Lunn , Linus Torvalds , Linux Stable , Linux Regressions , Bagas Sanjaya , Sami Korkalainen References: From: "Linux regression tracking (Thorsten Leemhuis)" Reply-To: Linux regressions mailing list In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-bounce-key: webpack.hosteurope.de;regressions@leemhuis.info;1687337220;beb854b2; X-HE-SMSGID: 1qBtUO-0002iS-5L [added Jason (who authored the culprit) to the list of recipients; moved net people and list to BCC, guess they are not much interested in this anymore then] On 21.06.23 08:07, Sami Korkalainen wrote: > I bisected again. It seems I made some mistake last time, as I got a > different result this time. Maybe, because these problematic kernels may > boot fine sometimes, like I said before. > > Anyway, first bad commit (makes much more sense this time): > e7b813b32a42a3a6281a4fd9ae7700a0257c1d50 efi: random: refresh > non-volatile random seed when RNG is initialized > > I confirmed that this is the code causing the issue by commenting it > out (see the patch file). Without this code, the latest mainline boots fine. Jason, in that case it seems this is something for you. For the initial report, see here: https://lore.kernel.org/all/GQUnKz2al3yke5mB2i1kp3SzNHjK8vi6KJEh7rnLrOQ24OrlljeCyeWveLW9pICEmB9Qc8PKdNt3w1t_g3-Uvxq1l8Wj67PpoMeWDoH8PKk=@proton.me/ Quoting a part of it: ``` Linux 6.2 and newer are (mostly) unbootable on my old HP 6730b laptop, the 6.1.30 works still fine. The weirdest thing is that newer kernels (like 6.3.4 and 6.4-rc3) may boot ok on the first try, but when rebooting, the very same version doesn't boot. Some times, when trying to boot, I get this message repeated forever: ACPI Error: No handler or method for GPE [XX], disabling event (20221020/evgpe-839) On newer kernels, the date is 20230331 instead of 20221020. There is also some other error, but I can't read it as it gets overwritten by the other ACPI error, see image linked at the end. And some times, the screen will just stay completely blank. I tried booting with acpi=off, but it does not help. ``` Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) -- Everything you wanna know about Linux kernel regression tracking: https://linux-regtracking.leemhuis.info/about/#tldr If I did something stupid, please tell me, as explained on that page. #regzbot introduced e7b813b32a42a3a6281a4fd9ae7700a0257c1d50