Looking at the full dmesg the first thing off that I see is this:
34539.429634] ------------[ cut here ]------------
[34539.429635] UBSAN: shift-out-of-bounds in /build/linux-vCyKs5/linux-6.8.0/fs/ufs/super.c:1247:19
[34539.429637] shift exponent 36 is too large for 32-bit type 'int'
[34539.429639] CPU: 7 PID: 29594 Comm: mount Tainted: P O 6.8.0-51-generic #52-Ubuntu
[34539.429641] Hardware name: Gigabyte Technology Co., Ltd. Z390 AORUS PRO/Z390 AORUS PRO-CF, BIOS F12g GA9 06/08/2020
[34539.429642] Call Trace:
[34539.429644] <TASK>
[34539.429646] dump_stack_lvl+0x76/0xa0
[34539.429649] dump_stack+0x10/0x20
[34539.429650] __ubsan_handle_shift_out_of_bounds+0x199/0x370
[34539.429654] ufs_fill_super.cold+0x16/0x1b7 [ufs]
[34539.429658] ? sb_set_blocksize+0x1d/0x70
[34539.429682] ? __pfx_ufs_fill_super+0x10/0x10 [ufs]
[34539.429685] mount_bdev+0xf3/0x140
[34539.429688] ufs_mount+0x15/0x30 [ufs]
[34539.429711] legacy_get_tree+0x28/0x60
[34539.429714] vfs_get_tree+0x27/0x100
[34539.429716] do_new_mount+0x1a0/0x340
[34539.429718] path_mount+0x1e0/0x830
[34539.429719] ? putname+0x5b/0x80
[34539.429721] __x64_sys_mount+0x127/0x160
[34539.429723] x64_sys_call+0x1e57/0x25a0
[34539.429725] do_syscall_64+0x7f/0x180
[34539.429728] ? put_fs_context+0xff/0x1c0
[34539.429730] ? do_new_mount+0x10d/0x340
[34539.429731] ? rseq_get_rseq_cs+0x22/0x280
[34539.429753] ? rseq_ip_fixup+0x90/0x1f0
[34539.429755] ? syscall_exit_to_user_mode+0x86/0x260
[34539.429757] ? do_syscall_64+0x8c/0x180
[34539.429758] ? do_faccessat+0x1c2/0x2f0
[34539.429780] ? syscall_exit_to_user_mode+0x86/0x260
[34539.429782] ? do_syscall_64+0x8c/0x180
[34539.429783] ? __do_sys_newfstatat+0x53/0x90
[34539.429786] ? syscall_exit_to_user_mode+0x86/0x260
[34539.429787] ? do_syscall_64+0x8c/0x180
[34539.429807] ? syscall_exit_to_user_mode+0x86/0x260
[34539.429809] ? do_syscall_64+0x8c/0x180
[34539.429810] ? irqentry_exit_to_user_mode+0x7b/0x260
[34539.429812] ? irqentry_exit+0x43/0x50
[34539.429813] ? clear_bhb_loop+0x15/0x70
[34539.429815] ? clear_bhb_loop+0x15/0x70
[34539.429816] ? clear_bhb_loop+0x15/0x70
[34539.429817] entry_SYSCALL_64_after_hwframe+0x78/0x80
[34539.429819] RIP: 0033:0x7689eff2af0e
[34539.429838] Code: 48 8b 0d 0d 7f 0d 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d da 7e 0d 00 f7 d8 64 89 01 48
[34539.429839] RSP: 002b:00007ffd8f391668 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
[34539.429841] RAX: ffffffffffffffda RBX: 0000575a9b52abe0 RCX: 00007689eff2af0e
[34539.429842] RDX: 0000575a9b52b070 RSI: 0000575a9b52b0b0 RDI: 0000575a9b52b090
[34539.429843] RBP: 00007ffd8f3916d0 R08: 0000575a9b52be30 R09: 0000000000000007
[34539.429844] R10: 0000000000000001 R11: 0000000000000246 R12: 0000575a9b52b090
[34539.429845] R13: 0000575a9b52b0b0 R14: 0000575a9b52b070 R15: 0000575a9b52ad40
[34539.429846] </TASK>
[34539.429847] ---[ end trace ]---
There is a launchpad bug for this, so people are working to fix it.
This is followed immediately by
[35018.100057] ufs: error (device sdc2): ufs_check_page: bad entry in directory #19957332: rec_len is smaller than minimal - offset=512, rec_len=0, name_len=0
[35018.100082] ufs: error (device sdc2): ufs_readdir: bad page in #19957332
which indicates that your ufs has corruption, or that the bug above induces appearance of corruption.
Do you have a UFS partition that you are trying to mount ? Try to boot without mounting it.
Launchpad bug link:
[ Impact ] UBSAN shift-out-of-bounds warning appears on system when some UFS filesystems are mounted. [ Test Plan ] Mount the UFS partition with the proposed kernel and verify that the warning is gone. [ Where problems could occur ] Should have zero impact, removes dead code. [ Original...
bugs.launchpad.net