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 following kernel panic is reported in the logs:
[ 5.136433] BUG: kernel NULL pointer dereference, address: 0000000000000218
[ 5.143393] #PF: supervisor read access in kernel mode
[ 5.148529] #PF: error_code(0x0000) - not-present page
[ 5.153664] PGD 0 P4D 0
[ 5.156203] Oops: Oops: 0000 [#1] PREEMPT SMP NOPTI
[ 5.161080] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 6.9.0-rc5-next-20240424 #1 a1639945aaee7370a5f0daa79d321d2bc0769584
[ 5.172023] Hardware name: LENOVO Morphius/Morphius, BIOS Google_Morphius.13434.60.0 10/08/2020
[ 5.180714] RIP: 0010:acpi_find_gpio+0x4b/0x103
[ 5.185246] Code: 65 48 8b 04 25 28 00 00 00 48 89 44 24 38 31 c0 48 89 3c 24 e8 24 9a 04 00 48 8b 3c 24 48 8b 74 24 08 84 c0 74 04 48 8d 5f f0 <48> 8b 93 18 02 00 00 48 8d 83 18 02 00 00 31 c9 48 39 c2 75 10 48
[ 5.203988] RSP: 0018:ffffa5a0c0033b98 EFLAGS: 00010246
[ 5.209212] RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffa5a0c0033c24
[ 5.216341] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff8a90c02a5420
[ 5.223470] RBP: ffffa5a0c0033c24 R08: ffffa5a0c0033c28 R09: fffffffffffcc098
[ 5.230599] R10: ffffffff96054f10 R11: fefefefefefefeff R12: ffff8a90c0ba6410
[ 5.237728] R13: ffffa5a0c0033c28 R14: ffffffff95da5d86 R15: 0000000000000000
[ 5.244857] FS: 0000000000000000(0000) GS:ffff8a90eae00000(0000) knlGS:0000000000000000
[ 5.252940] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 5.258684] CR2: 0000000000000218 CR3: 00000000b2a2e000 CR4: 00000000003506f0
[ 5.265813] Call Trace:
[ 5.268262] <TASK>
[ 5.270367] ? __die_body+0x1b/0x5d
[ 5.273861] ? page_fault_oops+0x340/0x3dc
[ 5.277957] ? prb_read_valid+0x14/0x1a
[ 5.281794] ? srso_return_thunk+0x5/0x5f
[ 5.285806] ? console_unlock+0x91/0xc0
[ 5.289644] ? exc_page_fault+0x1e2/0x502
[ 5.293658] ? asm_exc_page_fault+0x22/0x30
[ 5.297846] ? acpi_find_gpio+0x4b/0x103
[ 5.301769] ? acpi_find_gpio+0x3a/0x103
[ 5.305694] ? kvasprintf+0x77/0xba
[ 5.309186] gpiod_find_and_request+0xd5/0x395
[ 5.313634] devm_fwnode_gpiod_get_index+0x76/0xb1
[ 5.318427] gpio_keys_probe+0x43f/0x933
[ 5.322353] ? srso_return_thunk+0x5/0x5f
[ 5.326365] ? acpi_dev_pm_attach+0x96/0xb8
[ 5.330551] ? __device_attach_driver+0x93/0x93
[ 5.335083] platform_probe+0x3e/0x83
[ 5.338748] really_probe+0x111/0x261
[ 5.342411] __driver_probe_device+0xc5/0xf9
[ 5.346683] driver_probe_device+0x1e/0x77
[ 5.350778] __driver_attach+0xce/0xe7
[ 5.354530] bus_for_each_dev+0x7c/0xc2
[ 5.358366] ? kmalloc_trace_noprof+0x150/0x163
[ 5.362897] bus_add_driver+0xf4/0x1e6
[ 5.366650] driver_register+0xa6/0xe8
[ 5.370401] ? atkbd_init+0x26/0x26
[ 5.373892] do_one_initcall+0x80/0x1d9
[ 5.377730] kernel_init_freeable+0x1be/0x206
[ 5.382088] ? rest_init+0xbc/0xbc
[ 5.385491] kernel_init+0x16/0x119
[ 5.388981] ret_from_fork+0x24/0x38
[ 5.392558] ? rest_init+0xbc/0xbc
[ 5.395961] ret_from_fork_asm+0x11/0x20
[ 5.399887] </TASK>
[ 5.402075] Modules linked in:
[ 5.405133] CR2: 0000000000000218
[ 5.408450] ---[ end trace 0000000000000000 ]---
[ 5.413064] RIP: 0010:acpi_find_gpio+0x4b/0x103
[ 5.417592] Code: 65 48 8b 04 25 28 00 00 00 48 89 44 24 38 31 c0 48 89 3c 24 e8 24 9a 04 00 48 8b 3c 24 48 8b 74 24 08 84 c0 74 04 48 8d 5f f0 <48> 8b 93 18 02 00 00 48 8d 83 18 02 00 00 31 c9 48 39 c2 75 10 48
[ 5.436334] RSP: 0018:ffffa5a0c0033b98 EFLAGS: 00010246
[ 5.441558] RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffa5a0c0033c24
[ 5.448687] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff8a90c02a5420
[ 5.455816] RBP: ffffa5a0c0033c24 R08: ffffa5a0c0033c28 R09: fffffffffffcc098
[ 5.462945] R10: ffffffff96054f10 R11: fefefefefefefeff R12: ffff8a90c0ba6410
[ 5.470074] R13: ffffa5a0c0033c28 R14: ffffffff95da5d86 R15: 0000000000000000
[ 5.477203] FS: 0000000000000000(0000) GS:ffff8a90eae00000(0000) knlGS:0000000000000000
[ 5.485286] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 5.491026] CR2: 0000000000000218 CR3: 00000000b2a2e000 CR4: 00000000003506f0
[ 5.498155] Kernel panic - not syncing: Fatal exception
The issue is still present on next-20240426.
Sending this report in order to track the regression while a fix is
identified.
Best,
Laura
[1] https://pastebin.com/raw/C8ZVg4s2
[2] https://pastebin.com/raw/iej1hNWw
#regzbot introduced: next-20240416..next-20240418
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
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 -- [email protected]
> To unsubscribe send an email to [email protected]
> This list is managed by https://mailman.collabora.com