Bug 213511 - kernel panic during boot
Summary: kernel panic during boot
Status: RESOLVED CODE_FIX
Alias: None
Product: Drivers
Classification: Unclassified
Component: Platform_x86 (show other bugs)
Hardware: x86-64 Linux
: P1 high
Assignee: Andy Shevchenko
URL: https://lore.kernel.org/lkml/YM77uq51...
Keywords:
Depends on:
Blocks:
 
Reported: 2021-06-20 11:30 UTC by Dominik Brodowski
Modified: 2021-06-29 18:53 UTC (History)
1 user (show)

See Also:
Kernel Version: v5.13-rcX
Subsystem:
Regression: Yes
Bisected commit-id:

Attachments
grep -H 15 /sys/bus/acpi/devices/*/status (883 bytes, text/plain)
2021-06-20 11:30 UTC, Dominik Brodowski 		Details
/proc/iomem (5.38 KB, text/plain)
2021-06-20 11:31 UTC, Dominik Brodowski 		Details
/proc/ioports (1.22 KB, text/plain)
2021-06-20 11:31 UTC, Dominik Brodowski 		Details
lspci -nk -vv (70.43 KB, text/plain)
2021-06-20 11:33 UTC, Dominik Brodowski 		Details
acpidump (1.08 MB, text/plain)
2021-06-20 11:36 UTC, Dominik Brodowski 		Details
dmesg (excerpt) (59.81 KB, text/plain)
2021-06-20 11:40 UTC, Dominik Brodowski 		Details
Add an attachment (proposed patch, testcase, etc.)

Description Dominik Brodowski 2021-06-20 11:30:18 UTC 
Created attachment 297495 [details]
grep -H 15 /sys/bus/acpi/devices/*/status

Kernel panic introduced by patch 42e59982917a ("mfd: core: Add support for software nodes")
Comment 1 Dominik Brodowski 2021-06-20 11:31:23 UTC 
Created attachment 297497 [details]
/proc/iomem
Comment 2 Dominik Brodowski 2021-06-20 11:31:45 UTC 
Created attachment 297499 [details]
/proc/ioports
Comment 3 Dominik Brodowski 2021-06-20 11:33:44 UTC 
Created attachment 297501 [details]
lspci -nk -vv
Comment 4 Dominik Brodowski 2021-06-20 11:36:09 UTC 
Created attachment 297503 [details]
acpidump
Comment 5 Dominik Brodowski 2021-06-20 11:40:24 UTC 
Created attachment 297505 [details]
dmesg (excerpt)

Note that this is a working-kernel, with the problematic patch reverted.
Comment 6 Andy Shevchenko 2021-06-20 16:36:05 UTC 
Is it possible to have like a photo of the screen or other means to have this panic be caught and logged? Perhaps `earlyprintk...` can help here.
Note You need to log in before you can comment on or make changes to this bug.