You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Edit
Kernel aborts mount with "Kernel BUG" traceback when IBT is enabled. Indirect Branch Tracking (IBT) was introduced in kernel 5.18 with 11+ gen Intel CPUs.
A workaround is to set ibt=off kernel parameter.
Compiling with -fcf-protection=branch did not fix.
If this is an upstream issue, feel free to close.
Original text:
I moved my hard drives to a new PC and rebuilt the kernel with the exact same config as before. Got this kernel bug when I tried to mount.
All 3 drives are readable with bcachefs show-super and dd, so they're not broken.
Ya, IBT is the culprit: booting with ibt=off worked.
Similar problem reported here too, maybe we can see how they deal with it: NVIDIA/open-gpu-kernel-modules#256
FlyingWombat
changed the title
kernel BUG at arch/x86/kernel/traps.c:252 [7a90ae891e4a]
IBT support [7a90ae891e4a]
Jul 9, 2022
Edit
Kernel aborts mount with "Kernel BUG" traceback when IBT is enabled. Indirect Branch Tracking (IBT) was introduced in kernel 5.18 with 11+ gen Intel CPUs.
A workaround is to set ibt=off kernel parameter.
Compiling with -fcf-protection=branch did not fix.
If this is an upstream issue, feel free to close.
Original text:
I moved my hard drives to a new PC and rebuilt the kernel with the exact same config as before. Got this kernel bug when I tried to mount.
All 3 drives are readable with bcachefs show-super and dd, so they're not broken.
Dmesg output:
Version
Linux v5.18.10
bcachefs commit 7a90ae8
bcachefs-tools commit bad0c8c50758b4447d529f61017c1a8c85976a3e
Generic info
superblock info:
bcachefs-general-info.txt
system info (that's changed):
cpu: intel i7-12700k (alder lake)
mb: MSI Pro z690-a wifi ddr4
boot drive: nvme-Samsung_SSD_970_EVO_Plus
Building kernel with bcachefs debug options yielded a slightly different call trace:
bcachefs-5.18.10-g7a90ae891e4a-debug-trace.txt
The text was updated successfully, but these errors were encountered: