[Kernel-packages] [Bug 2079038] Re: [VROC] [Ub 24.04.0/1] Kernel bug and reboot hang during recovery - missing patch
Ok, so please rebase hwe kernel to the mentioned kernel (6.11-rc4) at least, if possible. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2079038 Title: [VROC] [Ub 24.04.0/1] Kernel bug and reboot hang during recovery - missing patch Status in linux package in Ubuntu: New Bug description: Steps to reproduce: 1. Create RAID array (example for IMSM): mdadm -CR imsm -e imsm -n2 /dev/nvme[01]n1 mdadm -CR vol1 -l1 -n2 /dev/nvme[01]n1 2. Hot-remove one of the drive. 3. Insert drive back - recovery should start. 4. Reboot platform Expected: reboot is performed successfully. Recovery is continued. Actual: reboot hanged and call trace appeared. [ 776.416504] (sd-umoun[3359]: Failed to unmount /run/shutdown/mounts/bd36b757b23bbc6f: Device or resource busy [ 776.445568] shutdown[1]: Could not stop MD /dev/md126: Device or resource busy mdadm: Cannot get exclusive access to /dev/md126:Perhaps a running process, mounted filesystem or active volume group? mdadm: Cannot stop container /dev/md127: member md126 still active mdadm: Cannot get exclusive access to /dev/md126:Perhaps a running process, mounted filesystem or active volume group? mdadm: Cannot st[ 784.636276] (sd-exec-[3360]: /usr/lib/systemd/system-shutdown/mdadm.finalrd failed with exit status 1. op container /dev/md127: member [ 784.647309] shutdown[1]: Unable to finalize remaining file systems, MD devices, ignoring. md126 still active [ 986.549746] INFO: task shutdown:1 blocked for more than 122 seconds. [ 986.556158] Not tainted 6.8.0-31-generic #31-Ubuntu [ 986.561586] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 986.569440] task:shutdownstate:D stack:0 pid:1 tgid:1 ppid:0 flags:0x4002 [ 986.578769] Call Trace: [ 986.581236] [ 986.583352] __schedule+0x27c/0x6b0 [ 986.586864] schedule+0x33/0x110 [ 986.590111] stop_sync_thread+0x135/0x1b0 [ 986.594143] ? __pfx_autoremove_wake_function+0x10/0x10 [ 986.599388] __md_stop_writes+0x19/0xf0 [ 986.603240] md_notify_reboot+0x93/0x160 [ 986.607186] notifier_call_chain+0x5e/0xe0 [ 986.611301] blocking_notifier_call_chain+0x41/0x70 [ 986.616201] kernel_restart+0x21/0xa0 [ 986.619881] __do_sys_reboot+0x156/0x250 [ 986.623824] __x64_sys_reboot+0x1b/0x30 [ 986.627680] x64_sys_call+0x223c/0x25c0 [ 986.631535] do_syscall_64+0x7f/0x180 [ 986.635218] ? irqentry_exit+0x43/0x50 [ 986.638990] ? exc_page_fault+0x94/0x1b0 [ 986.642932] entry_SYSCALL_64_after_hwframe+0x73/0x7b [ 986.648003] RIP: 0033:0x7da6531dea07 [ 986.651623] RSP: 002b:7fff2babce18 EFLAGS: 0246 ORIG_RAX: 00a9 [ 986.659211] RAX: ffda RBX: 0003 RCX: 7da6531dea07 [ 986.666362] RDX: 01234567 RSI: 28121969 RDI: fee1dead [ 986.673509] RBP: 7fff2babd050 R08: 0069 R09: [ 986.680662] R10: R11: 0246 R12: 0001 [ 986.687808] R13: R14: R15: 01234567 [ 986.694956] [ 986.697665] Kernel panic - not syncing: hung_task: blocked tasks [ 986.703732] CPU: 0 PID: 982 Comm: khungtaskd Not tainted 6.8.0-31-generic #31-Ubuntu [ 986.711510] Hardware name: Intel Corporation WilsonCity/WilsonCity, BIOS WLYDCRB1.SYS.0020.P84.2103030140 03/03/2021 [ 986.722061] Call Trace: [ 986.724529] [ 986.726639] dump_stack_lvl+0x48/0x70 [ 986.730326] dump_stack+0x10/0x20 [ 986.733661] panic+0x35f/0x3c0 [ 986.736738] check_hung_uninterruptible_tasks+0x279/0x320 [ 986.742157] ? __pfx_watchdog+0x10/0x10 [ 986.746011] watchdog+0xad/0xb0 [ 986.749164] kthread+0xef/0x120 [ 986.752317] ? __pfx_kthread+0x10/0x10 [ 986.756080] ret_from_fork+0x44/0x70 [ 986.760081] ? __pfx_kthread+0x10/0x10 [ 986.764201] ret_from_fork_asm+0x1b/0x30 [ 986.768473] [ 986.771197] Kernel Offset: 0x1c0 from 0x8100 (relocation range: 0x8000-0xbfff) [ 986.913304] ---[ end Kernel panic - not syncing: hung_task: blocked tasks ]--- This issue is fixed in md. Please apply patch: https://github.com/torvalds/linux/commit/1ddeeb2a058d7b2a58ed9e820396b4ceb715d529 But customer also see other issue and reboot is delayed with this patch (not hanged). I cannot reproduce it on my platform, but I know that newer kernel (6.11-rc4) fixes his all issues. If possible rebase to the 6.11-rc4 (https://kernel.ubuntu.com/mainline/v6.11-rc4/ ) because there all of the customers issues are fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2079038/+subscriptions -- Ma
[Kernel-packages] [Bug 2079038] Re: [VROC] [Ub 24.04.0/1] Kernel bug and reboot hang during recovery - missing patch
Is it possible to fix in Ubuntu 24.04.2? I don't know the process of updating kernel package in next LTS relases. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2079038 Title: [VROC] [Ub 24.04.0/1] Kernel bug and reboot hang during recovery - missing patch Status in linux package in Ubuntu: New Bug description: Steps to reproduce: 1. Create RAID array (example for IMSM): mdadm -CR imsm -e imsm -n2 /dev/nvme[01]n1 mdadm -CR vol1 -l1 -n2 /dev/nvme[01]n1 2. Hot-remove one of the drive. 3. Insert drive back - recovery should start. 4. Reboot platform Expected: reboot is performed successfully. Recovery is continued. Actual: reboot hanged and call trace appeared. [ 776.416504] (sd-umoun[3359]: Failed to unmount /run/shutdown/mounts/bd36b757b23bbc6f: Device or resource busy [ 776.445568] shutdown[1]: Could not stop MD /dev/md126: Device or resource busy mdadm: Cannot get exclusive access to /dev/md126:Perhaps a running process, mounted filesystem or active volume group? mdadm: Cannot stop container /dev/md127: member md126 still active mdadm: Cannot get exclusive access to /dev/md126:Perhaps a running process, mounted filesystem or active volume group? mdadm: Cannot st[ 784.636276] (sd-exec-[3360]: /usr/lib/systemd/system-shutdown/mdadm.finalrd failed with exit status 1. op container /dev/md127: member [ 784.647309] shutdown[1]: Unable to finalize remaining file systems, MD devices, ignoring. md126 still active [ 986.549746] INFO: task shutdown:1 blocked for more than 122 seconds. [ 986.556158] Not tainted 6.8.0-31-generic #31-Ubuntu [ 986.561586] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 986.569440] task:shutdownstate:D stack:0 pid:1 tgid:1 ppid:0 flags:0x4002 [ 986.578769] Call Trace: [ 986.581236] [ 986.583352] __schedule+0x27c/0x6b0 [ 986.586864] schedule+0x33/0x110 [ 986.590111] stop_sync_thread+0x135/0x1b0 [ 986.594143] ? __pfx_autoremove_wake_function+0x10/0x10 [ 986.599388] __md_stop_writes+0x19/0xf0 [ 986.603240] md_notify_reboot+0x93/0x160 [ 986.607186] notifier_call_chain+0x5e/0xe0 [ 986.611301] blocking_notifier_call_chain+0x41/0x70 [ 986.616201] kernel_restart+0x21/0xa0 [ 986.619881] __do_sys_reboot+0x156/0x250 [ 986.623824] __x64_sys_reboot+0x1b/0x30 [ 986.627680] x64_sys_call+0x223c/0x25c0 [ 986.631535] do_syscall_64+0x7f/0x180 [ 986.635218] ? irqentry_exit+0x43/0x50 [ 986.638990] ? exc_page_fault+0x94/0x1b0 [ 986.642932] entry_SYSCALL_64_after_hwframe+0x73/0x7b [ 986.648003] RIP: 0033:0x7da6531dea07 [ 986.651623] RSP: 002b:7fff2babce18 EFLAGS: 0246 ORIG_RAX: 00a9 [ 986.659211] RAX: ffda RBX: 0003 RCX: 7da6531dea07 [ 986.666362] RDX: 01234567 RSI: 28121969 RDI: fee1dead [ 986.673509] RBP: 7fff2babd050 R08: 0069 R09: [ 986.680662] R10: R11: 0246 R12: 0001 [ 986.687808] R13: R14: R15: 01234567 [ 986.694956] [ 986.697665] Kernel panic - not syncing: hung_task: blocked tasks [ 986.703732] CPU: 0 PID: 982 Comm: khungtaskd Not tainted 6.8.0-31-generic #31-Ubuntu [ 986.711510] Hardware name: Intel Corporation WilsonCity/WilsonCity, BIOS WLYDCRB1.SYS.0020.P84.2103030140 03/03/2021 [ 986.722061] Call Trace: [ 986.724529] [ 986.726639] dump_stack_lvl+0x48/0x70 [ 986.730326] dump_stack+0x10/0x20 [ 986.733661] panic+0x35f/0x3c0 [ 986.736738] check_hung_uninterruptible_tasks+0x279/0x320 [ 986.742157] ? __pfx_watchdog+0x10/0x10 [ 986.746011] watchdog+0xad/0xb0 [ 986.749164] kthread+0xef/0x120 [ 986.752317] ? __pfx_kthread+0x10/0x10 [ 986.756080] ret_from_fork+0x44/0x70 [ 986.760081] ? __pfx_kthread+0x10/0x10 [ 986.764201] ret_from_fork_asm+0x1b/0x30 [ 986.768473] [ 986.771197] Kernel Offset: 0x1c0 from 0x8100 (relocation range: 0x8000-0xbfff) [ 986.913304] ---[ end Kernel panic - not syncing: hung_task: blocked tasks ]--- This issue is fixed in md. Please apply patch: https://github.com/torvalds/linux/commit/1ddeeb2a058d7b2a58ed9e820396b4ceb715d529 But customer also see other issue and reboot is delayed with this patch (not hanged). I cannot reproduce it on my platform, but I know that newer kernel (6.11-rc4) fixes his all issues. If possible rebase to the 6.11-rc4 (https://kernel.ubuntu.com/mainline/v6.11-rc4/ ) because there all of the customers issues are fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2079038
[Kernel-packages] [Bug 2079038] [NEW] [VROC] [Ub 24.04.0/1] Kernel bug and reboot hang during recovery - missing patch
Public bug reported: Steps to reproduce: 1. Create RAID array (example for IMSM): mdadm -CR imsm -e imsm -n2 /dev/nvme[01]n1 mdadm -CR vol1 -l1 -n2 /dev/nvme[01]n1 2. Hot-remove one of the drive. 3. Insert drive back - recovery should start. 4. Reboot platform Expected: reboot is performed successfully. Recovery is continued. Actual: reboot hanged and call trace appeared. [ 776.416504] (sd-umoun[3359]: Failed to unmount /run/shutdown/mounts/bd36b757b23bbc6f: Device or resource busy [ 776.445568] shutdown[1]: Could not stop MD /dev/md126: Device or resource busy mdadm: Cannot get exclusive access to /dev/md126:Perhaps a running process, mounted filesystem or active volume group? mdadm: Cannot stop container /dev/md127: member md126 still active mdadm: Cannot get exclusive access to /dev/md126:Perhaps a running process, mounted filesystem or active volume group? mdadm: Cannot st[ 784.636276] (sd-exec-[3360]: /usr/lib/systemd/system- shutdown/mdadm.finalrd failed with exit status 1. op container /dev/md127: member [ 784.647309] shutdown[1]: Unable to finalize remaining file systems, MD devices, ignoring. md126 still active [ 986.549746] INFO: task shutdown:1 blocked for more than 122 seconds. [ 986.556158] Not tainted 6.8.0-31-generic #31-Ubuntu [ 986.561586] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 986.569440] task:shutdownstate:D stack:0 pid:1 tgid:1 ppid:0 flags:0x4002 [ 986.578769] Call Trace: [ 986.581236] [ 986.583352] __schedule+0x27c/0x6b0 [ 986.586864] schedule+0x33/0x110 [ 986.590111] stop_sync_thread+0x135/0x1b0 [ 986.594143] ? __pfx_autoremove_wake_function+0x10/0x10 [ 986.599388] __md_stop_writes+0x19/0xf0 [ 986.603240] md_notify_reboot+0x93/0x160 [ 986.607186] notifier_call_chain+0x5e/0xe0 [ 986.611301] blocking_notifier_call_chain+0x41/0x70 [ 986.616201] kernel_restart+0x21/0xa0 [ 986.619881] __do_sys_reboot+0x156/0x250 [ 986.623824] __x64_sys_reboot+0x1b/0x30 [ 986.627680] x64_sys_call+0x223c/0x25c0 [ 986.631535] do_syscall_64+0x7f/0x180 [ 986.635218] ? irqentry_exit+0x43/0x50 [ 986.638990] ? exc_page_fault+0x94/0x1b0 [ 986.642932] entry_SYSCALL_64_after_hwframe+0x73/0x7b [ 986.648003] RIP: 0033:0x7da6531dea07 [ 986.651623] RSP: 002b:7fff2babce18 EFLAGS: 0246 ORIG_RAX: 00a9 [ 986.659211] RAX: ffda RBX: 0003 RCX: 7da6531dea07 [ 986.666362] RDX: 01234567 RSI: 28121969 RDI: fee1dead [ 986.673509] RBP: 7fff2babd050 R08: 0069 R09: [ 986.680662] R10: R11: 0246 R12: 0001 [ 986.687808] R13: R14: R15: 01234567 [ 986.694956] [ 986.697665] Kernel panic - not syncing: hung_task: blocked tasks [ 986.703732] CPU: 0 PID: 982 Comm: khungtaskd Not tainted 6.8.0-31-generic #31-Ubuntu [ 986.711510] Hardware name: Intel Corporation WilsonCity/WilsonCity, BIOS WLYDCRB1.SYS.0020.P84.2103030140 03/03/2021 [ 986.722061] Call Trace: [ 986.724529] [ 986.726639] dump_stack_lvl+0x48/0x70 [ 986.730326] dump_stack+0x10/0x20 [ 986.733661] panic+0x35f/0x3c0 [ 986.736738] check_hung_uninterruptible_tasks+0x279/0x320 [ 986.742157] ? __pfx_watchdog+0x10/0x10 [ 986.746011] watchdog+0xad/0xb0 [ 986.749164] kthread+0xef/0x120 [ 986.752317] ? __pfx_kthread+0x10/0x10 [ 986.756080] ret_from_fork+0x44/0x70 [ 986.760081] ? __pfx_kthread+0x10/0x10 [ 986.764201] ret_from_fork_asm+0x1b/0x30 [ 986.768473] [ 986.771197] Kernel Offset: 0x1c0 from 0x8100 (relocation range: 0x8000-0xbfff) [ 986.913304] ---[ end Kernel panic - not syncing: hung_task: blocked tasks ]--- This issue is fixed in md. Please apply patch: https://github.com/torvalds/linux/commit/1ddeeb2a058d7b2a58ed9e820396b4ceb715d529 But customer also see other issue and reboot is delayed with this patch (not hanged). I cannot reproduce it on my platform, but I know that newer kernel (6.11-rc4) fixes his all issues. If possible rebase to the 6.11-rc4 (https://kernel.ubuntu.com/mainline/v6.11-rc4/ ) because there all of the customers issues are fixed. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2079038 Title: [VROC] [Ub 24.04.0/1] Kernel bug and reboot hang during recovery - missing patch Status in linux package in Ubuntu: New Bug description: Steps to reproduce: 1. Create RAID array (example for IMSM): mdadm -CR imsm -e imsm -n2 /dev/nvme[01]n1 mdadm -CR vol1 -l1 -n2 /dev/nvme[01]n1 2. Hot-remove one of the drive. 3. Insert drive back - recovery should start. 4. Reboot platform Expected: reboot is performed successfully. Recove
[Kernel-packages] [Bug 2079038] Re: [VROC] [Ub 24.04.0/1] Kernel bug and reboot hang during recovery - missing patch
Please fix in Ubuntu 24.04.1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2079038 Title: [VROC] [Ub 24.04.0/1] Kernel bug and reboot hang during recovery - missing patch Status in linux package in Ubuntu: New Bug description: Steps to reproduce: 1. Create RAID array (example for IMSM): mdadm -CR imsm -e imsm -n2 /dev/nvme[01]n1 mdadm -CR vol1 -l1 -n2 /dev/nvme[01]n1 2. Hot-remove one of the drive. 3. Insert drive back - recovery should start. 4. Reboot platform Expected: reboot is performed successfully. Recovery is continued. Actual: reboot hanged and call trace appeared. [ 776.416504] (sd-umoun[3359]: Failed to unmount /run/shutdown/mounts/bd36b757b23bbc6f: Device or resource busy [ 776.445568] shutdown[1]: Could not stop MD /dev/md126: Device or resource busy mdadm: Cannot get exclusive access to /dev/md126:Perhaps a running process, mounted filesystem or active volume group? mdadm: Cannot stop container /dev/md127: member md126 still active mdadm: Cannot get exclusive access to /dev/md126:Perhaps a running process, mounted filesystem or active volume group? mdadm: Cannot st[ 784.636276] (sd-exec-[3360]: /usr/lib/systemd/system-shutdown/mdadm.finalrd failed with exit status 1. op container /dev/md127: member [ 784.647309] shutdown[1]: Unable to finalize remaining file systems, MD devices, ignoring. md126 still active [ 986.549746] INFO: task shutdown:1 blocked for more than 122 seconds. [ 986.556158] Not tainted 6.8.0-31-generic #31-Ubuntu [ 986.561586] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 986.569440] task:shutdownstate:D stack:0 pid:1 tgid:1 ppid:0 flags:0x4002 [ 986.578769] Call Trace: [ 986.581236] [ 986.583352] __schedule+0x27c/0x6b0 [ 986.586864] schedule+0x33/0x110 [ 986.590111] stop_sync_thread+0x135/0x1b0 [ 986.594143] ? __pfx_autoremove_wake_function+0x10/0x10 [ 986.599388] __md_stop_writes+0x19/0xf0 [ 986.603240] md_notify_reboot+0x93/0x160 [ 986.607186] notifier_call_chain+0x5e/0xe0 [ 986.611301] blocking_notifier_call_chain+0x41/0x70 [ 986.616201] kernel_restart+0x21/0xa0 [ 986.619881] __do_sys_reboot+0x156/0x250 [ 986.623824] __x64_sys_reboot+0x1b/0x30 [ 986.627680] x64_sys_call+0x223c/0x25c0 [ 986.631535] do_syscall_64+0x7f/0x180 [ 986.635218] ? irqentry_exit+0x43/0x50 [ 986.638990] ? exc_page_fault+0x94/0x1b0 [ 986.642932] entry_SYSCALL_64_after_hwframe+0x73/0x7b [ 986.648003] RIP: 0033:0x7da6531dea07 [ 986.651623] RSP: 002b:7fff2babce18 EFLAGS: 0246 ORIG_RAX: 00a9 [ 986.659211] RAX: ffda RBX: 0003 RCX: 7da6531dea07 [ 986.666362] RDX: 01234567 RSI: 28121969 RDI: fee1dead [ 986.673509] RBP: 7fff2babd050 R08: 0069 R09: [ 986.680662] R10: R11: 0246 R12: 0001 [ 986.687808] R13: R14: R15: 01234567 [ 986.694956] [ 986.697665] Kernel panic - not syncing: hung_task: blocked tasks [ 986.703732] CPU: 0 PID: 982 Comm: khungtaskd Not tainted 6.8.0-31-generic #31-Ubuntu [ 986.711510] Hardware name: Intel Corporation WilsonCity/WilsonCity, BIOS WLYDCRB1.SYS.0020.P84.2103030140 03/03/2021 [ 986.722061] Call Trace: [ 986.724529] [ 986.726639] dump_stack_lvl+0x48/0x70 [ 986.730326] dump_stack+0x10/0x20 [ 986.733661] panic+0x35f/0x3c0 [ 986.736738] check_hung_uninterruptible_tasks+0x279/0x320 [ 986.742157] ? __pfx_watchdog+0x10/0x10 [ 986.746011] watchdog+0xad/0xb0 [ 986.749164] kthread+0xef/0x120 [ 986.752317] ? __pfx_kthread+0x10/0x10 [ 986.756080] ret_from_fork+0x44/0x70 [ 986.760081] ? __pfx_kthread+0x10/0x10 [ 986.764201] ret_from_fork_asm+0x1b/0x30 [ 986.768473] [ 986.771197] Kernel Offset: 0x1c0 from 0x8100 (relocation range: 0x8000-0xbfff) [ 986.913304] ---[ end Kernel panic - not syncing: hung_task: blocked tasks ]--- This issue is fixed in md. Please apply patch: https://github.com/torvalds/linux/commit/1ddeeb2a058d7b2a58ed9e820396b4ceb715d529 But customer also see other issue and reboot is delayed with this patch (not hanged). I cannot reproduce it on my platform, but I know that newer kernel (6.11-rc4) fixes his all issues. If possible rebase to the 6.11-rc4 (https://kernel.ubuntu.com/mainline/v6.11-rc4/ ) because there all of the customers issues are fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2079038/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to
[Kernel-packages] [Bug 1960324] Re: [VROC] Kernel does not contain fixes for iostat for md devices
** Changed in: linux-hwe-5.13 (Ubuntu) Status: In Progress => Fix Committed ** Changed in: linux-hwe-5.13 (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1960324 Title: [VROC] Kernel does not contain fixes for iostat for md devices Status in linux package in Ubuntu: Invalid Status in linux-hwe-5.13 package in Ubuntu: Fix Committed Status in linux source package in Focal: Invalid Status in linux-hwe-5.13 source package in Focal: Fix Committed Status in linux source package in Impish: Won't Fix Status in linux-hwe-5.13 source package in Impish: Invalid Bug description: Hello, I noticed that kernel which was used in ubuntu 22.04 (hwe-5.13) does not contain fixes for IO statistics for md devices. IO statistics for md devices were added to kernel 5.10 (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=41d2d848e5c09209bdb57ff9c0ca34075e22783d) but then bug for double fault was reported and this patch was reverted by Guoqing Jiang (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ad3fc798800fb7ca04c1dfc439dba946818048d8). Guoqing Jiang added series of patches which fixes problem and adds IO stats for md devices on top on the revert patch: - first commit from series: 10764815ff4728d2c57da677cd5d3dd6f446cf5f (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=10764815ff4728d2c57da677cd5d3dd6f446cf5f) - last one: de3ea66e9d23a34eef5e17f960d6473f78a1c54b (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=de3ea66e9d23a34eef5e17f960d6473f78a1c54b) I checked that kernel used in ubuntu 22.04 contains only patch with revert - iostat does not report for md devices (https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/log/?h=hwe-5.13&qt=author&q=Guoqing+Jiang) Please consider adding series of patches described above. Regards, Kinga Tanska To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1984117] Re: [VROC] Kernel panic during reshape - probably missing patch
Due to closing our project in Intel, there is no reason to process it. Please close this issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1984117 Title: [VROC] Kernel panic during reshape - probably missing patch Status in linux package in Ubuntu: Confirmed Bug description: Bug found for Jammy (22.04) Steps to reproduce: 1. Create 3 partitions with parted tool on initial non-RAID drive # parted -s /dev/nvme6n1 mklabel gpt # parted -s /dev/nvme6n1 mkpart primary ext4 0% 30% # parted -s /dev/nvme6n1 mkpart primary btrfs 30% 60% # parted -s /dev/nvme6n1 mkpart primary xfs 60% 90% 2. Create filesystem on each partition # mkfs.ext4 /dev/nvme6n1p1 # mkfs.ext4 /dev/nvme6n1p2 # mkfs.ext4 /dev/nvme6n1p3 4. Create RAID container # mdadm --create /dev/md/imsm0 --metadata=imsm --raid-devices=4 /dev/nvme6n1 /dev/nvme4n1 /dev/nvme2n1 /dev/nvme1n1 --run –force 5. Create RAID on drive with data # mdadm --create /dev/md/volume --level=0 --chunk 64 --raid-devices=1 /dev/nvme6n1 --run –force 6. Make sure GPT data structures are in proper place # sgdisk -e /dev/md/volume 7. Grow temporary RAID 0 volume with two devices. Wait for reshape end. # mdadm --grow /dev/md/imsm0 --raid-devices=2 8. Grow temporary RAID 0 to RAID 10 # mdadm --grow /dev/md/volume --level=10 Results: Recovery starts but frozen. Kernel BUG occurs: [ 724.885252] md: recovery of RAID array md126 [ 724.885956] [ cut here ] [ 724.885960] kernel BUG at drivers/md/raid10.c:928! [ 724.891527] invalid opcode: [#1] SMP NOPTI [ 724.896736] CPU: 5 PID: 4872 Comm: md126_resync Not tainted 5.15.0-25-generic #25-Ubuntu [ 724.905943] Hardware name: Intel Corporation ArcherCity/ArcherCity, BIOS EGSDCRB1.SYS.0079.D34.2205030421 05/03/2022 [ 724.917839] RIP: 0010:raise_barrier+0x184/0x190 [raid10] [ 724.923896] Code: 89 f7 e8 4f c6 cf d4 e9 e5 fe ff ff 8b 8f ec 00 00 00 85 c9 74 14 4c 8d a7 dc 00 00 00 4c 89 e7 e8 91 7f 93 d5 e9 c7 fe ff ff <0f> 0b e8 35 9b 92 d5 0f 1f 44 00 00 0f 1f 44 00 00 55 48 89 e5 41 [ 724.945031] RSP: 0018:ff3c62714464fbd8 EFLAGS: 00010246 [ 724.950978] RAX: RBX: ff3282bd578e4c00 RCX: [ 724.959064] RDX: RSI: 0001 RDI: ff3282bd578e4c00 [ 724.967154] RBP: ff3c62714464fc28 R08: ff3282b9cf23ca00 R09: 0001 [ 724.975239] R10: 0293 R11: ff3282bcae577590 R12: ff3282b9cf23ca00 [ 724.983306] R13: 0003 R14: 0080 R15: ff3282bd578e4c00 [ 724.991405] FS: () GS:ff3282bcae54() knlGS: [ 725.000572] CS: 0010 DS: ES: CR0: 80050033 [ 725.007105] CR2: 7f086b758a50 CR3: 44010001 CR4: 00771ee0 [ 725.015209] DR0: DR1: DR2: [ 725.023295] DR3: DR6: fffe07f0 DR7: 0400 [ 725.031391] PKRU: 5554 [ 725.034514] Call Trace: [ 725.037360] [ 725.039787] ? bio_reset+0x12/0x50 [ 725.043721] ? raid10_alloc_init_r10buf+0x6d/0xc0 [raid10] [ 725.049966] raid10_sync_request+0x77c/0x1600 [raid10] [ 725.055832] md_do_sync.cold+0x42c/0xa17 [ 725.060331] md_thread+0xaa/0x160 [ 725.064144] ? md_write_inc+0x50/0x50 [ 725.068350] kthread+0x127/0x150 [ 725.072055] ? set_kthread_struct+0x50/0x50 [ 725.076850] ret_from_fork+0x1f/0x30 [ 725.080963] [ 725.083515] Modules linked in: xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_counter bridge stp llc nf_tables nfnetlink nvme_fabrics intel_rapl_msr intel_rapl_common i10nm_edac nfit x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_realtek snd_hda_codec_generic kvm_intel ledtrig_audio kvm snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec rapl snd_hda_core snd_hwdep snd_pcm snd_timer snd efi_pstore joydev input_leds isst_if_mbox_pci pmt_telemetry idxd pmt_crashlog isst_if_mmio mei_me soundcore pmt_class isst_if_common mei idxd_bus ipmi_ssif acpi_ipmi ipmi_si acpi_power_meter acpi_pad mac_hid sch_fq_codel dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_devintf ipmi_msghandler msr nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor [ 725.083585] async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear dm_mirror dm_region_hash dm_log nvme nvme_core hid_generic usbhid ast i2c_algo_bit hid drm_vram_helper drm_ttm_helper ttm ax88179_178a drm_kms_helper usbnet syscopyarea uas mii sysfillrect usb_storage sysi
[Kernel-packages] [Bug 1970412] Re: [VROC] Ubuntu doesn't support 3rd SATA
Due to closing our project in Intel, there is no reason to process it. Please close this issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1970412 Title: [VROC] Ubuntu doesn't support 3rd SATA Status in linux package in Ubuntu: Confirmed Bug description: An effort has been made to enable 3rd SATA support in kernel, but unfortunately the patch didn't make it to upstream (we are still working to make it happen). Without it certain utility programs cannot function properly when 3rd SATA is engaged. The patch itself adds Intel Emmitsburg PCH RAID PCI IDs to the list of supported controllers. Would you kindly apply this patch to 22.04 release? Patch to be applied: https://lore.kernel.org/linux- ide/20201119104318.79297-1-mika.westerb...@linux.intel.com/ Regards, Lukasz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970412/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1984117] Re: [VROC] Kernel panic during reshape - probably missing patch
Hello, do you have any update on this issue? Thanks, Kinga Tanska -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1984117 Title: [VROC] Kernel panic during reshape - probably missing patch Status in linux package in Ubuntu: Confirmed Bug description: Bug found for Jammy (22.04) Steps to reproduce: 1. Create 3 partitions with parted tool on initial non-RAID drive # parted -s /dev/nvme6n1 mklabel gpt # parted -s /dev/nvme6n1 mkpart primary ext4 0% 30% # parted -s /dev/nvme6n1 mkpart primary btrfs 30% 60% # parted -s /dev/nvme6n1 mkpart primary xfs 60% 90% 2. Create filesystem on each partition # mkfs.ext4 /dev/nvme6n1p1 # mkfs.ext4 /dev/nvme6n1p2 # mkfs.ext4 /dev/nvme6n1p3 4. Create RAID container # mdadm --create /dev/md/imsm0 --metadata=imsm --raid-devices=4 /dev/nvme6n1 /dev/nvme4n1 /dev/nvme2n1 /dev/nvme1n1 --run –force 5. Create RAID on drive with data # mdadm --create /dev/md/volume --level=0 --chunk 64 --raid-devices=1 /dev/nvme6n1 --run –force 6. Make sure GPT data structures are in proper place # sgdisk -e /dev/md/volume 7. Grow temporary RAID 0 volume with two devices. Wait for reshape end. # mdadm --grow /dev/md/imsm0 --raid-devices=2 8. Grow temporary RAID 0 to RAID 10 # mdadm --grow /dev/md/volume --level=10 Results: Recovery starts but frozen. Kernel BUG occurs: [ 724.885252] md: recovery of RAID array md126 [ 724.885956] [ cut here ] [ 724.885960] kernel BUG at drivers/md/raid10.c:928! [ 724.891527] invalid opcode: [#1] SMP NOPTI [ 724.896736] CPU: 5 PID: 4872 Comm: md126_resync Not tainted 5.15.0-25-generic #25-Ubuntu [ 724.905943] Hardware name: Intel Corporation ArcherCity/ArcherCity, BIOS EGSDCRB1.SYS.0079.D34.2205030421 05/03/2022 [ 724.917839] RIP: 0010:raise_barrier+0x184/0x190 [raid10] [ 724.923896] Code: 89 f7 e8 4f c6 cf d4 e9 e5 fe ff ff 8b 8f ec 00 00 00 85 c9 74 14 4c 8d a7 dc 00 00 00 4c 89 e7 e8 91 7f 93 d5 e9 c7 fe ff ff <0f> 0b e8 35 9b 92 d5 0f 1f 44 00 00 0f 1f 44 00 00 55 48 89 e5 41 [ 724.945031] RSP: 0018:ff3c62714464fbd8 EFLAGS: 00010246 [ 724.950978] RAX: RBX: ff3282bd578e4c00 RCX: [ 724.959064] RDX: RSI: 0001 RDI: ff3282bd578e4c00 [ 724.967154] RBP: ff3c62714464fc28 R08: ff3282b9cf23ca00 R09: 0001 [ 724.975239] R10: 0293 R11: ff3282bcae577590 R12: ff3282b9cf23ca00 [ 724.983306] R13: 0003 R14: 0080 R15: ff3282bd578e4c00 [ 724.991405] FS: () GS:ff3282bcae54() knlGS: [ 725.000572] CS: 0010 DS: ES: CR0: 80050033 [ 725.007105] CR2: 7f086b758a50 CR3: 44010001 CR4: 00771ee0 [ 725.015209] DR0: DR1: DR2: [ 725.023295] DR3: DR6: fffe07f0 DR7: 0400 [ 725.031391] PKRU: 5554 [ 725.034514] Call Trace: [ 725.037360] [ 725.039787] ? bio_reset+0x12/0x50 [ 725.043721] ? raid10_alloc_init_r10buf+0x6d/0xc0 [raid10] [ 725.049966] raid10_sync_request+0x77c/0x1600 [raid10] [ 725.055832] md_do_sync.cold+0x42c/0xa17 [ 725.060331] md_thread+0xaa/0x160 [ 725.064144] ? md_write_inc+0x50/0x50 [ 725.068350] kthread+0x127/0x150 [ 725.072055] ? set_kthread_struct+0x50/0x50 [ 725.076850] ret_from_fork+0x1f/0x30 [ 725.080963] [ 725.083515] Modules linked in: xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_counter bridge stp llc nf_tables nfnetlink nvme_fabrics intel_rapl_msr intel_rapl_common i10nm_edac nfit x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_realtek snd_hda_codec_generic kvm_intel ledtrig_audio kvm snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec rapl snd_hda_core snd_hwdep snd_pcm snd_timer snd efi_pstore joydev input_leds isst_if_mbox_pci pmt_telemetry idxd pmt_crashlog isst_if_mmio mei_me soundcore pmt_class isst_if_common mei idxd_bus ipmi_ssif acpi_ipmi ipmi_si acpi_power_meter acpi_pad mac_hid sch_fq_codel dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_devintf ipmi_msghandler msr nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor [ 725.083585] async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear dm_mirror dm_region_hash dm_log nvme nvme_core hid_generic usbhid ast i2c_algo_bit hid drm_vram_helper drm_ttm_helper ttm ax88179_178a drm_kms_helper usbnet syscopyarea uas mii sysfillrect usb_storage sysimgblt crct10dif_
[Kernel-packages] [Bug 1960324] Re: [VROC] Kernel does not contain fixes for iostat for md devices
Thanks for your help. I can confirm that issue is fixed in 5.15. Can be closed now. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1960324 Title: [VROC] Kernel does not contain fixes for iostat for md devices Status in linux package in Ubuntu: Invalid Status in linux-hwe-5.13 package in Ubuntu: In Progress Status in linux source package in Focal: Invalid Status in linux-hwe-5.13 source package in Focal: In Progress Status in linux source package in Impish: Won't Fix Status in linux-hwe-5.13 source package in Impish: Invalid Bug description: Hello, I noticed that kernel which was used in ubuntu 22.04 (hwe-5.13) does not contain fixes for IO statistics for md devices. IO statistics for md devices were added to kernel 5.10 (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=41d2d848e5c09209bdb57ff9c0ca34075e22783d) but then bug for double fault was reported and this patch was reverted by Guoqing Jiang (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ad3fc798800fb7ca04c1dfc439dba946818048d8). Guoqing Jiang added series of patches which fixes problem and adds IO stats for md devices on top on the revert patch: - first commit from series: 10764815ff4728d2c57da677cd5d3dd6f446cf5f (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=10764815ff4728d2c57da677cd5d3dd6f446cf5f) - last one: de3ea66e9d23a34eef5e17f960d6473f78a1c54b (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=de3ea66e9d23a34eef5e17f960d6473f78a1c54b) I checked that kernel used in ubuntu 22.04 contains only patch with revert - iostat does not report for md devices (https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/log/?h=hwe-5.13&qt=author&q=Guoqing+Jiang) Please consider adding series of patches described above. Regards, Kinga Tanska To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986668] Re: [VROC] Kernel does not contain fixes for iostat for md devices
Thanks for your help. I can confirm that issue is fixed in 5.15. Can be closed now. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1986668 Title: [VROC] Kernel does not contain fixes for iostat for md devices Status in linux package in Ubuntu: Invalid Bug description: Hello, I noticed that kernel which was used in ubuntu 22.04 does not contain fixes for IO statistics for md devices. IO statistics for md devices were added to kernel 5.10 (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=41d2d848e5c09209bdb57ff9c0ca34075e22783d) but then bug for double fault was reported and this patch was reverted by Guoqing Jiang (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ad3fc798800fb7ca04c1dfc439dba946818048d8). Guoqing Jiang added series of patches which fixes problem and adds IO stats for md devices on top on the revert patch: - first commit from series: 10764815ff4728d2c57da677cd5d3dd6f446cf5f (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=10764815ff4728d2c57da677cd5d3dd6f446cf5f) - last one: de3ea66e9d23a34eef5e17f960d6473f78a1c54b (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=de3ea66e9d23a34eef5e17f960d6473f78a1c54b) I checked that kernel used in ubuntu 22.04 contains only patch with revert - iostat does not report for md devices (https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/log/?h=hwe-5.13&qt=author&q=Guoqing+Jiang) Please consider adding series of patches described above. Regards, Kinga Tanska To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986668/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960324] Re: [VROC] Kernel does not contain fixes for iostat for md devices
Hello @bladernr, do you have any update of this issue? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1960324 Title: [VROC] Kernel does not contain fixes for iostat for md devices Status in linux package in Ubuntu: Invalid Status in linux-hwe-5.13 package in Ubuntu: In Progress Status in linux source package in Focal: Invalid Status in linux-hwe-5.13 source package in Focal: In Progress Status in linux source package in Impish: Won't Fix Status in linux-hwe-5.13 source package in Impish: Invalid Bug description: Hello, I noticed that kernel which was used in ubuntu 22.04 (hwe-5.13) does not contain fixes for IO statistics for md devices. IO statistics for md devices were added to kernel 5.10 (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=41d2d848e5c09209bdb57ff9c0ca34075e22783d) but then bug for double fault was reported and this patch was reverted by Guoqing Jiang (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ad3fc798800fb7ca04c1dfc439dba946818048d8). Guoqing Jiang added series of patches which fixes problem and adds IO stats for md devices on top on the revert patch: - first commit from series: 10764815ff4728d2c57da677cd5d3dd6f446cf5f (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=10764815ff4728d2c57da677cd5d3dd6f446cf5f) - last one: de3ea66e9d23a34eef5e17f960d6473f78a1c54b (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=de3ea66e9d23a34eef5e17f960d6473f78a1c54b) I checked that kernel used in ubuntu 22.04 contains only patch with revert - iostat does not report for md devices (https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/log/?h=hwe-5.13&qt=author&q=Guoqing+Jiang) Please consider adding series of patches described above. Regards, Kinga Tanska To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960324] Re: [VROC] Kernel does not contain fixes for iostat for md devices
We've installed Ubuntu Kinetic with 5.15 kernel and updated it to 5.19.0-051900 (which was not available in default ubuntu repo, and was taken from here https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.19/amd64/ ). Issue does not occur with this configuration. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1960324 Title: [VROC] Kernel does not contain fixes for iostat for md devices Status in linux package in Ubuntu: Invalid Status in linux-hwe-5.13 package in Ubuntu: In Progress Status in linux source package in Focal: Invalid Status in linux-hwe-5.13 source package in Focal: In Progress Status in linux source package in Impish: Won't Fix Status in linux-hwe-5.13 source package in Impish: Invalid Bug description: Hello, I noticed that kernel which was used in ubuntu 22.04 (hwe-5.13) does not contain fixes for IO statistics for md devices. IO statistics for md devices were added to kernel 5.10 (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=41d2d848e5c09209bdb57ff9c0ca34075e22783d) but then bug for double fault was reported and this patch was reverted by Guoqing Jiang (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ad3fc798800fb7ca04c1dfc439dba946818048d8). Guoqing Jiang added series of patches which fixes problem and adds IO stats for md devices on top on the revert patch: - first commit from series: 10764815ff4728d2c57da677cd5d3dd6f446cf5f (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=10764815ff4728d2c57da677cd5d3dd6f446cf5f) - last one: de3ea66e9d23a34eef5e17f960d6473f78a1c54b (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=de3ea66e9d23a34eef5e17f960d6473f78a1c54b) I checked that kernel used in ubuntu 22.04 contains only patch with revert - iostat does not report for md devices (https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/log/?h=hwe-5.13&qt=author&q=Guoqing+Jiang) Please consider adding series of patches described above. Regards, Kinga Tanska To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986668] Re: [VROC] Kernel does not contain fixes for iostat for md devices
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1986668 Title: [VROC] Kernel does not contain fixes for iostat for md devices Status in linux package in Ubuntu: Confirmed Bug description: Hello, I noticed that kernel which was used in ubuntu 22.04 does not contain fixes for IO statistics for md devices. IO statistics for md devices were added to kernel 5.10 (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=41d2d848e5c09209bdb57ff9c0ca34075e22783d) but then bug for double fault was reported and this patch was reverted by Guoqing Jiang (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ad3fc798800fb7ca04c1dfc439dba946818048d8). Guoqing Jiang added series of patches which fixes problem and adds IO stats for md devices on top on the revert patch: - first commit from series: 10764815ff4728d2c57da677cd5d3dd6f446cf5f (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=10764815ff4728d2c57da677cd5d3dd6f446cf5f) - last one: de3ea66e9d23a34eef5e17f960d6473f78a1c54b (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=de3ea66e9d23a34eef5e17f960d6473f78a1c54b) I checked that kernel used in ubuntu 22.04 contains only patch with revert - iostat does not report for md devices (https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/log/?h=hwe-5.13&qt=author&q=Guoqing+Jiang) Please consider adding series of patches described above. Regards, Kinga Tanska To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986668/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960324] Re: [VROC] Kernel does not contain fixes for iostat for md devices
Ok, sorry, I didn't understand which kernel is used in Jammy correctly. I've opened new bug for 22.04 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986668 . Verification for Kinetic in progress, I will let you know here if issue is reproducible there. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1960324 Title: [VROC] Kernel does not contain fixes for iostat for md devices Status in linux package in Ubuntu: Invalid Status in linux-hwe-5.13 package in Ubuntu: In Progress Status in linux source package in Focal: Invalid Status in linux-hwe-5.13 source package in Focal: In Progress Status in linux source package in Impish: Won't Fix Status in linux-hwe-5.13 source package in Impish: Invalid Bug description: Hello, I noticed that kernel which was used in ubuntu 22.04 (hwe-5.13) does not contain fixes for IO statistics for md devices. IO statistics for md devices were added to kernel 5.10 (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=41d2d848e5c09209bdb57ff9c0ca34075e22783d) but then bug for double fault was reported and this patch was reverted by Guoqing Jiang (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ad3fc798800fb7ca04c1dfc439dba946818048d8). Guoqing Jiang added series of patches which fixes problem and adds IO stats for md devices on top on the revert patch: - first commit from series: 10764815ff4728d2c57da677cd5d3dd6f446cf5f (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=10764815ff4728d2c57da677cd5d3dd6f446cf5f) - last one: de3ea66e9d23a34eef5e17f960d6473f78a1c54b (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=de3ea66e9d23a34eef5e17f960d6473f78a1c54b) I checked that kernel used in ubuntu 22.04 contains only patch with revert - iostat does not report for md devices (https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/log/?h=hwe-5.13&qt=author&q=Guoqing+Jiang) Please consider adding series of patches described above. Regards, Kinga Tanska To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986668] [NEW] [VROC] Kernel does not contain fixes for iostat for md devices
Public bug reported: Hello, I noticed that kernel which was used in ubuntu 22.04 does not contain fixes for IO statistics for md devices. IO statistics for md devices were added to kernel 5.10 (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=41d2d848e5c09209bdb57ff9c0ca34075e22783d) but then bug for double fault was reported and this patch was reverted by Guoqing Jiang (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ad3fc798800fb7ca04c1dfc439dba946818048d8). Guoqing Jiang added series of patches which fixes problem and adds IO stats for md devices on top on the revert patch: - first commit from series: 10764815ff4728d2c57da677cd5d3dd6f446cf5f (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=10764815ff4728d2c57da677cd5d3dd6f446cf5f) - last one: de3ea66e9d23a34eef5e17f960d6473f78a1c54b (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=de3ea66e9d23a34eef5e17f960d6473f78a1c54b) I checked that kernel used in ubuntu 22.04 contains only patch with revert - iostat does not report for md devices (https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/log/?h=hwe-5.13&qt=author&q=Guoqing+Jiang) Please consider adding series of patches described above. Regards, Kinga Tanska ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: vroc ** Description changed: Hello, - I noticed that kernel which was used in ubuntu 22.04 (hwe-5.13) does not - contain fixes for IO statistics for md devices. IO statistics for md - devices were added to kernel 5.10 + I noticed that kernel which was used in ubuntu 22.04 does not contain + fixes for IO statistics for md devices. IO statistics for md devices + were added to kernel 5.10 (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=41d2d848e5c09209bdb57ff9c0ca34075e22783d) but then bug for double fault was reported and this patch was reverted by Guoqing Jiang (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ad3fc798800fb7ca04c1dfc439dba946818048d8). Guoqing Jiang added series of patches which fixes problem and adds IO stats for md devices on top on the revert patch: - first commit from series: 10764815ff4728d2c57da677cd5d3dd6f446cf5f (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=10764815ff4728d2c57da677cd5d3dd6f446cf5f) - last one: de3ea66e9d23a34eef5e17f960d6473f78a1c54b (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=de3ea66e9d23a34eef5e17f960d6473f78a1c54b) I checked that kernel used in ubuntu 22.04 contains only patch with revert - iostat does not report for md devices (https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/log/?h=hwe-5.13&qt=author&q=Guoqing+Jiang) Please consider adding series of patches described above. Regards, Kinga Tanska -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1986668 Title: [VROC] Kernel does not contain fixes for iostat for md devices Status in linux package in Ubuntu: Incomplete Bug description: Hello, I noticed that kernel which was used in ubuntu 22.04 does not contain fixes for IO statistics for md devices. IO statistics for md devices were added to kernel 5.10 (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=41d2d848e5c09209bdb57ff9c0ca34075e22783d) but then bug for double fault was reported and this patch was reverted by Guoqing Jiang (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ad3fc798800fb7ca04c1dfc439dba946818048d8). Guoqing Jiang added series of patches which fixes problem and adds IO stats for md devices on top on the revert patch: - first commit from series: 10764815ff4728d2c57da677cd5d3dd6f446cf5f (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=10764815ff4728d2c57da677cd5d3dd6f446cf5f) - last one: de3ea66e9d23a34eef5e17f960d6473f78a1c54b (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=de3ea66e9d23a34eef5e17f960d6473f78a1c54b) I checked that kernel used in ubuntu 22.04 contains only patch with revert - iostat does not report for md devices (https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/log/?h=hwe-5.13&qt=author&q=Guoqing+Jiang) Please consider adding series of patches described above. Regards, Kinga Tanska To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986668/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1984117] Re: [VROC] Kernel panic during reshape - probably missing patch
Logs are added in description instead of attachment. Changing to confirmed. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1984117 Title: [VROC] Kernel panic during reshape - probably missing patch Status in linux package in Ubuntu: Confirmed Bug description: Bug found for Jammy (22.04) Steps to reproduce: 1. Create 3 partitions with parted tool on initial non-RAID drive # parted -s /dev/nvme6n1 mklabel gpt # parted -s /dev/nvme6n1 mkpart primary ext4 0% 30% # parted -s /dev/nvme6n1 mkpart primary btrfs 30% 60% # parted -s /dev/nvme6n1 mkpart primary xfs 60% 90% 2. Create filesystem on each partition # mkfs.ext4 /dev/nvme6n1p1 # mkfs.ext4 /dev/nvme6n1p2 # mkfs.ext4 /dev/nvme6n1p3 4. Create RAID container # mdadm --create /dev/md/imsm0 --metadata=imsm --raid-devices=4 /dev/nvme6n1 /dev/nvme4n1 /dev/nvme2n1 /dev/nvme1n1 --run –force 5. Create RAID on drive with data # mdadm --create /dev/md/volume --level=0 --chunk 64 --raid-devices=1 /dev/nvme6n1 --run –force 6. Make sure GPT data structures are in proper place # sgdisk -e /dev/md/volume 7. Grow temporary RAID 0 volume with two devices. Wait for reshape end. # mdadm --grow /dev/md/imsm0 --raid-devices=2 8. Grow temporary RAID 0 to RAID 10 # mdadm --grow /dev/md/volume --level=10 Results: Recovery starts but frozen. Kernel BUG occurs: [ 724.885252] md: recovery of RAID array md126 [ 724.885956] [ cut here ] [ 724.885960] kernel BUG at drivers/md/raid10.c:928! [ 724.891527] invalid opcode: [#1] SMP NOPTI [ 724.896736] CPU: 5 PID: 4872 Comm: md126_resync Not tainted 5.15.0-25-generic #25-Ubuntu [ 724.905943] Hardware name: Intel Corporation ArcherCity/ArcherCity, BIOS EGSDCRB1.SYS.0079.D34.2205030421 05/03/2022 [ 724.917839] RIP: 0010:raise_barrier+0x184/0x190 [raid10] [ 724.923896] Code: 89 f7 e8 4f c6 cf d4 e9 e5 fe ff ff 8b 8f ec 00 00 00 85 c9 74 14 4c 8d a7 dc 00 00 00 4c 89 e7 e8 91 7f 93 d5 e9 c7 fe ff ff <0f> 0b e8 35 9b 92 d5 0f 1f 44 00 00 0f 1f 44 00 00 55 48 89 e5 41 [ 724.945031] RSP: 0018:ff3c62714464fbd8 EFLAGS: 00010246 [ 724.950978] RAX: RBX: ff3282bd578e4c00 RCX: [ 724.959064] RDX: RSI: 0001 RDI: ff3282bd578e4c00 [ 724.967154] RBP: ff3c62714464fc28 R08: ff3282b9cf23ca00 R09: 0001 [ 724.975239] R10: 0293 R11: ff3282bcae577590 R12: ff3282b9cf23ca00 [ 724.983306] R13: 0003 R14: 0080 R15: ff3282bd578e4c00 [ 724.991405] FS: () GS:ff3282bcae54() knlGS: [ 725.000572] CS: 0010 DS: ES: CR0: 80050033 [ 725.007105] CR2: 7f086b758a50 CR3: 44010001 CR4: 00771ee0 [ 725.015209] DR0: DR1: DR2: [ 725.023295] DR3: DR6: fffe07f0 DR7: 0400 [ 725.031391] PKRU: 5554 [ 725.034514] Call Trace: [ 725.037360] [ 725.039787] ? bio_reset+0x12/0x50 [ 725.043721] ? raid10_alloc_init_r10buf+0x6d/0xc0 [raid10] [ 725.049966] raid10_sync_request+0x77c/0x1600 [raid10] [ 725.055832] md_do_sync.cold+0x42c/0xa17 [ 725.060331] md_thread+0xaa/0x160 [ 725.064144] ? md_write_inc+0x50/0x50 [ 725.068350] kthread+0x127/0x150 [ 725.072055] ? set_kthread_struct+0x50/0x50 [ 725.076850] ret_from_fork+0x1f/0x30 [ 725.080963] [ 725.083515] Modules linked in: xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_counter bridge stp llc nf_tables nfnetlink nvme_fabrics intel_rapl_msr intel_rapl_common i10nm_edac nfit x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_realtek snd_hda_codec_generic kvm_intel ledtrig_audio kvm snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec rapl snd_hda_core snd_hwdep snd_pcm snd_timer snd efi_pstore joydev input_leds isst_if_mbox_pci pmt_telemetry idxd pmt_crashlog isst_if_mmio mei_me soundcore pmt_class isst_if_common mei idxd_bus ipmi_ssif acpi_ipmi ipmi_si acpi_power_meter acpi_pad mac_hid sch_fq_codel dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_devintf ipmi_msghandler msr nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor [ 725.083585] async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear dm_mirror dm_region_hash dm_log nvme nvme_core hid_generic usbhid ast i2c_algo_bit hid drm_vram_helper drm_ttm_helper ttm ax88179_178a drm_kms_helper usbnet
[Kernel-packages] [Bug 1984117] [NEW] [VROC] Kernel panic during reshape - probably missing patch
Public bug reported: Bug found for Jammy (22.04) Steps to reproduce: 1. Create 3 partitions with parted tool on initial non-RAID drive # parted -s /dev/nvme6n1 mklabel gpt # parted -s /dev/nvme6n1 mkpart primary ext4 0% 30% # parted -s /dev/nvme6n1 mkpart primary btrfs 30% 60% # parted -s /dev/nvme6n1 mkpart primary xfs 60% 90% 2. Create filesystem on each partition # mkfs.ext4 /dev/nvme6n1p1 # mkfs.ext4 /dev/nvme6n1p2 # mkfs.ext4 /dev/nvme6n1p3 4. Create RAID container # mdadm --create /dev/md/imsm0 --metadata=imsm --raid-devices=4 /dev/nvme6n1 /dev/nvme4n1 /dev/nvme2n1 /dev/nvme1n1 --run –force 5. Create RAID on drive with data # mdadm --create /dev/md/volume --level=0 --chunk 64 --raid-devices=1 /dev/nvme6n1 --run –force 6. Make sure GPT data structures are in proper place # sgdisk -e /dev/md/volume 7. Grow temporary RAID 0 volume with two devices. Wait for reshape end. # mdadm --grow /dev/md/imsm0 --raid-devices=2 8. Grow temporary RAID 0 to RAID 10 # mdadm --grow /dev/md/volume --level=10 Results: Recovery starts but frozen. Kernel BUG occurs: [ 724.885252] md: recovery of RAID array md126 [ 724.885956] [ cut here ] [ 724.885960] kernel BUG at drivers/md/raid10.c:928! [ 724.891527] invalid opcode: [#1] SMP NOPTI [ 724.896736] CPU: 5 PID: 4872 Comm: md126_resync Not tainted 5.15.0-25-generic #25-Ubuntu [ 724.905943] Hardware name: Intel Corporation ArcherCity/ArcherCity, BIOS EGSDCRB1.SYS.0079.D34.2205030421 05/03/2022 [ 724.917839] RIP: 0010:raise_barrier+0x184/0x190 [raid10] [ 724.923896] Code: 89 f7 e8 4f c6 cf d4 e9 e5 fe ff ff 8b 8f ec 00 00 00 85 c9 74 14 4c 8d a7 dc 00 00 00 4c 89 e7 e8 91 7f 93 d5 e9 c7 fe ff ff <0f> 0b e8 35 9b 92 d5 0f 1f 44 00 00 0f 1f 44 00 00 55 48 89 e5 41 [ 724.945031] RSP: 0018:ff3c62714464fbd8 EFLAGS: 00010246 [ 724.950978] RAX: RBX: ff3282bd578e4c00 RCX: [ 724.959064] RDX: RSI: 0001 RDI: ff3282bd578e4c00 [ 724.967154] RBP: ff3c62714464fc28 R08: ff3282b9cf23ca00 R09: 0001 [ 724.975239] R10: 0293 R11: ff3282bcae577590 R12: ff3282b9cf23ca00 [ 724.983306] R13: 0003 R14: 0080 R15: ff3282bd578e4c00 [ 724.991405] FS: () GS:ff3282bcae54() knlGS: [ 725.000572] CS: 0010 DS: ES: CR0: 80050033 [ 725.007105] CR2: 7f086b758a50 CR3: 44010001 CR4: 00771ee0 [ 725.015209] DR0: DR1: DR2: [ 725.023295] DR3: DR6: fffe07f0 DR7: 0400 [ 725.031391] PKRU: 5554 [ 725.034514] Call Trace: [ 725.037360] [ 725.039787] ? bio_reset+0x12/0x50 [ 725.043721] ? raid10_alloc_init_r10buf+0x6d/0xc0 [raid10] [ 725.049966] raid10_sync_request+0x77c/0x1600 [raid10] [ 725.055832] md_do_sync.cold+0x42c/0xa17 [ 725.060331] md_thread+0xaa/0x160 [ 725.064144] ? md_write_inc+0x50/0x50 [ 725.068350] kthread+0x127/0x150 [ 725.072055] ? set_kthread_struct+0x50/0x50 [ 725.076850] ret_from_fork+0x1f/0x30 [ 725.080963] [ 725.083515] Modules linked in: xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_counter bridge stp llc nf_tables nfnetlink nvme_fabrics intel_rapl_msr intel_rapl_common i10nm_edac nfit x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_realtek snd_hda_codec_generic kvm_intel ledtrig_audio kvm snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec rapl snd_hda_core snd_hwdep snd_pcm snd_timer snd efi_pstore joydev input_leds isst_if_mbox_pci pmt_telemetry idxd pmt_crashlog isst_if_mmio mei_me soundcore pmt_class isst_if_common mei idxd_bus ipmi_ssif acpi_ipmi ipmi_si acpi_power_meter acpi_pad mac_hid sch_fq_codel dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_devintf ipmi_msghandler msr nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor [ 725.083585] async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear dm_mirror dm_region_hash dm_log nvme nvme_core hid_generic usbhid ast i2c_algo_bit hid drm_vram_helper drm_ttm_helper ttm ax88179_178a drm_kms_helper usbnet syscopyarea uas mii sysfillrect usb_storage sysimgblt crct10dif_pclmul fb_sys_fops crc32_pclmul ghash_clmulni_intel cec rc_core aesni_intel i2c_i801 crypto_simd vmd i2c_smbus intel_pmt i2c_ismt drm cryptd xhci_pci ahci igc libahci xhci_pci_renesas wmi pinctrl_emmitsburg [ 725.230991] ---[ end trace ba2ba247d7919b18 ]--- [ 725.482652] RIP: 0010:raise_barrier+0x184/0x190 [raid10] [ 725.489216] Code: 89 f7 e8 4f c6 cf d4 e9 e5 fe ff ff 8b 8f ec 00 00 00 85 c9 74 14 4c 8d a7 dc 00 00 00 4c 89 e7 e8 91 7f 93 d5 e9 c7 fe ff ff <0f> 0b e8 35 9b 92 d5 0f 1f 44 00 00 0f 1f 44 00 00 55 48 89 e5 41 [
[Kernel-packages] [Bug 1960324] Re: [VROC] Kernel does not contain fixes for iostat for md devices
Hi, Should I submit new bug for Jammy? I don't see this release in this bug, but it should be fixed there too. Kinga Tanska -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1960324 Title: [VROC] Kernel does not contain fixes for iostat for md devices Status in linux package in Ubuntu: Invalid Status in linux-hwe-5.13 package in Ubuntu: In Progress Status in linux source package in Focal: Invalid Status in linux-hwe-5.13 source package in Focal: In Progress Status in linux source package in Impish: Won't Fix Status in linux-hwe-5.13 source package in Impish: Invalid Bug description: Hello, I noticed that kernel which was used in ubuntu 22.04 (hwe-5.13) does not contain fixes for IO statistics for md devices. IO statistics for md devices were added to kernel 5.10 (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=41d2d848e5c09209bdb57ff9c0ca34075e22783d) but then bug for double fault was reported and this patch was reverted by Guoqing Jiang (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ad3fc798800fb7ca04c1dfc439dba946818048d8). Guoqing Jiang added series of patches which fixes problem and adds IO stats for md devices on top on the revert patch: - first commit from series: 10764815ff4728d2c57da677cd5d3dd6f446cf5f (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=10764815ff4728d2c57da677cd5d3dd6f446cf5f) - last one: de3ea66e9d23a34eef5e17f960d6473f78a1c54b (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=de3ea66e9d23a34eef5e17f960d6473f78a1c54b) I checked that kernel used in ubuntu 22.04 contains only patch with revert - iostat does not report for md devices (https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/log/?h=hwe-5.13&qt=author&q=Guoqing+Jiang) Please consider adding series of patches described above. Regards, Kinga Tanska To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960324] Re: [VROC] Kernel does not contain fixes for iostat for md devices
Hi @kamalmostafa, Just to make sure, because task has "in progress" state. Was this fix included into 5.13 kernel used in Ubuntu 22.04? Or will be included in next releases? Regards, Kinga Tanska -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1960324 Title: [VROC] Kernel does not contain fixes for iostat for md devices Status in linux package in Ubuntu: Invalid Status in linux-hwe-5.13 package in Ubuntu: In Progress Status in linux source package in Focal: Invalid Status in linux-hwe-5.13 source package in Focal: In Progress Status in linux source package in Impish: In Progress Status in linux-hwe-5.13 source package in Impish: Invalid Bug description: Hello, I noticed that kernel which was used in ubuntu 22.04 (hwe-5.13) does not contain fixes for IO statistics for md devices. IO statistics for md devices were added to kernel 5.10 (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=41d2d848e5c09209bdb57ff9c0ca34075e22783d) but then bug for double fault was reported and this patch was reverted by Guoqing Jiang (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ad3fc798800fb7ca04c1dfc439dba946818048d8). Guoqing Jiang added series of patches which fixes problem and adds IO stats for md devices on top on the revert patch: - first commit from series: 10764815ff4728d2c57da677cd5d3dd6f446cf5f (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=10764815ff4728d2c57da677cd5d3dd6f446cf5f) - last one: de3ea66e9d23a34eef5e17f960d6473f78a1c54b (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=de3ea66e9d23a34eef5e17f960d6473f78a1c54b) I checked that kernel used in ubuntu 22.04 contains only patch with revert - iostat does not report for md devices (https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/log/?h=hwe-5.13&qt=author&q=Guoqing+Jiang) Please consider adding series of patches described above. Regards, Kinga Tanska To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960324] Re: [VROC] Kernel does not contain fixes for iostat for md devices
Hi, sorry for the delay. I checked test kernel and it works as expected. I think you can submit it. Thanks, Kinga Tanska -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1960324 Title: [VROC] Kernel does not contain fixes for iostat for md devices Status in linux package in Ubuntu: Invalid Status in linux-hwe-5.13 package in Ubuntu: In Progress Status in linux source package in Focal: Invalid Status in linux-hwe-5.13 source package in Focal: In Progress Status in linux source package in Impish: In Progress Status in linux-hwe-5.13 source package in Impish: Invalid Bug description: Hello, I noticed that kernel which was used in ubuntu 22.04 (hwe-5.13) does not contain fixes for IO statistics for md devices. IO statistics for md devices were added to kernel 5.10 (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=41d2d848e5c09209bdb57ff9c0ca34075e22783d) but then bug for double fault was reported and this patch was reverted by Guoqing Jiang (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ad3fc798800fb7ca04c1dfc439dba946818048d8). Guoqing Jiang added series of patches which fixes problem and adds IO stats for md devices on top on the revert patch: - first commit from series: 10764815ff4728d2c57da677cd5d3dd6f446cf5f (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=10764815ff4728d2c57da677cd5d3dd6f446cf5f) - last one: de3ea66e9d23a34eef5e17f960d6473f78a1c54b (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=de3ea66e9d23a34eef5e17f960d6473f78a1c54b) I checked that kernel used in ubuntu 22.04 contains only patch with revert - iostat does not report for md devices (https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/log/?h=hwe-5.13&qt=author&q=Guoqing+Jiang) Please consider adding series of patches described above. Regards, Kinga Tanska To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960324] Re: Kernel does not contain fixes for iostat for md devices
** Tags added: vroc ** Summary changed: - Kernel does not contain fixes for iostat for md devices + [VROC] Kernel does not contain fixes for iostat for md devices -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1960324 Title: [VROC] Kernel does not contain fixes for iostat for md devices Status in linux-hwe-5.13 package in Ubuntu: New Bug description: Hello, I noticed that kernel which was used in ubuntu 22.04 (hwe-5.13) does not contain fixes for IO statistics for md devices. IO statistics for md devices were added to kernel 5.10 (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=41d2d848e5c09209bdb57ff9c0ca34075e22783d) but then bug for double fault was reported and this patch was reverted by Guoqing Jiang (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ad3fc798800fb7ca04c1dfc439dba946818048d8). Guoqing Jiang added series of patches which fixes problem and adds IO stats for md devices on top on the revert patch: - first commit from series: 10764815ff4728d2c57da677cd5d3dd6f446cf5f (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=10764815ff4728d2c57da677cd5d3dd6f446cf5f) - last one: de3ea66e9d23a34eef5e17f960d6473f78a1c54b (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=de3ea66e9d23a34eef5e17f960d6473f78a1c54b) I checked that kernel used in ubuntu 22.04 contains only patch with revert - iostat does not report for md devices (https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/log/?h=hwe-5.13&qt=author&q=Guoqing+Jiang) Please consider adding series of patches described above. Regards, Kinga Tanska To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1960324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960926] [NEW] Installation on RAID volume fails - ubuntu 22.04
Public bug reported: Installation on RAID volume created in uefi fails with error "ValueError: devices or container for raid must be specified". Syslog contains error log with curtin: Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: start: cmd-install/stage-partitioning/builtin/cmd-block-meta: configuring raid: raid-md127 Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: An error occured handling 'raid-md127': ValueError - devices or container for raid must be specified Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: finish: cmd-install/stage-partitioning/builtin/cmd-block-meta: FAIL: configuring raid: raid-md127 Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: TIMED BLOCK_META: 0.647 Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: finish: cmd-install/stage-partitioning/builtin/cmd-block-meta: FAIL: curtin command block-meta Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: Traceback (most recent call last): Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: File "/snap/subiquity/2974/lib/python3.8/site-packages/curtin/commands/main.py", line 202, in main Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: ret = args.func(args) Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: File "/snap/subiquity/2974/lib/python3.8/site-packages/curtin/log.py", line 97, in wrapper Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: return log_time("TIMED %s: " % msg, func, *args, **kwargs) Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: File "/snap/subiquity/2974/lib/python3.8/site-packages/curtin/log.py", line 79, in log_time Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: return func(*args, **kwargs) Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: File "/snap/subiquity/2974/lib/python3.8/site-packages/curtin/commands/block_meta.py", line 117, in block_meta Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: return meta_custom(args) Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: File "/snap/subiquity/2974/lib/python3.8/site-packages/curtin/commands/block_meta.py", line 2024, in meta_custom Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: handler(command, storage_config_dict) Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: File "/snap/subiquity/2974/lib/python3.8/site-packages/curtin/commands/block_meta.py", line 1586, in raid_handler Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: raise ValueError("devices or container for raid must be specified") Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: ValueError: devices or container for raid must be specified Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: devices or container for raid must be specified Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: builtin command failed Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: finish: cmd-install/stage-partitioning/builtin: FAIL: running 'curtin block-meta simple' Jan 20 08:58:16 ubuntu-server curtin_event.4517.3[4968]: finish: cmd-install/stage-partitioning/builtin: FAIL: running 'curtin block-meta simple' Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: builtin took 1.288 seconds Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: stage_partitioning took 1.289 seconds Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: finish: cmd-install/stage-partitioning: FAIL: configuring storage Jan 20 08:58:16 ubuntu-server curtin_event.4517.3[4968]: finish: cmd-install/stage-partitioning: FAIL: configuring storage Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: curtin: Installation failed with exception: Unexpected error while running command. Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: Command: ['curtin', 'block-meta', 'simple'] Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: Exit code: 3 ** Affects: curtin (Ubuntu) Importance: Undecided Status: New ** Tags: vroc ** Description changed: Installation on RAID volume created in uefi fails with error "ValueError: devices or container for raid must be specified". Syslog contains error log with curtin: + Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: start: cmd-install/stage-partitioning/builtin/cmd-block-meta: configuring raid: raid-md127 + Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: An error occured handling 'raid-md127': ValueError - devices or container for raid must be specified + Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: finish: cmd-install/stage-partitioning/builtin/cmd-block-meta: FAIL: configuring raid: raid-md127 + Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: TIMED BLOCK_META: 0.647 Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: finish: cmd-install/stage-partitioning/builtin/cmd-block-meta: FAIL: curtin command block-meta Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: Traceback (most recent call last): Jan 20 08:5
[Kernel-packages] [Bug 1960324] [NEW] Kernel does not contain fixes for iostat for md devices
Public bug reported: Hello, I noticed that kernel which was used in ubuntu 22.04 (hwe-5.13) does not contain fixes for IO statistics for md devices. IO statistics for md devices were added to kernel 5.10 (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=41d2d848e5c09209bdb57ff9c0ca34075e22783d) but then bug for double fault was reported and this patch was reverted by Guoqing Jiang (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ad3fc798800fb7ca04c1dfc439dba946818048d8). Guoqing Jiang added series of patches which fixes problem and adds IO stats for md devices on top on the revert patch: - first commit from series: 10764815ff4728d2c57da677cd5d3dd6f446cf5f (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=10764815ff4728d2c57da677cd5d3dd6f446cf5f) - last one: de3ea66e9d23a34eef5e17f960d6473f78a1c54b (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=de3ea66e9d23a34eef5e17f960d6473f78a1c54b) I checked that kernel used in ubuntu 22.04 contains only patch with revert - iostat does not report for md devices (https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/log/?h=hwe-5.13&qt=author&q=Guoqing+Jiang) Please consider adding series of patches described above. Regards, Kinga Tanska ** Affects: linux-hwe-5.13 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1960324 Title: Kernel does not contain fixes for iostat for md devices Status in linux-hwe-5.13 package in Ubuntu: New Bug description: Hello, I noticed that kernel which was used in ubuntu 22.04 (hwe-5.13) does not contain fixes for IO statistics for md devices. IO statistics for md devices were added to kernel 5.10 (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=41d2d848e5c09209bdb57ff9c0ca34075e22783d) but then bug for double fault was reported and this patch was reverted by Guoqing Jiang (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ad3fc798800fb7ca04c1dfc439dba946818048d8). Guoqing Jiang added series of patches which fixes problem and adds IO stats for md devices on top on the revert patch: - first commit from series: 10764815ff4728d2c57da677cd5d3dd6f446cf5f (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=10764815ff4728d2c57da677cd5d3dd6f446cf5f) - last one: de3ea66e9d23a34eef5e17f960d6473f78a1c54b (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=de3ea66e9d23a34eef5e17f960d6473f78a1c54b) I checked that kernel used in ubuntu 22.04 contains only patch with revert - iostat does not report for md devices (https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/log/?h=hwe-5.13&qt=author&q=Guoqing+Jiang) Please consider adding series of patches described above. Regards, Kinga Tanska To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1960324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp