I am reporting a kernel stability issue on a CIX Sky1 CD8180 based board running Linux 6.19.11 with the Sky1 patch set applied. After enabling additional kernel boot parameters for panic on lockups and better crash visibility, the system started showing repeated SCMI communication errors in dmesg, including response timeouts and unexpected message ordering on SCMI protocol devices.
The newly enabled boot options were added only to improve debugging and crash persistence, not to change the functional behavior of the board. Before enabling them, the system already had instability concerns and unexpected reboots or freezes. After enabling softlockup_panic=1 and hardlockup_panic=1, the kernel began to print a large amount of SCMI related errors, which strongly suggests an underlying firmware, mailbox, SCMI transport, or power management communication problem that was previously not visible so clearly in logs.
Hardware
Board: CIX Sky1 CD8180 platform, OrangePi 6 Plus class board
Firmware reports: Cix Technology Group CIX Phecda Board
Boot mode: devicetree boot
SoC family: Sky1 / CD8180
Serial console enabled on ttyAMA2
Software
Kernel: Linux 6.19.11 built with Sky1 patch set
Init system: OpenRC
Bootloader: GRUB style boot entry
ACPI disabled
BIOS: BiosV1.4-W20260130-97268c4c
Devicetree in use: sky1-orangepi-6-plus-6.19.11.dtb
Problem summary
The system shows repeated SCMI communication failures at runtime, including:
arm-scmi ... timed out in resp(caller: do_xfer+0x118/0x530)
scmi_protocol ... Message for XXX type Y is not expected!
These errors appear continuously in bursts and indicate that requests sent through SCMI are timing out, followed by responses arriving unexpectedly or out of sequence. This suggests a real bug in SCMI handling, firmware interaction, transport synchronization, or a related subsystem such as cpufreq, thermal, regulator, or DVFS integration.
The issue became clearly visible after switching from the original boot configuration to a second test configuration that added:
softlockup_panic=1
hardlockup_panic=1
These parameters were enabled only to improve lockup diagnosis and pstore crash capture. They do not appear to be the root cause themselves, but after enabling them the SCMI failures became obvious in the kernel log.
Observed errors include
Repeated SCMI response timeouts in do_xfer
Repeated unexpected SCMI protocol messages on scmi_dev.4 and scmi_dev.5
Large bursts of SCMI errors within seconds during runtime
Prior system instability and reboot investigation that motivated enabling stronger panic and debug options
Representative log excerpt
[ 0.114988] calling scmi_bus_init+0x0/0x60 @ 1
[ 0.115003] scmi_core: SCMI protocol bus registered
[ 0.115007] initcall scmi_bus_init+0x0/0x60 returned 0 after 0 usecs
[ 0.117921] calling scmi_power_domain_init+0x0/0x40 @ 1
[ 0.117946] initcall scmi_power_domain_init+0x0/0x40 returned 0 after 0 usecs
[ 0.372317] calling scmi_clocks_driver_init+0x0/0x40 @ 1
[ 0.372340] initcall scmi_clocks_driver_init+0x0/0x40 returned 0 after 16 usecs
[ 0.404252] calling scmi_perf_domain_driver_init+0x0/0x40 @ 1
[ 0.404274] initcall scmi_perf_domain_driver_init+0x0/0x40 returned 0 after 15 usecs
[ 0.407071] calling scmi_drv_init+0x0/0x40 @ 1
[ 0.407090] initcall scmi_drv_init+0x0/0x40 returned 0 after 12 usecs
[ 0.410402] calling scmi_reset_driver_init+0x0/0x40 @ 1
[ 0.410423] initcall scmi_reset_driver_init+0x0/0x40 returned 0 after 13 usecs
[ 0.449392] calling scmi_imx_bbm_key_driver_init+0x0/0x40 @ 1
[ 0.449416] initcall scmi_imx_bbm_key_driver_init+0x0/0x40 returned 0 after 17 usecs
[ 0.450397] calling scmi_imx_bbm_rtc_driver_init+0x0/0x40 @ 1
[ 0.450419] initcall scmi_imx_bbm_rtc_driver_init+0x0/0x40 returned 0 after 14 usecs
[ 0.454758] calling scmi_hwmon_drv_init+0x0/0x40 @ 1
[ 0.454779] initcall scmi_hwmon_drv_init+0x0/0x40 returned 0 after 16 usecs
[ 0.459798] calling scmi_cpufreq_drv_init+0x0/0x40 @ 1
[ 0.459819] initcall scmi_cpufreq_drv_init+0x0/0x40 returned 0 after 15 usecs
[ 0.466961] calling scmi_smc_driver_init+0x0/0x38 @ 1
[ 0.467663] probe of firmware:scmi-smc returned 0 after 671 usecs
[ 0.467798] initcall scmi_smc_driver_init+0x0/0x38 returned 0 after 830 usecs
[ 0.467808] calling scmi_mailbox_driver_init+0x0/0x38 @ 1
[ 0.469132] probe of firmware:scmi returned 0 after 1291 usecs
[ 0.469255] initcall scmi_mailbox_driver_init+0x0/0x38 returned 0 after 1439 usecs
[ 0.469266] calling scmi_transport_optee_init+0x0/0x38 @ 1
[ 0.469282] initcall scmi_transport_optee_init+0x0/0x38 returned 0 after 9 usecs
[ 0.469289] calling scmi_imx_bbm_init+0x0/0x30 @ 1
[ 0.469305] initcall scmi_imx_bbm_init+0x0/0x30 returned 0 after 9 usecs
[ 0.469312] calling scmi_imx_cpu_init+0x0/0x30 @ 1
[ 0.469321] initcall scmi_imx_cpu_init+0x0/0x30 returned 0 after 1 usecs
[ 0.469328] calling scmi_imx_lmm_init+0x0/0x30 @ 1
[ 0.469336] initcall scmi_imx_lmm_init+0x0/0x30 returned 0 after 2 usecs
[ 0.469345] calling scmi_imx_misc_init+0x0/0x30 @ 1
[ 0.469352] initcall scmi_imx_misc_init+0x0/0x30 returned 0 after 1 usecs
[ 0.469359] calling scmi_driver_init+0x0/0x80 @ 1
[ 0.469480] arm-scmi arm-scmi.0.auto: Using scmi_smc_transport
[ 0.469489] arm-scmi arm-scmi.0.auto: SCMI max-rx-timeout: 30ms / max-msg-size: 104bytes / max-msg: 20
[ 0.469557] smc_chan_setup: tx=1 dev=arm-scmi.0.auto cdev=scmi_dev.1
[ 0.469564] smc_chan_setup: dev->of_node=/firmware/scmi-smc cdev->of_node=/firmware/scmi-smc
[ 0.469595] scmi_protocol scmi_dev.1: Enabled polling mode TX channel - prot_id:16
[ 0.469631] smc_chan_setup: tx=0 dev=arm-scmi.0.auto cdev=scmi_dev.2
[ 0.469637] smc_chan_setup: dev->of_node=/firmware/scmi-smc cdev->of_node=/firmware/scmi-smc
[ 0.469700] arm-scmi arm-scmi.0.auto: SCMI Notifications - Core Enabled.
[ 0.469742] arm-scmi arm-scmi.0.auto: Malformed reply - real_sz:8 calc_sz:4 (loop_num_ret:1)
[ 0.469750] arm-scmi arm-scmi.0.auto: SCMI Protocol v2.0 'CIX:' Firmware version 0x0
[ 0.469786] arm-scmi arm-scmi.0.auto: Enabling SCMI Quirk [quirk_clock_rates_triplet_out_of_spec]
[ 0.470967] scmi-power-domain scmi_dev.3: SCMI power domains registered (22 domains)
[ 0.470986] probe of scmi_dev.3 returned 0 after 1048 usecs
[ 0.471008] probe of arm-scmi.0.auto returned 0 after 1563 usecs
[ 0.471046] arm-scmi arm-scmi.1.auto: Using scmi_mailbox_transport
[ 0.471053] arm-scmi arm-scmi.1.auto: SCMI max-rx-timeout: 30ms / max-msg-size: 104bytes / max-msg: 20
[ 0.471324] arm-scmi arm-scmi.1.auto: SCMI Notifications - Core Enabled.
[ 0.471691] arm-scmi arm-scmi.1.auto: SCMI Protocol v2.0 'cix:cix' Firmware version 0x20b0000
[ 0.472751] arm-scmi arm-scmi.1.auto: Failed to get FC for protocol 13 [MSG_ID:6 / RES_ID:0] - ret:-95. Using regular messaging.
[ 0.473012] arm-scmi arm-scmi.1.auto: Failed to get FC for protocol 13 [MSG_ID:8 / RES_ID:1] - ret:-95. Using regular messaging.
[ 0.473085] arm-scmi arm-scmi.1.auto: Failed to get FC for protocol 13 [MSG_ID:6 / RES_ID:1] - ret:-95. Using regular messaging.
[ 0.473166] arm-scmi arm-scmi.1.auto: Failed to get FC for protocol 13 [MSG_ID:7 / RES_ID:1] - ret:-95. Using regular messaging.
[ 0.473217] arm-scmi arm-scmi.1.auto: multiplier for domain 2 rounded
[ 0.473497] arm-scmi arm-scmi.1.auto: Failed to get FC for protocol 13 [MSG_ID:6 / RES_ID:2] - ret:-95. Using regular messaging.
[ 0.473622] arm-scmi arm-scmi.1.auto: multiplier for domain 3 rounded
[ 0.473866] arm-scmi arm-scmi.1.auto: Failed to get FC for protocol 13 [MSG_ID:6 / RES_ID:3] - ret:-95. Using regular messaging.
[ 0.473985] arm-scmi arm-scmi.1.auto: multiplier for domain 4 rounded
[ 0.474224] arm-scmi arm-scmi.1.auto: Failed to get FC for protocol 13 [MSG_ID:6 / RES_ID:4] - ret:-95. Using regular messaging.
[ 0.474343] arm-scmi arm-scmi.1.auto: multiplier for domain 5 rounded
[ 0.474817] arm-scmi arm-scmi.1.auto: Failed to get FC for protocol 13 [MSG_ID:6 / RES_ID:5] - ret:-95. Using regular messaging.
[ 0.474952] arm-scmi arm-scmi.1.auto: multiplier for domain 6 rounded
[ 0.475200] arm-scmi arm-scmi.1.auto: Failed to get FC for protocol 13 [MSG_ID:6 / RES_ID:6] - ret:-95. Using regular messaging.
[ 0.475527] arm-scmi arm-scmi.1.auto: Failed to get FC for protocol 13 [MSG_ID:8 / RES_ID:7] - ret:-95. Using regular messaging.
[ 0.475612] arm-scmi arm-scmi.1.auto: Failed to get FC for protocol 13 [MSG_ID:6 / RES_ID:7] - ret:-95. Using regular messaging.
[ 0.475684] arm-scmi arm-scmi.1.auto: Failed to get FC for protocol 13 [MSG_ID:7 / RES_ID:7] - ret:-95. Using regular messaging.
[ 0.479235] probe of scmi_dev.6 returned 0 after 7280 usecs
[ 0.479709] scmi-perf-domain scmi_dev.7: SCMI perf domains registered (12 domains)
[ 0.479724] probe of scmi_dev.7 returned 0 after 447 usecs
[ 0.574923] probe of scmi_dev.8 returned 0 after 95161 usecs
[ 0.575881] scmi-hwmon scmi_dev.9: Error enabling sensor VPU. err=-2
[ 0.575934] scmi-hwmon scmi_dev.9: Error enabling sensor GPU_btm. err=-2
[ 0.575983] scmi-hwmon scmi_dev.9: Error enabling sensor GPU_top. err=-2
[ 0.576031] scmi-hwmon scmi_dev.9: Error enabling sensor SOC_BRC. err=-2
[ 0.576081] scmi-hwmon scmi_dev.9: Error enabling sensor DDR_btm. err=-2
[ 0.576130] scmi-hwmon scmi_dev.9: Error enabling sensor DDR_top. err=-2
[ 0.576180] scmi-hwmon scmi_dev.9: Error enabling sensor CI. err=-2
[ 0.576231] scmi-hwmon scmi_dev.9: Error enabling sensor NPU. err=-2
[ 0.576281] scmi-hwmon scmi_dev.9: Error enabling sensor CPU_M1. err=-2
[ 0.576331] scmi-hwmon scmi_dev.9: Error enabling sensor CPU_B1. err=-2
[ 0.576452] scmi-hwmon scmi_dev.9: Error enabling sensor CPU_M0. err=-2
[ 0.576497] scmi-hwmon scmi_dev.9: Error enabling sensor CPU_B0. err=-2
[ 0.576543] scmi-hwmon scmi_dev.9: Error enabling sensor SOC_TRC. err=-2
[ 0.576589] scmi-hwmon scmi_dev.9: Error enabling sensor GPU_AVE. err=-2
[ 0.576634] scmi-hwmon scmi_dev.9: Error enabling sensor PCB_SOC. err=-2
[ 0.576680] scmi-hwmon scmi_dev.9: Error enabling sensor PCB_BRDG. err=-2
[ 0.576730] scmi-hwmon scmi_dev.9: Error enabling sensor PCB_CHG. err=-2
[ 0.576781] scmi-hwmon scmi_dev.9: Error enabling sensor PCB_DRAM. err=-2
[ 0.576830] scmi-hwmon scmi_dev.9: Error enabling sensor PCB_USB. err=-2
[ 0.576880] scmi-hwmon scmi_dev.9: Error enabling sensor PCB_PMIC. err=-2
[ 0.576914] probe of scmi_dev.9 returned 0 after 1874 usecs
[ 0.576932] arm-scmi arm-scmi.1.auto: SCMI protocol 129 not implemented
[ 0.576974] probe of arm-scmi.1.auto returned 0 after 105956 usecs
[ 0.576997] initcall scmi_driver_init+0x0/0x80 returned 0 after 107631 usecs
[ 0.577564] calling scmi_imx_cpu_driver_init+0x0/0x40 @ 1
[ 0.577614] initcall scmi_imx_cpu_driver_init+0x0/0x40 returned 0 after 37 usecs
[ 0.577631] calling scmi_imx_misc_ctrl_driver_init+0x0/0x40 @ 1
[ 0.577669] initcall scmi_imx_misc_ctrl_driver_init+0x0/0x40 returned 0 after 24 usecs
[ 0.577685] calling scmi_imx_lmm_driver_init+0x0/0x40 @ 1
[ 0.577729] initcall scmi_imx_lmm_driver_init+0x0/0x40 returned 0 after 30 usecs
[ 91.475418] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 91.515419] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 91.559427] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 91.595911] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 91.643914] scmi_protocol scmi_dev.4: Message for 202 type 0 is not expected!
[ 91.643955] scmi_protocol scmi_dev.5: Message for 201 type 2 is not expected!
[ 91.747432] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 91.939427] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 91.979451] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 92.019433] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 92.022206] scmi_protocol scmi_dev.5: Message for 209 type 2 is not expected!
[ 92.179448] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 92.219438] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 92.260781] scmi_protocol scmi_dev.4: Message for 213 type 0 is not expected!
[ 92.379453] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 92.427440] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 92.467446] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 92.507446] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 92.512928] scmi_protocol scmi_dev.4: Message for 218 type 0 is not expected!
[ 92.512961] scmi_protocol scmi_dev.5: Message for 217 type 2 is not expected!
[ 92.803460] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 92.843445] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 92.883453] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 92.884903] scmi_protocol scmi_dev.4: Message for 223 type 0 is not expected!
[ 92.884942] scmi_protocol scmi_dev.5: Message for 222 type 2 is not expected!
[ 93.051452] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 93.091463] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 93.137048] scmi_protocol scmi_dev.4: Message for 226 type 0 is not expected!
[ 93.239466] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 93.303464] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 93.339465] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 93.379467] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 93.381893] scmi_protocol scmi_dev.4: Message for 231 type 0 is not expected!
[ 93.381926] scmi_protocol scmi_dev.5: Message for 230 type 2 is not expected!
[ 93.551475] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 93.591475] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 93.631475] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 93.635100] scmi_protocol scmi_dev.5: Message for 235 type 2 is not expected!
[ 93.803479] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 93.843483] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 93.879951] scmi_protocol scmi_dev.4: Message for 239 type 0 is not expected!
[ 94.039486] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 94.079499] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 94.124797] scmi_protocol scmi_dev.4: Message for 242 type 0 is not expected!
[ 94.287505] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 94.327499] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 94.367497] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 94.419497] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 94.496753] scmi_protocol scmi_dev.4: Message for 247 type 0 is not expected!
[ 94.579496] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 94.659503] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 94.741599] scmi_protocol scmi_dev.4: Message for 250 type 0 is not expected!
[ 94.819504] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 94.859520] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 95.023509] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 95.063528] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 95.103516] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 95.113562] scmi_protocol scmi_dev.5: Message for 257 type 2 is not expected!
[ 95.283528] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 95.323522] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 95.365673] scmi_protocol scmi_dev.4: Message for 261 type 0 is not expected!
[ 95.483523] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 95.535529] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 95.575525] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 95.610532] scmi_protocol scmi_dev.5: Message for 265 type 2 is not expected!
[ 95.771539] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 95.807538] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 95.847551] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 95.856412] scmi_protocol scmi_dev.5: Message for 270 type 2 is not expected!
[ 96.019542] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 96.059543] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 96.108543] scmi_protocol scmi_dev.4: Message for 274 type 0 is not expected!
[ 96.211550] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 96.267547] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 96.307579] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 96.347555] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 96.353403] scmi_protocol scmi_dev.4: Message for 279 type 0 is not expected!
[ 96.353426] scmi_protocol scmi_dev.5: Message for 278 type 2 is not expected!
[ 96.519557] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 96.559557] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 96.639571] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 96.725362] scmi_protocol scmi_dev.4: Message for 284 type 0 is not expected!
[ 96.787571] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 96.827578] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 96.891655] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 96.927572] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 96.970211] scmi_protocol scmi_dev.4: Message for 289 type 0 is not expected!
[ 96.970232] scmi_protocol scmi_dev.5: Message for 288 type 2 is not expected!
[ 97.087570] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 97.139572] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 97.222361] scmi_protocol scmi_dev.4: Message for 292 type 0 is not expected!
[ 97.299573] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 97.339574] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 97.511576] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 97.551597] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 97.591588] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 97.594282] scmi_protocol scmi_dev.5: Message for 299 type 2 is not expected!
[ 97.763611] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 97.803593] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 97.846422] scmi_protocol scmi_dev.4: Message for 303 type 0 is not expected!
[ 102.363718] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
[ 102.399724] arm-scmi arm-scmi.1.auto: timed out in resp(caller: do_xfer+0x118/0x530)
The same pattern continues repeatedly for many more lines in the attached dmesg log.
Boot configuration:
menuentry '1 OrangePi 6 Plus (6.19.11) test2' {
devicetree /sky1-orangepi-6-plus-6.19.11.dtb
linux /vmlinuz-6.19.11 \
loglevel=7 ignore_loglevel log_buf_len=8M printk.devkmsg=on initcall_debug \
panic=30 panic_on_oops=1 softlockup_panic=1 hardlockup_panic=1 \
pstore.backend=ramoops \
console=ttyAMA2,115200 console=tty1 \
earlycon=pl011,0x040d0000 \
no_console_suspend \
drm.debug=0 \
efi=noruntime \
arm-smmu-v3.disable_bypass=0 \
clk_ignore_unused \
linlon_dp.enable_fb=1 \
nowatchdog watchdog_dev.handle_boot_enabled=0 \
acpi=off \
root=PARTUUID=8112a51c-af33-4033-9676-c142ea88d79d rootwait rw
initrd /initramfs-6.19.11.img
}
Important note
I do not claim that softlockup_panic=1 or hardlockup_panic=1 introduced the SCMI bug. My interpretation is that these options made the existing instability easier to observe in logs while I was investigating spontaneous freezes and reboots on this kernel.
Possible affected areas
SCMI firmware implementation
SCMI transport or mailbox layer
Clock, regulator, thermal, or DVFS integration through SCMI
Interaction with Sky1 out of tree patch set on Linux 6.19.11
How to reproduce
Build Linux 6.19.11 with the Sky1 patch set applied
Boot the board with the devicetree for OrangePi 6 Plus
Use the second boot entry shown above with softlockup_panic=1 and hardlockup_panic=1 enabled
Observe dmesg after boot and during runtime
Repeated SCMI timeout and unexpected message errors begin to appear
I will attach the full kernel .config and the complete dmesg log as attachments at the end of this report.
Files attached:
dmesg.log
config-6.19.11.txt
OBS: tested on 6.19.10, same issue.
I am reporting a kernel stability issue on a CIX Sky1 CD8180 based board running Linux 6.19.11 with the Sky1 patch set applied. After enabling additional kernel boot parameters for panic on lockups and better crash visibility, the system started showing repeated SCMI communication errors in dmesg, including response timeouts and unexpected message ordering on SCMI protocol devices.
The newly enabled boot options were added only to improve debugging and crash persistence, not to change the functional behavior of the board. Before enabling them, the system already had instability concerns and unexpected reboots or freezes. After enabling softlockup_panic=1 and hardlockup_panic=1, the kernel began to print a large amount of SCMI related errors, which strongly suggests an underlying firmware, mailbox, SCMI transport, or power management communication problem that was previously not visible so clearly in logs.
Hardware
Board: CIX Sky1 CD8180 platform, OrangePi 6 Plus class board
Firmware reports: Cix Technology Group CIX Phecda Board
Boot mode: devicetree boot
SoC family: Sky1 / CD8180
Serial console enabled on ttyAMA2
Software
Kernel: Linux 6.19.11 built with Sky1 patch set
Init system: OpenRC
Bootloader: GRUB style boot entry
ACPI disabled
BIOS: BiosV1.4-W20260130-97268c4c
Devicetree in use: sky1-orangepi-6-plus-6.19.11.dtb
Problem summary
The system shows repeated SCMI communication failures at runtime, including:
arm-scmi ... timed out in resp(caller: do_xfer+0x118/0x530)
scmi_protocol ... Message for XXX type Y is not expected!
These errors appear continuously in bursts and indicate that requests sent through SCMI are timing out, followed by responses arriving unexpectedly or out of sequence. This suggests a real bug in SCMI handling, firmware interaction, transport synchronization, or a related subsystem such as cpufreq, thermal, regulator, or DVFS integration.
The issue became clearly visible after switching from the original boot configuration to a second test configuration that added:
softlockup_panic=1
hardlockup_panic=1
These parameters were enabled only to improve lockup diagnosis and pstore crash capture. They do not appear to be the root cause themselves, but after enabling them the SCMI failures became obvious in the kernel log.
Observed errors include
Repeated SCMI response timeouts in do_xfer
Repeated unexpected SCMI protocol messages on scmi_dev.4 and scmi_dev.5
Large bursts of SCMI errors within seconds during runtime
Prior system instability and reboot investigation that motivated enabling stronger panic and debug options
Representative log excerpt
The same pattern continues repeatedly for many more lines in the attached dmesg log.
Boot configuration:
Important note
I do not claim that softlockup_panic=1 or hardlockup_panic=1 introduced the SCMI bug. My interpretation is that these options made the existing instability easier to observe in logs while I was investigating spontaneous freezes and reboots on this kernel.
Possible affected areas
SCMI firmware implementation
SCMI transport or mailbox layer
Clock, regulator, thermal, or DVFS integration through SCMI
Interaction with Sky1 out of tree patch set on Linux 6.19.11
How to reproduce
Build Linux 6.19.11 with the Sky1 patch set applied
Boot the board with the devicetree for OrangePi 6 Plus
Use the second boot entry shown above with softlockup_panic=1 and hardlockup_panic=1 enabled
Observe dmesg after boot and during runtime
Repeated SCMI timeout and unexpected message errors begin to appear
I will attach the full kernel .config and the complete dmesg log as attachments at the end of this report.
Files attached:
dmesg.log
config-6.19.11.txt
OBS: tested on 6.19.10, same issue.