https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/5789/steps/13/logs/stdio {'mdadm': ['/usr/lib/mdadm/ptest/tests/01replace']} FAIL: /usr/lib/mdadm/ptest/tests/01replace ERROR: dmesg prints errors when testing 01replace! FAILED - see /usr/lib/mdadm/ptest/logs/01replace.log and /usr/lib/mdadm/ptest/logs/fail01replace.log for details dmesg has: [ 171.621016] ------------[ cut here ]------------ [ 171.623595] WARNING: CPU: 0 PID: 3532 at /drivers/md/raid5.c:5236 handle_stripe+0xc84/0x2158 [ 171.625592] Modules linked in: loop [ 171.626528] CPU: 0 PID: 3532 Comm: md0_raid6 Not tainted 6.5.10-yocto-standard #1 [ 171.632726] Hardware name: linux,dummy-virt (DT) [ 171.633969] pstate: 20000005 (nzCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 171.636528] pc : handle_stripe+0xc84/0x2158 [ 171.637720] lr : handle_stripe+0x14a0/0x2158 [ 171.638755] sp : ffffffc089263b70 [ 171.639549] x29: ffffffc089263c00 x28: 0000000000000001 x27: ffffff800576a888 [ 171.641184] x26: ffffff800576ab1c x25: ffffffc089263ca8 x24: 0000000000000003 [ 171.642791] x23: 0000000000000000 x22: 00000000ffffffff x21: ffffff800576a800 [ 171.644440] x20: 0000000000000004 x19: ffffff802a5e4fa0 x18: 000000000000000f [ 171.646062] x17: ffffffbfbea9e000 x16: 0000000000000000 x15: 0000000000000000 [ 171.647674] x14: 0000000000000220 x13: 0000000000000003 x12: 00000000fa83b2da [ 171.649402] x11: 0000000000000000 x10: ffffff802c4766d0 x9 : ffffffc080989328 [ 171.651953] x8 : 0000000000000000 x7 : 0000000000000000 x6 : 0000000000000002 [ 171.653882] x5 : 0000000000400000 x4 : 0000000000000004 x3 : 0000000000200010 [ 171.655590] x2 : ffffff802a5e55b0 x1 : 0000000000000000 x0 : 0000000000200010 [ 171.657324] Call trace: [ 171.658007] handle_stripe+0xc84/0x2158 [ 171.658969] handle_active_stripes.isra.0+0x2f0/0x470 [ 171.660109] raid5d+0x2e0/0x670 [ 171.661214] md_thread+0xac/0x1a8 [ 171.662440] kthread+0x104/0x118 [ 171.663703] ret_from_fork+0x10/0x20 [ 171.664606] ---[ end trace 0000000000000000 ]--- Not sure this is the actual cause
Randy will discuss with co-worker and either get the issue fixed or skip the test or all mdadm ptests even.
https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/5869/steps/12/logs/stdio qemuarm64-ptest ubuntu2204-arm-1
This was {'mdadm': ['/usr/lib/mdadm/ptest/tests/10ddf-fail-stop-readdFAILED_-_see_/usr/lib/mdadm/ptest/logs/10ddf-fail-stop-readd.log_and_/usr/lib/mdadm/ptest/logs/fail10ddf-fail-stop-readd.log_for_details']}
https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/5828/steps/12/logs/stdio qemuarm64-ptest ubuntu2204-arm-1 {'mdadm': ['/usr/lib/mdadm/ptest/tests/13imsm-r0_r0_2d-grow-r0_r0_5dFAILED_-_see_/usr/lib/mdadm/ptest/logs/13imsm-r0_r0_2d-grow-r0_r0_5d.log_and_/usr/lib/mdadm/ptest/logs/fail13imsm-r0_r0_2d-grow-r0_r0_5d.log_for_details']}
Add Ovidiu so he knows what's going on. Pavel is going to disable all the mdadm ptests and try to work to get some of the many patches merged upstream.
https://autobuilder.yoctoproject.org/typhoon/#/builders/81/builds/6105/steps/13/logs/stdio qemux86-64-ptest stream8-ty-1
https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/5776/steps/12/logs/stdio qemuarm64-ptest ubuntu2004-arm-1
https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/5642/steps/12/logs/stdio qemuarm64-ptest ubuntu2204-arm-1
This bug "fixed" by disabling ptests for mdadm [1] Once upstream makes new release we may want to revisit this decisions and re-enable the tests together with cleaning up downstream patches. [1] https://git.openembedded.org/openembedded-core/commit/?id=22ae573aa1a1244d4dea498d4fa4fcdf195bedf8