From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (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 CA2CC19BDA for ; Wed, 21 Jun 2023 17:57:46 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id EED07C433C0 for ; Wed, 21 Jun 2023 17:57:45 +0000 (UTC) Authentication-Results: smtp.kernel.org; dkim=pass (1024-bit key) header.d=zx2c4.com header.i=@zx2c4.com header.b="oDTsIIwI" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zx2c4.com; s=20210105; t=1687370263; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Rl4SatZlYW3zfPB8EhfcgRbTfzI6pKWS4+j1IBQgrSM=; b=oDTsIIwIyLRvCLBWHGbhCAQ0jWcHoHSdvBujlFDFYuJ6v+5xf2lo8LmmNSa6WcXBo+svnZ oDttXneIJV1YhbJvmHpzXFCg2Q7f4MepbCwTHn3RDqSaUT6tNzpkM3xlAAaI1uQCUaD8Qh UYajdLj7rLoIc3nykTeUFkMim1+MzVo= Received: by mail.zx2c4.com (ZX2C4 Mail Server) with ESMTPSA id 8f597833 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO) for ; Wed, 21 Jun 2023 17:57:42 +0000 (UTC) Received: by mail-vs1-f46.google.com with SMTP id ada2fe7eead31-440b54708f2so1483865137.0 for ; Wed, 21 Jun 2023 10:57:42 -0700 (PDT) X-Gm-Message-State: AC+VfDyVpJcbETM1NEmBMY++2ezy+cGHGwb9Uk1KTvU9yXSfIwMrlaRa FwWQl4uH/Jy2RQJDqR3HhICe37lIT/HB5tvLMxk= X-Google-Smtp-Source: ACHHUZ53lppsuJRUY2telQU1fgcbJ1amd7Gy3dfz3XBiZB9kGBmv82dqJ5lIE/ByYVNdHEJQPKWfMcJPdfqxchHEuyE= X-Received: by 2002:a05:6102:398:b0:440:a920:dcc4 with SMTP id m24-20020a056102039800b00440a920dcc4mr5969366vsq.22.1687370261715; Wed, 21 Jun 2023 10:57:41 -0700 (PDT) Precedence: bulk X-Mailing-List: regressions@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 References: <9517bb70-426c-0296-b426-f5b4f075f7c8@leemhuis.info> In-Reply-To: <9517bb70-426c-0296-b426-f5b4f075f7c8@leemhuis.info> From: "Jason A. Donenfeld" Date: Wed, 21 Jun 2023 19:57:30 +0200 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [REGRESSION][BISECTED] Boot stall from merge tag 'net-next-6.2' To: regressions@leemhuis.info, Ard Biesheuvel Cc: Andrew Lunn , Linus Torvalds , Linux Stable , Linux Regressions , Bagas Sanjaya , Sami Korkalainen Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable +Ard - any ideas here? On Wed, Jun 21, 2023 at 10:46=E2=80=AFAM Linux regression tracking (Thorste= n Leemhuis) wrote: > > [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 ma= y > > 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/GQUnKz2al3yke5mB2i1kp3SzNHjK8vi6KJEh7rnLrOQ24= OrlljeCyeWveLW9pICEmB9Qc8PKdNt3w1t_g3-Uvxq1l8Wj67PpoMeWDoH8PKk=3D@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=3Doff, 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