linux-kernel - Re: [REGRESSION] next boot regression caused by RIP:0010:acpi_find

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <252f883a-6bf1-4ef7-a5f9-d261a6cf725e@leemhuis.info>
Date: Wed, 8 May 2024 13:36:58 +0200
From: "Linux regression tracking (Thorsten Leemhuis)"
 <regressions@...mhuis.info>
To: Laura Nao <laura.nao@...labora.com>, regressions@...ts.linux.dev
Cc: linux-kernel@...r.kernel.org, kernel@...labora.com
Subject: Re: [REGRESSION] next boot regression caused by
 RIP:0010:acpi_find_gpio+0x4b/0x103 kernel panic

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