Messages in this thread | | | From | Laura Nao <> | Subject | [REGRESSION] next boot regression caused by RIP:0010:acpi_find_gpio+0x4b/0x103 kernel panic | Date | Wed, 8 May 2024 14:39:15 +0200 |
| |
Hi Thorsten,
On 5/8/24 13:36, Linux regression tracking (Thorsten Leemhuis) wrote: > 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. >
The issue was detected by the new KernelCI system - there's no web dashboard for it yet, which is why I did not provide a link earlier.
I verified this is still happening on next-20240508 and I already started a bisection, I'll report back when I get the results.
Thanks,
Laura
> 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 > > _______________________________________________ > Kernel mailing list -- kernel@mailman.collabora.com > To unsubscribe send an email to kernel-leave@mailman.collabora.com > This list is managed by https://mailman.collabora.com
| |