clk_imx8mp_audiomix_runtime_resume Kernel panic regression on v6.12
Subsystems (2)
Hello,
it seems that an old regression is back on v6.12, reproduced on -rc2 (not sure about rc1).
The original report is from https://lore.kernel.org/all/20240424164725.GA18760@francesco-nb/
and it was fixed with https://lore.kernel.org/all/[email protected]/.
Is it now back?
[ 4.012850] SError Interrupt on CPU2, code 0x00000000bf000002 -- SError [ 4.012862] CPU: 2 UID: 0 PID: 186 Comm: (udev-worker) Not tainted 6.12.0-rc2-0.0.0-devel-00004-g8b1b79e88956 #1 [ 4.012869] Hardware name: Toradex Verdin iMX8M Plus WB on Dahlia Board (DT) [ 4.012872] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 4.012877] pc : clk_imx8mp_audiomix_runtime_resume+0x38/0x48 [ 4.012891] lr : pm_generic_runtime_resume+0x2c/0x44 [ 4.012897] sp : ffff8000821cb740 [ 4.012899] x29: ffff8000821cb740 x28: ffff8000793c48d8 x27: ffff8000793c48c0 [ 4.012908] x26: ffff0000c0ec90f4 x25: 0000000000000000 x24: 0000000000000000 [ 4.012916] x23: 0000000000000000 x22: ffff0000c1bef180 x21: 0000000000000000 [ 4.012923] x20: ffff0000c0a73000 x19: ffff0000c0ecbc10 x18: ffffffffffffffff [ 4.012930] x17: 3030303064623033 x16: 2f7375622e303030 x15: 756e285472656c6c [ 4.012937] x14: ffff800081267458 x13: 6d692c6c73664361 x12: 0000000000000000 [ 4.012944] x11: 00353333333d4d55 x10: ffff8000818020ae x9 : 0000000000000008 [ 4.012951] x8 : 0000000000000008 x7 : 0000000000000000 x6 : ffff0000c5bf2080 [ 4.012958] x5 : ffff800081f10000 x4 : ffff800080c182e8 x3 : ffff0000c0ee7088 [ 4.012965] x2 : 0000000000000000 x1 : 0000000000000004 x0 : ffff800081f10300 [ 4.012973] Kernel panic - not syncing: Asynchronous SError Interrupt [ 4.012976] CPU: 2 UID: 0 PID: 186 Comm: (udev-worker) Not tainted 6.12.0-rc2-0.0.0-devel-00004-g8b1b79e88956 #1 [ 4.012982] Hardware name: Toradex Verdin iMX8M Plus WB on Dahlia Board (DT) [ 4.012985] Call trace: [ 4.012988] dump_backtrace+0xd0/0x120 [ 4.012998] show_stack+0x18/0x24 [ 4.013005] dump_stack_lvl+0x60/0x80 [ 4.013013] dump_stack+0x18/0x24 [ 4.013019] panic+0x168/0x350 [ 4.013025] add_taint+0x0/0xbc [ 4.013029] arm64_serror_panic+0x64/0x70 [ 4.013034] do_serror+0x3c/0x70 [ 4.013039] el1h_64_error_handler+0x30/0x54 [ 4.013046] el1h_64_error+0x64/0x68 [ 4.013050] clk_imx8mp_audiomix_runtime_resume+0x38/0x48 [ 4.013059] __genpd_runtime_resume+0x30/0x80 [ 4.013066] genpd_runtime_resume+0x114/0x29c [ 4.013073] __rpm_callback+0x48/0x1e0 [ 4.013079] rpm_callback+0x68/0x80 [ 4.013084] rpm_resume+0x3bc/0x6a0 [ 4.013089] __pm_runtime_resume+0x50/0x9c [ 4.013095] pm_runtime_get_suppliers+0x60/0x8c [ 4.013101] __driver_probe_device+0x4c/0x14c [ 4.013108] driver_probe_device+0x3c/0x120 [ 4.013114] __driver_attach+0xc4/0x200 [ 4.013119] bus_for_each_dev+0x7c/0xe0 [ 4.013125] driver_attach+0x24/0x30 [ 4.013130] bus_add_driver+0x110/0x240 [ 4.013135] driver_register+0x68/0x124 [ 4.013142] __platform_driver_register+0x24/0x30 [ 4.013149] sdma_driver_init+0x20/0x1000 [imx_sdma] [ 4.013163] do_one_initcall+0x60/0x1e0 [ 4.013168] do_init_module+0x5c/0x21c [ 4.013175] load_module+0x1a98/0x205c [ 4.013181] init_module_from_file+0x88/0xd4 [ 4.013187] __arm64_sys_finit_module+0x258/0x350 [ 4.013194] invoke_syscall.constprop.0+0x50/0xe0 [ 4.013202] do_el0_svc+0xa8/0xe0 [ 4.013208] el0_svc+0x3c/0x140 [ 4.013215] el0t_64_sync_handler+0x120/0x12c [ 4.013222] el0t_64_sync+0x190/0x194 [ 4.013228] SMP: stopping secondary CPUs [ 4.013237] Kernel Offset: disabled [ 4.013239] CPU features: 0x00,00000000,00200000,4200420b [ 4.013243] Memory Limit: none [ 4.316721] ---[ end Kernel panic - not syncing: Asynchronous SError Interrupt ]---
Francesco
Quoted 26 lines
Subject:
clk_imx8mp_audiomix_runtime_resumeKernel panic regression on v6.12Hello,
it seems that an old regression is back on v6.12, reproduced on -rc2 (not sure about rc1).The original report is from
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2F
lore.kernel.org%2Fall%2F20240424164725.GA18760%40francesco- nb%2F&data=05%7C02%7Cpeng.fan%40nxp.com%7C5d607b7da6304 cc475bd08dce6d39678%7C686ea1d3bc2b4c6fa92cd99c5c301635%7 C0%7C0%7C638639043687597943%7CUnknown%7CTWFpbGZsb3d8e yJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn 0%3D%7C0%7C%7C%7C&sdata=OEpuMElhS1Qu8ozk%2Foru6LUf3m6Z 9vKCIph0ySjhwFg%3D&reserved=0
and it was fixed with
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2F
lore.kernel.org%2Fall%2F1715396125-3724-1-git-send-email- shengjiu.wang%40nxp.com%2F&data=05%7C02%7Cpeng.fan%40nxp.c om%7C5d607b7da6304cc475bd08dce6d39678%7C686ea1d3bc2b4c6 fa92cd99c5c301635%7C0%7C0%7C638639043687614985%7CUnkno wn%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBT iI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=Uk3dHAJ60Q yvDHohjqZJSqaPZCCU4tAM7eD1cY%2Fh9gg%3D&reserved=0.
Quoted 1 line
Is it now back?
With tag: next-20240930, I need see this issue on i.MX8MP-EVK board.
Regards,
Peng.
Quoted 84 lines
[ 4.012850] SError Interrupt on CPU2, code 0x00000000bf000002 -- SError [ 4.012862] CPU: 2 UID: 0 PID: 186 Comm: (udev-worker) Not tainted 6.12.0-rc2-0.0.0-devel-00004-g8b1b79e88956 #1 [ 4.012869] Hardware name: Toradex Verdin iMX8M Plus WB on Dahlia Board (DT) [ 4.012872] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 4.012877] pc : clk_imx8mp_audiomix_runtime_resume+0x38/0x48 [ 4.012891] lr : pm_generic_runtime_resume+0x2c/0x44 [ 4.012897] sp : ffff8000821cb740 [ 4.012899] x29: ffff8000821cb740 x28: ffff8000793c48d8 x27: ffff8000793c48c0 [ 4.012908] x26: ffff0000c0ec90f4 x25: 0000000000000000 x24: 0000000000000000 [ 4.012916] x23: 0000000000000000 x22: ffff0000c1bef180 x21: 0000000000000000 [ 4.012923] x20: ffff0000c0a73000 x19: ffff0000c0ecbc10 x18: ffffffffffffffff [ 4.012930] x17: 3030303064623033 x16: 2f7375622e303030 x15: 756e285472656c6c [ 4.012937] x14: ffff800081267458 x13: 6d692c6c73664361 x12: 0000000000000000 [ 4.012944] x11: 00353333333d4d55 x10: ffff8000818020ae x9 : 0000000000000008 [ 4.012951] x8 : 0000000000000008 x7 : 0000000000000000 x6 : ffff0000c5bf2080 [ 4.012958] x5 : ffff800081f10000 x4 : ffff800080c182e8 x3 : ffff0000c0ee7088 [ 4.012965] x2 : 0000000000000000 x1 : 0000000000000004 x0 : ffff800081f10300 [ 4.012973] Kernel panic - not syncing: Asynchronous SError Interrupt [ 4.012976] CPU: 2 UID: 0 PID: 186 Comm: (udev-worker) Not tainted 6.12.0-rc2-0.0.0-devel-00004-g8b1b79e88956 #1 [ 4.012982] Hardware name: Toradex Verdin iMX8M Plus WB on Dahlia Board (DT) [ 4.012985] Call trace: [ 4.012988] dump_backtrace+0xd0/0x120 [ 4.012998] show_stack+0x18/0x24 [ 4.013005] dump_stack_lvl+0x60/0x80 [ 4.013013] dump_stack+0x18/0x24 [ 4.013019] panic+0x168/0x350 [ 4.013025] add_taint+0x0/0xbc [ 4.013029] arm64_serror_panic+0x64/0x70 [ 4.013034] do_serror+0x3c/0x70 [ 4.013039] el1h_64_error_handler+0x30/0x54 [ 4.013046] el1h_64_error+0x64/0x68 [ 4.013050] clk_imx8mp_audiomix_runtime_resume+0x38/0x48 [ 4.013059] __genpd_runtime_resume+0x30/0x80 [ 4.013066] genpd_runtime_resume+0x114/0x29c [ 4.013073] __rpm_callback+0x48/0x1e0 [ 4.013079] rpm_callback+0x68/0x80 [ 4.013084] rpm_resume+0x3bc/0x6a0 [ 4.013089] __pm_runtime_resume+0x50/0x9c [ 4.013095] pm_runtime_get_suppliers+0x60/0x8c [ 4.013101] __driver_probe_device+0x4c/0x14c [ 4.013108] driver_probe_device+0x3c/0x120 [ 4.013114] __driver_attach+0xc4/0x200 [ 4.013119] bus_for_each_dev+0x7c/0xe0 [ 4.013125] driver_attach+0x24/0x30 [ 4.013130] bus_add_driver+0x110/0x240 [ 4.013135] driver_register+0x68/0x124 [ 4.013142] __platform_driver_register+0x24/0x30 [ 4.013149] sdma_driver_init+0x20/0x1000 [imx_sdma] [ 4.013163] do_one_initcall+0x60/0x1e0 [ 4.013168] do_init_module+0x5c/0x21c [ 4.013175] load_module+0x1a98/0x205c [ 4.013181] init_module_from_file+0x88/0xd4 [ 4.013187] __arm64_sys_finit_module+0x258/0x350 [ 4.013194] invoke_syscall.constprop.0+0x50/0xe0 [ 4.013202] do_el0_svc+0xa8/0xe0 [ 4.013208] el0_svc+0x3c/0x140 [ 4.013215] el0t_64_sync_handler+0x120/0x12c [ 4.013222] el0t_64_sync+0x190/0x194 [ 4.013228] SMP: stopping secondary CPUs [ 4.013237] Kernel Offset: disabled [ 4.013239] CPU features: 0x00,00000000,00200000,4200420b [ 4.013243] Memory Limit: none [ 4.316721] ---[ end Kernel panic - not syncing: Asynchronous SErrorInterrupt ]---
Francesco
Quoted 11 lines
Subject: RE:
clk_imx8mp_audiomix_runtime_resumeKernel panic regression on v6.12Quoted 1 line
Subject:
clk_imx8mp_audiomix_runtime_resumeKernel panicregression on
Quoted 4 lines
v6.12
Is it now back?
With tag: next-20240930, I need see this issue on i.MX8MP-EVK board.
Sorry, typo. I not see issue on my board.
Regards,
Peng.
Quoted 94 lines
Regards,
Peng.Quoted 2 lines
[ 4.012850] SError Interrupt on CPU2, code 0x00000000bf000002 --
Quoted 2 lines
SError
[ 4.012862] CPU: 2 UID: 0 PID: 186 Comm: (udev-worker) Nottainted
Quoted 4 lines
6.12.0-rc2-0.0.0-devel-00004-g8b1b79e88956 #1
[ 4.012869] Hardware name: Toradex Verdin iMX8M Plus WB on Dahlia Board (DT) [ 4.012872] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS
Quoted 2 lines
BTYPE=--)
[ 4.012877] pc :clk_imx8mp_audiomix_runtime_resume+0x38/0x48 > [ 4.012891] lr : pm_generic_runtime_resume+0x2c/0x44Quoted 14 lines
[ 4.012897] sp : ffff8000821cb740 [ 4.012899] x29: ffff8000821cb740 x28: ffff8000793c48d8 x27: ffff8000793c48c0 [ 4.012908] x26: ffff0000c0ec90f4 x25: 0000000000000000 x24: 0000000000000000 [ 4.012916] x23: 0000000000000000 x22: ffff0000c1bef180 x21: 0000000000000000 [ 4.012923] x20: ffff0000c0a73000 x19: ffff0000c0ecbc10 x18: ffffffffffffffff [ 4.012930] x17: 3030303064623033 x16: 2f7375622e303030 x15: 756e285472656c6c [ 4.012937] x14: ffff800081267458 x13: 6d692c6c73664361 x12: 0000000000000000 [ 4.012944] x11: 00353333333d4d55 x10: ffff8000818020ae x9 :Quoted 8 lines
0000000000000008
[ 4.012951] x8 : 0000000000000008 x7 : 0000000000000000 x6 : ffff0000c5bf2080 [ 4.012958] x5 : ffff800081f10000 x4 : ffff800080c182e8 x3 : ffff0000c0ee7088 [ 4.012965] x2 : 0000000000000000 x1 : 0000000000000004 x0 : ffff800081f10300 [ 4.012973] Kernel panic - not syncing: Asynchronous SErrorInterrupt
Quoted 1 line
[ 4.012976] CPU: 2 UID: 0 PID: 186 Comm: (udev-worker) Nottainted
Quoted 50 lines
6.12.0-rc2-0.0.0-devel-00004-g8b1b79e88956 #1
[ 4.012982] Hardware name: Toradex Verdin iMX8M Plus WB on Dahlia Board (DT) [ 4.012985] Call trace: [ 4.012988] dump_backtrace+0xd0/0x120 [ 4.012998] show_stack+0x18/0x24 [ 4.013005] dump_stack_lvl+0x60/0x80 [ 4.013013] dump_stack+0x18/0x24 [ 4.013019] panic+0x168/0x350 [ 4.013025] add_taint+0x0/0xbc [ 4.013029] arm64_serror_panic+0x64/0x70 [ 4.013034] do_serror+0x3c/0x70 [ 4.013039] el1h_64_error_handler+0x30/0x54 [ 4.013046] el1h_64_error+0x64/0x68 [ 4.013050] clk_imx8mp_audiomix_runtime_resume+0x38/0x48 [ 4.013059] __genpd_runtime_resume+0x30/0x80 [ 4.013066] genpd_runtime_resume+0x114/0x29c [ 4.013073] __rpm_callback+0x48/0x1e0 [ 4.013079] rpm_callback+0x68/0x80 [ 4.013084] rpm_resume+0x3bc/0x6a0 [ 4.013089] __pm_runtime_resume+0x50/0x9c [ 4.013095] pm_runtime_get_suppliers+0x60/0x8c [ 4.013101] __driver_probe_device+0x4c/0x14c [ 4.013108] driver_probe_device+0x3c/0x120 [ 4.013114] __driver_attach+0xc4/0x200 [ 4.013119] bus_for_each_dev+0x7c/0xe0 [ 4.013125] driver_attach+0x24/0x30 [ 4.013130] bus_add_driver+0x110/0x240 [ 4.013135] driver_register+0x68/0x124 [ 4.013142] __platform_driver_register+0x24/0x30 [ 4.013149] sdma_driver_init+0x20/0x1000 [imx_sdma] [ 4.013163] do_one_initcall+0x60/0x1e0 [ 4.013168] do_init_module+0x5c/0x21c [ 4.013175] load_module+0x1a98/0x205c [ 4.013181] init_module_from_file+0x88/0xd4 [ 4.013187] __arm64_sys_finit_module+0x258/0x350 [ 4.013194] invoke_syscall.constprop.0+0x50/0xe0 [ 4.013202] do_el0_svc+0xa8/0xe0 [ 4.013208] el0_svc+0x3c/0x140 [ 4.013215] el0t_64_sync_handler+0x120/0x12c [ 4.013222] el0t_64_sync+0x190/0x194 [ 4.013228] SMP: stopping secondary CPUs [ 4.013237] Kernel Offset: disabled [ 4.013239] CPU features: 0x00,00000000,00200000,4200420b [ 4.013243] Memory Limit: none [ 4.316721] ---[ end Kernel panic - not syncing: Asynchronous SErrorInterrupt ]---
Francesco
Quoted 6 lines · Peng Fan
Quoted 6 lines
Subject: RE:
clk_imx8mp_audiomix_runtime_resumeKernel panic regression on v6.12Quoted 1 line
Subject:
clk_imx8mp_audiomix_runtime_resumeKernel panicregression on
Quoted 8 lines
Quoted 6 lines
Quoted 4 lines
v6.12
Is it now back?
With tag: next-20240930, I need see this issue on i.MX8MP-EVK board.
Sorry, typo. I not see issue on my board.
I tested RC1 on the Beacon board and didn't see any issues, but I can try testing linux-next when I have some time.
adam
Quoted 99 lines
Regards,
Peng.Quoted 94 lines
Regards,
Peng.Quoted 2 lines
[ 4.012850] SError Interrupt on CPU2, code 0x00000000bf000002 --
Quoted 2 lines
SError
[ 4.012862] CPU: 2 UID: 0 PID: 186 Comm: (udev-worker) Nottainted
Quoted 4 lines
6.12.0-rc2-0.0.0-devel-00004-g8b1b79e88956 #1
[ 4.012869] Hardware name: Toradex Verdin iMX8M Plus WB on Dahlia Board (DT) [ 4.012872] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS
Quoted 2 lines
BTYPE=--)
[ 4.012877] pc :clk_imx8mp_audiomix_runtime_resume+0x38/0x48 > [ 4.012891] lr : pm_generic_runtime_resume+0x2c/0x44Quoted 14 lines
[ 4.012897] sp : ffff8000821cb740 [ 4.012899] x29: ffff8000821cb740 x28: ffff8000793c48d8 x27: ffff8000793c48c0 [ 4.012908] x26: ffff0000c0ec90f4 x25: 0000000000000000 x24: 0000000000000000 [ 4.012916] x23: 0000000000000000 x22: ffff0000c1bef180 x21: 0000000000000000 [ 4.012923] x20: ffff0000c0a73000 x19: ffff0000c0ecbc10 x18: ffffffffffffffff [ 4.012930] x17: 3030303064623033 x16: 2f7375622e303030 x15: 756e285472656c6c [ 4.012937] x14: ffff800081267458 x13: 6d692c6c73664361 x12: 0000000000000000 [ 4.012944] x11: 00353333333d4d55 x10: ffff8000818020ae x9 :Quoted 8 lines
0000000000000008
[ 4.012951] x8 : 0000000000000008 x7 : 0000000000000000 x6 : ffff0000c5bf2080 [ 4.012958] x5 : ffff800081f10000 x4 : ffff800080c182e8 x3 : ffff0000c0ee7088 [ 4.012965] x2 : 0000000000000000 x1 : 0000000000000004 x0 : ffff800081f10300 [ 4.012973] Kernel panic - not syncing: Asynchronous SErrorInterrupt
Quoted 1 line
[ 4.012976] CPU: 2 UID: 0 PID: 186 Comm: (udev-worker) Nottainted
Quoted 50 lines
6.12.0-rc2-0.0.0-devel-00004-g8b1b79e88956 #1
[ 4.012982] Hardware name: Toradex Verdin iMX8M Plus WB on Dahlia Board (DT) [ 4.012985] Call trace: [ 4.012988] dump_backtrace+0xd0/0x120 [ 4.012998] show_stack+0x18/0x24 [ 4.013005] dump_stack_lvl+0x60/0x80 [ 4.013013] dump_stack+0x18/0x24 [ 4.013019] panic+0x168/0x350 [ 4.013025] add_taint+0x0/0xbc [ 4.013029] arm64_serror_panic+0x64/0x70 [ 4.013034] do_serror+0x3c/0x70 [ 4.013039] el1h_64_error_handler+0x30/0x54 [ 4.013046] el1h_64_error+0x64/0x68 [ 4.013050] clk_imx8mp_audiomix_runtime_resume+0x38/0x48 [ 4.013059] __genpd_runtime_resume+0x30/0x80 [ 4.013066] genpd_runtime_resume+0x114/0x29c [ 4.013073] __rpm_callback+0x48/0x1e0 [ 4.013079] rpm_callback+0x68/0x80 [ 4.013084] rpm_resume+0x3bc/0x6a0 [ 4.013089] __pm_runtime_resume+0x50/0x9c [ 4.013095] pm_runtime_get_suppliers+0x60/0x8c [ 4.013101] __driver_probe_device+0x4c/0x14c [ 4.013108] driver_probe_device+0x3c/0x120 [ 4.013114] __driver_attach+0xc4/0x200 [ 4.013119] bus_for_each_dev+0x7c/0xe0 [ 4.013125] driver_attach+0x24/0x30 [ 4.013130] bus_add_driver+0x110/0x240 [ 4.013135] driver_register+0x68/0x124 [ 4.013142] __platform_driver_register+0x24/0x30 [ 4.013149] sdma_driver_init+0x20/0x1000 [imx_sdma] [ 4.013163] do_one_initcall+0x60/0x1e0 [ 4.013168] do_init_module+0x5c/0x21c [ 4.013175] load_module+0x1a98/0x205c [ 4.013181] init_module_from_file+0x88/0xd4 [ 4.013187] __arm64_sys_finit_module+0x258/0x350 [ 4.013194] invoke_syscall.constprop.0+0x50/0xe0 [ 4.013202] do_el0_svc+0xa8/0xe0 [ 4.013208] el0_svc+0x3c/0x140 [ 4.013215] el0t_64_sync_handler+0x120/0x12c [ 4.013222] el0t_64_sync+0x190/0x194 [ 4.013228] SMP: stopping secondary CPUs [ 4.013237] Kernel Offset: disabled [ 4.013239] CPU features: 0x00,00000000,00200000,4200420b [ 4.013243] Memory Limit: none [ 4.316721] ---[ end Kernel panic - not syncing: Asynchronous SErrorInterrupt ]---
Francesco
Il 8 ottobre 2024 14:19:15 CEST, Adam Ford <[email protected]> ha scritto:
Quoted 10 lines · Peng Fan
Quoted 9 lines
Quoted 9 lines
Subject: RE:
clk_imx8mp_audiomix_runtime_resumeKernel panic regression on v6.12Quoted 1 line
Subject:
clk_imx8mp_audiomix_runtime_resumeKernel panicregression on
Quoted 3 lines
v6.12
Quoted 9 lines
Quoted 5 lines
Quoted 3 lines
Quoted 1 line
Is it now back?
With tag: next-20240930, I need see this issue on i.MX8MP-EVK board.
Sorry, typo. I not see issue on my board.
I tested RC1 on the Beacon board and didn't see any issues, but I can try testing linux-next when I have some time.
I forgot to mention that the issue is not systematic as it was in the original report.
And it was reproduced on v6.12-rc2, not with -next.
Francesco
Quoted 100 lines
adam
Quoted 99 lines
Regards,
Peng.Quoted 94 lines
Regards,
Peng.Quoted 2 lines
[ 4.012850] SError Interrupt on CPU2, code 0x00000000bf000002 --
Quoted 2 lines
SError
[ 4.012862] CPU: 2 UID: 0 PID: 186 Comm: (udev-worker) Nottainted
Quoted 4 lines
6.12.0-rc2-0.0.0-devel-00004-g8b1b79e88956 #1
[ 4.012869] Hardware name: Toradex Verdin iMX8M Plus WB on Dahlia Board (DT) [ 4.012872] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS
Quoted 2 lines
BTYPE=--)
[ 4.012877] pc :clk_imx8mp_audiomix_runtime_resume+0x38/0x48 > [ 4.012891] lr : pm_generic_runtime_resume+0x2c/0x44Quoted 14 lines
[ 4.012897] sp : ffff8000821cb740 [ 4.012899] x29: ffff8000821cb740 x28: ffff8000793c48d8 x27: ffff8000793c48c0 [ 4.012908] x26: ffff0000c0ec90f4 x25: 0000000000000000 x24: 0000000000000000 [ 4.012916] x23: 0000000000000000 x22: ffff0000c1bef180 x21: 0000000000000000 [ 4.012923] x20: ffff0000c0a73000 x19: ffff0000c0ecbc10 x18: ffffffffffffffff [ 4.012930] x17: 3030303064623033 x16: 2f7375622e303030 x15: 756e285472656c6c [ 4.012937] x14: ffff800081267458 x13: 6d692c6c73664361 x12: 0000000000000000 [ 4.012944] x11: 00353333333d4d55 x10: ffff8000818020ae x9 :Quoted 8 lines
0000000000000008
[ 4.012951] x8 : 0000000000000008 x7 : 0000000000000000 x6 : ffff0000c5bf2080 [ 4.012958] x5 : ffff800081f10000 x4 : ffff800080c182e8 x3 : ffff0000c0ee7088 [ 4.012965] x2 : 0000000000000000 x1 : 0000000000000004 x0 : ffff800081f10300 [ 4.012973] Kernel panic - not syncing: Asynchronous SErrorInterrupt
Quoted 1 line
[ 4.012976] CPU: 2 UID: 0 PID: 186 Comm: (udev-worker) Nottainted
Quoted 50 lines
6.12.0-rc2-0.0.0-devel-00004-g8b1b79e88956 #1
[ 4.012982] Hardware name: Toradex Verdin iMX8M Plus WB on Dahlia Board (DT) [ 4.012985] Call trace: [ 4.012988] dump_backtrace+0xd0/0x120 [ 4.012998] show_stack+0x18/0x24 [ 4.013005] dump_stack_lvl+0x60/0x80 [ 4.013013] dump_stack+0x18/0x24 [ 4.013019] panic+0x168/0x350 [ 4.013025] add_taint+0x0/0xbc [ 4.013029] arm64_serror_panic+0x64/0x70 [ 4.013034] do_serror+0x3c/0x70 [ 4.013039] el1h_64_error_handler+0x30/0x54 [ 4.013046] el1h_64_error+0x64/0x68 [ 4.013050] clk_imx8mp_audiomix_runtime_resume+0x38/0x48 [ 4.013059] __genpd_runtime_resume+0x30/0x80 [ 4.013066] genpd_runtime_resume+0x114/0x29c [ 4.013073] __rpm_callback+0x48/0x1e0 [ 4.013079] rpm_callback+0x68/0x80 [ 4.013084] rpm_resume+0x3bc/0x6a0 [ 4.013089] __pm_runtime_resume+0x50/0x9c [ 4.013095] pm_runtime_get_suppliers+0x60/0x8c [ 4.013101] __driver_probe_device+0x4c/0x14c [ 4.013108] driver_probe_device+0x3c/0x120 [ 4.013114] __driver_attach+0xc4/0x200 [ 4.013119] bus_for_each_dev+0x7c/0xe0 [ 4.013125] driver_attach+0x24/0x30 [ 4.013130] bus_add_driver+0x110/0x240 [ 4.013135] driver_register+0x68/0x124 [ 4.013142] __platform_driver_register+0x24/0x30 [ 4.013149] sdma_driver_init+0x20/0x1000 [imx_sdma] [ 4.013163] do_one_initcall+0x60/0x1e0 [ 4.013168] do_init_module+0x5c/0x21c [ 4.013175] load_module+0x1a98/0x205c [ 4.013181] init_module_from_file+0x88/0xd4 [ 4.013187] __arm64_sys_finit_module+0x258/0x350 [ 4.013194] invoke_syscall.constprop.0+0x50/0xe0 [ 4.013202] do_el0_svc+0xa8/0xe0 [ 4.013208] el0_svc+0x3c/0x140 [ 4.013215] el0t_64_sync_handler+0x120/0x12c [ 4.013222] el0t_64_sync+0x190/0x194 [ 4.013228] SMP: stopping secondary CPUs [ 4.013237] Kernel Offset: disabled [ 4.013239] CPU features: 0x00,00000000,00200000,4200420b [ 4.013243] Memory Limit: none [ 4.316721] ---[ end Kernel panic - not syncing: Asynchronous SErrorInterrupt ]---
Francesco
Hello,
Quoted 18 lines · Francesco Dolcini
Il 8 ottobre 2024 14:19:15 CEST, Adam Ford <[email protected]> ha scritto:
Quoted 16 lines · Peng Fan
Quoted 14 lines
Quoted 4 lines
Subject: RE:
clk_imx8mp_audiomix_runtime_resumeKernel panic regression on v6.12Quoted 8 lines
Quoted 1 line
Subject:
clk_imx8mp_audiomix_runtime_resumeKernel panicregression on
Quoted 4 lines
v6.12
Is it now back?
With tag: next-20240930, I need see this issue on i.MX8MP-EVK board.
Sorry, typo. I not see issue on my board.
Quoted 7 lines
Quoted 3 lines
I tested RC1 on the Beacon board and didn't see any issues, but I can try testing linux-next when I have some time.
I forgot to mention that the issue is not systematic as it was in the original report.
And it was reproduced on v6.12-rc2, not with -next.
I tested RC3, and I cannot replicate it. Are you still having issues?
adam
Quoted 106 lines
Francesco
Quoted 100 lines
adam
Quoted 99 lines
Regards,
Peng.Quoted 94 lines
Regards,
Peng.Quoted 2 lines
[ 4.012850] SError Interrupt on CPU2, code 0x00000000bf000002 --
Quoted 2 lines
SError
[ 4.012862] CPU: 2 UID: 0 PID: 186 Comm: (udev-worker) Nottainted
Quoted 4 lines
6.12.0-rc2-0.0.0-devel-00004-g8b1b79e88956 #1
[ 4.012869] Hardware name: Toradex Verdin iMX8M Plus WB on Dahlia Board (DT) [ 4.012872] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS
Quoted 2 lines
BTYPE=--)
[ 4.012877] pc :clk_imx8mp_audiomix_runtime_resume+0x38/0x48 > [ 4.012891] lr : pm_generic_runtime_resume+0x2c/0x44Quoted 14 lines
[ 4.012897] sp : ffff8000821cb740 [ 4.012899] x29: ffff8000821cb740 x28: ffff8000793c48d8 x27: ffff8000793c48c0 [ 4.012908] x26: ffff0000c0ec90f4 x25: 0000000000000000 x24: 0000000000000000 [ 4.012916] x23: 0000000000000000 x22: ffff0000c1bef180 x21: 0000000000000000 [ 4.012923] x20: ffff0000c0a73000 x19: ffff0000c0ecbc10 x18: ffffffffffffffff [ 4.012930] x17: 3030303064623033 x16: 2f7375622e303030 x15: 756e285472656c6c [ 4.012937] x14: ffff800081267458 x13: 6d692c6c73664361 x12: 0000000000000000 [ 4.012944] x11: 00353333333d4d55 x10: ffff8000818020ae x9 :Quoted 8 lines
0000000000000008
[ 4.012951] x8 : 0000000000000008 x7 : 0000000000000000 x6 : ffff0000c5bf2080 [ 4.012958] x5 : ffff800081f10000 x4 : ffff800080c182e8 x3 : ffff0000c0ee7088 [ 4.012965] x2 : 0000000000000000 x1 : 0000000000000004 x0 : ffff800081f10300 [ 4.012973] Kernel panic - not syncing: Asynchronous SErrorInterrupt
Quoted 1 line
[ 4.012976] CPU: 2 UID: 0 PID: 186 Comm: (udev-worker) Nottainted
Quoted 50 lines
6.12.0-rc2-0.0.0-devel-00004-g8b1b79e88956 #1
[ 4.012982] Hardware name: Toradex Verdin iMX8M Plus WB on Dahlia Board (DT) [ 4.012985] Call trace: [ 4.012988] dump_backtrace+0xd0/0x120 [ 4.012998] show_stack+0x18/0x24 [ 4.013005] dump_stack_lvl+0x60/0x80 [ 4.013013] dump_stack+0x18/0x24 [ 4.013019] panic+0x168/0x350 [ 4.013025] add_taint+0x0/0xbc [ 4.013029] arm64_serror_panic+0x64/0x70 [ 4.013034] do_serror+0x3c/0x70 [ 4.013039] el1h_64_error_handler+0x30/0x54 [ 4.013046] el1h_64_error+0x64/0x68 [ 4.013050] clk_imx8mp_audiomix_runtime_resume+0x38/0x48 [ 4.013059] __genpd_runtime_resume+0x30/0x80 [ 4.013066] genpd_runtime_resume+0x114/0x29c [ 4.013073] __rpm_callback+0x48/0x1e0 [ 4.013079] rpm_callback+0x68/0x80 [ 4.013084] rpm_resume+0x3bc/0x6a0 [ 4.013089] __pm_runtime_resume+0x50/0x9c [ 4.013095] pm_runtime_get_suppliers+0x60/0x8c [ 4.013101] __driver_probe_device+0x4c/0x14c [ 4.013108] driver_probe_device+0x3c/0x120 [ 4.013114] __driver_attach+0xc4/0x200 [ 4.013119] bus_for_each_dev+0x7c/0xe0 [ 4.013125] driver_attach+0x24/0x30 [ 4.013130] bus_add_driver+0x110/0x240 [ 4.013135] driver_register+0x68/0x124 [ 4.013142] __platform_driver_register+0x24/0x30 [ 4.013149] sdma_driver_init+0x20/0x1000 [imx_sdma] [ 4.013163] do_one_initcall+0x60/0x1e0 [ 4.013168] do_init_module+0x5c/0x21c [ 4.013175] load_module+0x1a98/0x205c [ 4.013181] init_module_from_file+0x88/0xd4 [ 4.013187] __arm64_sys_finit_module+0x258/0x350 [ 4.013194] invoke_syscall.constprop.0+0x50/0xe0 [ 4.013202] do_el0_svc+0xa8/0xe0 [ 4.013208] el0_svc+0x3c/0x140 [ 4.013215] el0t_64_sync_handler+0x120/0x12c [ 4.013222] el0t_64_sync+0x190/0x194 [ 4.013228] SMP: stopping secondary CPUs [ 4.013237] Kernel Offset: disabled [ 4.013239] CPU features: 0x00,00000000,00200000,4200420b [ 4.013243] Memory Limit: none [ 4.316721] ---[ end Kernel panic - not syncing: Asynchronous SErrorInterrupt ]---
Francesco
Hello,
Hello,
Quoted 8 lines · Francesco Dolcini
Hello,
it seems that an old regression is back on v6.12, reproduced on -rc2 (not sure about rc1).The original report is from https://lore.kernel.org/all/20240424164725.GA18760@francesco-nb/
and it was fixed with https://lore.kernel.org/all/[email protected]/.Is it now back?
I was able to reproduce this issue once more, this time with 6.11.7. As I wrote in another email the issue is not systematic as it used to be.
Any idea?
[ 4.287586] SError Interrupt on CPU1, code 0x00000000bf000002 -- SError [ 4.287594] CPU: 1 UID: 0 PID: 195 Comm: (udev-worker) Not tainted 6.11.7-7.1.0-devel-00010-g5374bda92db5 #1 [ 4.287601] Hardware name: Toradex Verdin iMX8M Plus WB on Dahlia Board (DT) [ 4.287604] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 4.287609] pc : clk_imx8mp_audiomix_runtime_resume+0x18/0x40 [ 4.287623] lr : pm_generic_runtime_resume+0x2c/0x44 [ 4.287631] sp : ffff80008216b740 [ 4.287633] x29: ffff80008216b740 x28: ffff800080e85010 x27: ffff8000794758d8 [ 4.287642] x26: ffff0000c0a664f4 x25: 0000000000000000 x24: 0000000000000000 [ 4.287649] x23: 0000000000000000 x22: ffff0000c0d01120 x21: 0000000000000000 [ 4.287655] x20: ffff0000c1308800 x19: ffff0000c0a68c10 x18: 0000000000047820 [ 4.287662] x17: 0000000000000000 x16: ffff0000faf87820 x15: 0000000000000002 [ 4.287668] x14: 0000000000001400 x13: 00000000000003a0 x12: 0000000054a32c00 [ 4.287675] x11: 0000000000000000 x10: ffff8000817b9d36 x9 : 0000000000000008 [ 4.287682] x8 : 0000000000000008 x7 : 0000000000000000 x6 : 0000000000000000 [ 4.287688] x5 : ffff800081ec0000 x4 : ffff0000c1a0b488 x3 : ffff800080bd23f0 [ 4.287694] x2 : 0000000000000000 x1 : 0000000000000004 x0 : ffff800081ec0300 [ 4.287703] Kernel panic - not syncing: Asynchronous SError Interrupt [ 4.287705] CPU: 1 UID: 0 PID: 195 Comm: (udev-worker) Not tainted 6.11.7-7.1.0-devel-00010-g5374bda92db5 #1 [ 4.287711] Hardware name: Toradex Verdin iMX8M Plus WB on Dahlia Board (DT) [ 4.287714] Call trace: [ 4.287716] dump_backtrace+0x94/0x114 [ 4.287725] show_stack+0x18/0x24 [ 4.287732] dump_stack_lvl+0x34/0x8c [ 4.287740] dump_stack+0x18/0x24 [ 4.287747] panic+0x390/0x3a4 [ 4.287751] nmi_panic+0x40/0x8c [ 4.287755] arm64_serror_panic+0x64/0x70 [ 4.287759] do_serror+0x3c/0x70 [ 4.287763] el1h_64_error_handler+0x30/0x48 [ 4.287771] el1h_64_error+0x64/0x68 [ 4.287776] clk_imx8mp_audiomix_runtime_resume+0x18/0x40 [ 4.287784] __genpd_runtime_resume+0x30/0x80 [ 4.287791] genpd_runtime_resume+0x114/0x29c [ 4.287799] __rpm_callback+0x48/0x1d8 [ 4.287806] rpm_callback+0x68/0x74 [ 4.287813] rpm_resume+0x46c/0x6bc [ 4.287819] __pm_runtime_resume+0x50/0x94 [ 4.287825] pm_runtime_get_suppliers+0x60/0x8c [ 4.287831] __driver_probe_device+0x4c/0x15c [ 4.287838] driver_probe_device+0x3c/0x110 [ 4.287844] __driver_attach+0xf0/0x1f8 [ 4.287850] bus_for_each_dev+0x7c/0xdc [ 4.287856] driver_attach+0x24/0x30 [ 4.287862] bus_add_driver+0x110/0x234 [ 4.287868] driver_register+0x5c/0x124 [ 4.287874] __platform_driver_register+0x28/0x34 [ 4.287882] sdma_driver_init+0x20/0x1000 [imx_sdma] [ 4.287895] do_one_initcall+0x80/0x1c8 [ 4.287900] do_init_module+0x60/0x218 [ 4.287907] load_module+0x1fcc/0x2040 [ 4.287912] init_module_from_file+0x88/0xcc [ 4.287918] __arm64_sys_finit_module+0x254/0x34c [ 4.287924] invoke_syscall.constprop.0+0x50/0xe4 [ 4.287932] do_el0_svc+0xa8/0xc8 [ 4.287938] el0_svc+0x3c/0x13c [ 4.287945] el0t_64_sync_handler+0x120/0x12c [ 4.287952] el0t_64_sync+0x190/0x194 [ 4.287958] SMP: stopping secondary CPUs [ 4.287965] Kernel Offset: disabled [ 4.287966] CPU features: 0x00,00000000,00100000,4200420b [ 4.287970] Memory Limit: none [ 4.590829] ---[ end Kernel panic - not syncing: Asynchronous SError Interrupt ]---
Francesco
Quoted 7 lines · Francesco Dolcini
Quoted 6 lines · Francesco Dolcini
it seems that an old regression is back on v6.12, reproduced on -rc2 (not sure about rc1).
The original report is from https://lore.kernel.org/all/20240424164725.GA18760@francesco-nb/
and it was fixed with https://lore.kernel.org/all/[email protected]/.
Quoted 7 lines
Quoted 1 line
Is it now back?
I was able to reproduce this issue once more, this time with 6.11.7. As I wrote in another email the issue is not systematic as it used to be.
Any idea?
Frank, Shengjiu, could it be that the udelay(5) in imx_pgc_power_up() is too short and therefore we have such non-systematic failures?
Francesco
Quoted 11 lines · Francesco Dolcini
Quoted 9 lines · Francesco Dolcini
Quoted 7 lines · Francesco Dolcini
it seems that an old regression is back on v6.12, reproduced on -rc2 (not sure about rc1).
The original report is from https://lore.kernel.org/all/20240424164725.GA18760@francesco-nb/
and it was fixed with https://lore.kernel.org/all/[email protected]/.Is it now back?
Quoted 9 lines
Quoted 5 lines
I was able to reproduce this issue once more, this time with 6.11.7. As I wrote in another email the issue is not systematic as it used to be.
Any idea?
Frank, Shengjiu, could it be that the udelay(5) in
imx_pgc_power_up()is too short and therefore we have such non-systematic failures?
Francesco, it seems hard to reproduce it on my i.MX8MP-EVK board.
If it is easy to reproduce on your side, you can try to enlarge the delay time to see if there is any improvement.
Thanks.
Best regards
Shengjiu Wang
Quoted 18 lines · Shengjiu Wang
Quoted 17 lines · Francesco Dolcini
Quoted 14 lines · Francesco Dolcini
Quoted 7 lines · Francesco Dolcini
it seems that an old regression is back on v6.12, reproduced on -rc2 (not sure about rc1).
The original report is from https://lore.kernel.org/all/20240424164725.GA18760@francesco-nb/
and it was fixed with https://lore.kernel.org/all/[email protected]/.Is it now back?
I was able to reproduce this issue once more, this time with 6.11.7. As I wrote in another email the issue is not systematic as it used to be.
Any idea?
Quoted 8 lines
Quoted 3 lines
Frank, Shengjiu, could it be that the udelay(5) in
imx_pgc_power_up()is too short and therefore we have such non-systematic failures?Francesco, it seems hard to reproduce it on my i.MX8MP-EVK board.
If it is easy to reproduce on your side, you can try to enlarge the delay time to see if there is any improvement.
It's hard also for me to reproduce, we just have a relatively extensive test farm and 2 times it happened while doing unrelated tests. I was hoping we could have some idea on what's going on, I'll see if I can put together some kind of stress test, being able to reproduce it more systematically would certainly help.
Francesco
Quoted 26 lines · Francesco Dolcini
Quoted 24 lines · Shengjiu Wang
Quoted 11 lines · Francesco Dolcini
Quoted 9 lines · Francesco Dolcini
Quoted 7 lines · Francesco Dolcini
it seems that an old regression is back on v6.12, reproduced on -rc2 (not sure about rc1).
The original report is from https://lore.kernel.org/all/20240424164725.GA18760@francesco-nb/
and it was fixed with https://lore.kernel.org/all/[email protected]/.Is it now back?
Quoted 9 lines
Quoted 5 lines
I was able to reproduce this issue once more, this time with 6.11.7. As I wrote in another email the issue is not systematic as it used to be.
Any idea?
Frank, Shengjiu, could it be that the udelay(5) in
imx_pgc_power_up()is too short and therefore we have such non-systematic failures?Francesco, it seems hard to reproduce it on my i.MX8MP-EVK board.
Quoted 9 lines
Quoted 2 lines
If it is easy to reproduce on your side, you can try to enlarge the delay time to see if there is any improvement.
It's hard also for me to reproduce, we just have a relatively extensive test farm and 2 times it happened while doing unrelated tests. I was hoping we could have some idea on what's going on, I'll see if I can put together some kind of stress test, being able to reproduce it more systematically would certainly help.
With my test, the issue reproduced with delay 5us/6us. but hard reproduced with 7us.
I think we may need to use a delay of 10us for safety.
Best regards
Shengjiu Wang
Hello Shengjiu,
Quoted 37 lines · Shengjiu Wang
Quoted 26 lines · Francesco Dolcini
Quoted 24 lines · Shengjiu Wang
Quoted 11 lines · Francesco Dolcini
Quoted 9 lines · Francesco Dolcini
Quoted 7 lines · Francesco Dolcini
it seems that an old regression is back on v6.12, reproduced on -rc2 (not sure about rc1).
The original report is from https://lore.kernel.org/all/20240424164725.GA18760@francesco-nb/
and it was fixed with https://lore.kernel.org/all/[email protected]/.Is it now back?
Quoted 9 lines
Quoted 5 lines
I was able to reproduce this issue once more, this time with 6.11.7. As I wrote in another email the issue is not systematic as it used to be.
Any idea?
Frank, Shengjiu, could it be that the udelay(5) in
imx_pgc_power_up()is too short and therefore we have such non-systematic failures?Francesco, it seems hard to reproduce it on my i.MX8MP-EVK board.
Quoted 9 lines
Quoted 2 lines
If it is easy to reproduce on your side, you can try to enlarge the delay time to see if there is any improvement.
It's hard also for me to reproduce, we just have a relatively extensive test farm and 2 times it happened while doing unrelated tests. I was hoping we could have some idea on what's going on, I'll see if I can put together some kind of stress test, being able to reproduce it more systematically would certainly help.
Quoted 3 lines
With my test, the issue reproduced with delay 5us/6us. but hard reproduced with 7us.
I think we may need to use a delay of 10us for safety.
Great that you were able to narrow this down and confirm the issue. I wonder if you would have any information on what is the actual delay that the HW would need, instead of guessing numbers. If not, well, let's go with 15usec, or 10usec, your call in the end.
Will you send a patch?
Francesco
Quoted 45 lines · Francesco Dolcini
Hello Shengjiu,
Quoted 37 lines · Shengjiu Wang
Quoted 26 lines · Francesco Dolcini
Quoted 24 lines · Shengjiu Wang
Quoted 11 lines · Francesco Dolcini
Quoted 9 lines · Francesco Dolcini
Quoted 7 lines · Francesco Dolcini
it seems that an old regression is back on v6.12, reproduced on -rc2 (not sure about rc1).
The original report is from https://lore.kernel.org/all/20240424164725.GA18760@francesco-nb/
and it was fixed with https://lore.kernel.org/all/[email protected]/.Is it now back?
Quoted 9 lines
Quoted 5 lines
I was able to reproduce this issue once more, this time with 6.11.7. As I wrote in another email the issue is not systematic as it used to be.
Any idea?
Frank, Shengjiu, could it be that the udelay(5) in
imx_pgc_power_up()is too short and therefore we have such non-systematic failures?Francesco, it seems hard to reproduce it on my i.MX8MP-EVK board.
Quoted 9 lines
Quoted 2 lines
If it is easy to reproduce on your side, you can try to enlarge the delay time to see if there is any improvement.
It's hard also for me to reproduce, we just have a relatively extensive test farm and 2 times it happened while doing unrelated tests. I was hoping we could have some idea on what's going on, I'll see if I can put together some kind of stress test, being able to reproduce it more systematically would certainly help.
Quoted 3 lines
With my test, the issue reproduced with delay 5us/6us. but hard reproduced with 7us.
I think we may need to use a delay of 10us for safety.
Quoted 6 lines
Great that you were able to narrow this down and confirm the issue. I wonder if you would have any information on what is the actual delay that the HW would need, instead of guessing numbers. If not, well, let's go with 15usec, or 10usec, your call in the end.
Will you send a patch?
Peng (or anyone from NXP),
Do any of the clock speeds have an impact on the propagation time? If the clocks are running at overdrive speeds vs nominal speeds vs underclocked, could this time be adjusted accordingly somehow?
adam
Quoted 3 lines
Francesco