Received-SPF: pass (google.com: domain of linux-kernel+bounces-173149-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.80.249 as permitted sender) client-ip=147.75.80.249;
Message-ID: <252f883a-6bf1-4ef7-a5f9-d261a6cf725e@leemhuis.info>
Date: Wed, 8 May 2024 13:36:58 +0200
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [REGRESSION] next boot regression caused by
 RIP:0010:acpi_find_gpio+0x4b/0x103 kernel panic
To: Laura Nao <laura.nao@collabora.com>, regressions@lists.linux.dev
Cc: linux-kernel@vger.kernel.org, kernel@collabora.com
References: <20240426154208.81894-1-laura.nao@collabora.com>
From: "Linux regression tracking (Thorsten Leemhuis)"
 <regressions@leemhuis.info>
Content-Language: en-US, de-DE
Reply-To: Linux regressions mailing list <regressions@lists.linux.dev>
In-Reply-To: <20240426154208.81894-1-laura.nao@collabora.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

On 26.04.24 17:42, Laura Nao wrote:
> Hello,
> 
> KernelCI has identified a next boot regression on the following
> Chromebooks, between next-20240416 and next-20240418:
> - Lenovo ThinkPad C13 Yoga Chromebook (codename morphius) - kernel
>   configuration used [1]
> - ASUS Chromebook Flip C436FA (codename helios) - kernel configuration
>   used [2]
>
> [...]
> 
> The issue is still present on next-20240426.
>> #regzbot introduced: next-20240416..next-20240418

Hmmm, I noticed nothing has happened here.

Is this issue still happening? With a link to the particular test in the
CI I might have been able to answer that myself. ;)

If it's still broken I assume we need a bisection.

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 poke