lkml.org 
[lkml]   [2024]   [May]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: [REGRESSION] next boot regression caused by RIP:0010:acpi_find_gpio+0x4b/0x103 kernel panic
From
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


\
 
 \ /
  Last update: 2024-05-08 13:37    [W:0.025 / U:0.608 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site