Linux kernel regression status

[next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive]

next-20240416..next-20240418

next boot regression caused by RIP:0010:acpi_find_gpio+0x4b/0x103 kernel panic by Laura Nao

Earliest & latest activity: & . Noteworthy: [1], [2], [resolution].

[1]: [PATCH] gpiolib: acpi: Add ACPI device NULL check to acpi_can_fallback_to_crs() [implicit due to Link/Closes tag]

, by Laura Nao (monitored)

[2]: [PATCH] gpiolib: acpi: Move ACPI device NULL check to acpi_can_fallback_to_crs() [implicit due to Link/Closes tag]

, by Laura Nao (monitored)

Resolution: 4bcc9bba48fa ("gpiolib: acpi: Move ACPI device NULL check to acpi_can_fallback_to_crs()")

in v6.10-rc1

Latest five known activities:

Re: [PATCH] gpiolib: acpi: Move ACPI device NULL check to acpi_can_fallback_to_crs()
, by Stephen Rothwell
Re: [PATCH] gpiolib: acpi: Move ACPI device NULL check to acpi_can_fallback_to_crs()
, by Linux regression tracking (Thorsten Leemhuis)
Commit 4bcc9bba48fa in next
, by Laura Nao
Commit 4bcc9bba48fa in mainline
, by Laura Nao
Re: [PATCH] gpiolib: acpi: Move ACPI device NULL check to acpi_can_fallback_to_crs()
, by Andy Shevchenko

Regzbot command history:

fix: 4bcc9bba48fa [implicit, due to a Link/Closes tag]
, by Laura Nao
note: 4bcc9bba48fa in mainline referred to this regression
, by Laura Nao
relate: https://lore.kernel.org/lkml/20240513095610.216668-1-laura.nao@collabora.com/ [PATCH] gpiolib: acpi: Move ACPI device NULL check to acpi_can_fallback_to_crs() [implicit due to Link/Closes tag]
, by Laura Nao
relate: https://lore.kernel.org/lkml/20240509104605.538274-1-laura.nao@collabora.com/ [PATCH] gpiolib: acpi: Add ACPI device NULL check to acpi_can_fallback_to_crs() [implicit due to Link/Closes tag]
, by Laura Nao
poke
, by Linux regression tracking (Thorsten Leemhuis)
introduced: next-20240416..next-20240418
, by Laura Nao

next

[compiled by regzbot on 2026-07-18 07:54:22 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

[recently 93 events occurred that regzbot was unable to handle]