We also have clients reporting the same issue: [ 462.430466] RIP: 0010:0x0 [ 462.430499] Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6. [ 462.430532] RSP: 0018:ffffb98d4433f7e8 EFLAGS: 00010206 [ 462.430560] RAX: 0000000000000000 RBX: 0000000000092800 RCX: 0000000000000001 [ 462.430593] RDX: ffff98d23cbc16f0 RSI: 0000000000000000 RDI: 0000000000092800 [ 462.430627] RBP: ffffb98d4433f858 R08: ffff9872f18ccb40 R09: ffff98746e04f050 [ 462.430659] R10: ffff9872cec23000 R11: ffff98730c595c00 R12: 0000000000092c00 [ 462.430692] R13: 0000000000000400 R14: ffff98d23cbc1708 R15: ffff9873d16da080 [ 462.430725] FS: 00007fec39f8e800(0000) GS:ffff98d07fa80000(0000) knlGS:0000000000000000 [ 462.430763] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 462.430791] CR2: ffffffffffffffd6 CR3: 00000002ad60a002 CR4: 00000000007726e0 [ 462.430824] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 462.430856] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 462.430889] PKRU: 55555554 [ 462.430905] Call Trace: [ 462.430921] <TASK> [ 462.430934] mempool_alloc+0x64/0x1b0 [ 462.430966] ? __kmalloc+0x179/0x330 [ 462.430993] bio_alloc_bioset+0x9d/0x370 [ 462.431021] ? r10bio_pool_alloc+0x26/0x30 [raid10] [ 462.431055] bio_clone_fast+0x1f/0x90 [ 462.431078] md_account_bio+0x42/0x80 [ 462.431103] raid10_handle_discard+0x56f/0x6b0 [raid10] [ 462.431137] raid10_make_request+0x147/0x180 [raid10] [ 462.431167] md_handle_request+0x12a/0x1b0 [ 462.431193] ? submit_bio_checks+0x1a5/0x580 [ 462.431221] md_submit_bio+0x76/0xc0 [ 462.431244] __submit_bio+0x1a2/0x220 [ 462.431269] ? __submit_bio_noacct+0x85/0x200 [ 462.431296] __submit_bio_noacct+0x85/0x200 [ 462.431322] submit_bio_noacct+0x4e/0x120 [ 462.431347] ? __cond_resched+0x1a/0x60 [ 462.432356] submit_bio+0x4a/0x130 [ 462.433303] submit_bio_wait+0x5a/0xc0 [ 462.434233] blkdev_issue_discard+0x7e/0xd0 [ 462.435135] xfs_trim_extents+0x1cc/0x3b0 [xfs] [ 462.436237] xfs_ioc_trim+0x19c/0x260 [xfs] [ 462.437274] xfs_file_ioctl+0x7c3/0xb00 [xfs] [ 462.438270] ? perf_syscall_exit+0x18a/0x1a0 [ 462.439066] ? exit_to_user_mode_prepare+0x37/0xb0 [ 462.439836] ? syscall_exit_to_user_mode+0x2c/0x50 [ 462.440589] ? do_syscall_64+0x63/0xb0 [ 462.441130] ? exit_to_user_mode_prepare+0x37/0xb0 [ 462.441443] __x64_sys_ioctl+0x95/0xd0 [ 462.441754] x64_sys_call+0x1e5f/0x1fa0 [ 462.442065] do_syscall_64+0x56/0xb0 [ 462.442367] ? clear_bhb_loop+0x60/0xb0 [ 462.442659] ? clear_bhb_loop+0x60/0xb0 [ 462.442938] ? clear_bhb_loop+0x60/0xb0 [ 462.443210] ? clear_bhb_loop+0x60/0xb0 [ 462.443473] ? clear_bhb_loop+0x60/0xb0 [ 462.443728] entry_SYSCALL_64_after_hwframe+0x6c/0xd6
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2117395 Title: [Regression] kernel 5.15.0-144-generic - discard broken with RAID10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2117395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
