Qualcommax: nss_port5_rx_clk_src: rcg didn't update its configuration

For a while I thought that the error that I noted in GL-iNet AX1800 new router - OpenWrt support? - #710 by dr-m had been magically fixed, but it seems that it can take several hours or even days between the messages. Below I’m reproducing the first stack trace from the dmesg output of my router, as well as all subsequent messages of the similar type (omitting the stack traces):

[38385.954253] nss_port5_rx_clk_src: rcg didn't update its configuration.
[38385.954287] WARNING: CPU: 3 PID: 576 at drivers/clk/qcom/clk-rcg2.c:133 update_config+0xac/0xb8
[38385.964246] Modules linked in: pppoe ppp_async nft_fib_inet nf_flow_table_inet ath11k_ahb(O) ath11k(O) pppox ppp_generic nft_reject_ipv6 nft_reject_ipv4 nft_reject_inet nft_reject nft_redir nft_quota nft_numgen nft_nat nft_masq nft_log nft_limit nft_hash nft_flow_offload nft_fib_ipv6 nft_fib_ipv4 nft_fib nft_ct nft_chain_nat nf_tables nf_nat nf_flow_table nf_conntrack mac80211(O) cfg80211(O) slhc qrtr_smd qrtr qmi_helpers(O) nfnetlink nf_reject_ipv6 nf_reject_ipv4 nf_log_syslog nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c hwmon crc_ccitt compat(O) sha512_generic sha512_arm64 seqiv sha3_generic jitterentropy_rng drbg michael_mic hmac geniv cmac leds_gpio xhci_plat_hcd xhci_pci xhci_hcd dwc3 dwc3_qcom qca_nss_dp(O) qca_ssdk(O) gpio_button_hotplug(O) ext4 mbcache jbd2 crc32c_generic
[38386.019353] CPU: 3 PID: 576 Comm: kworker/3:5 Tainted: G           O       6.6.87 #0
[38386.041588] Hardware name: GL.iNet GL-AX1800 (DT)
[38386.049397] Workqueue: events qca_mac_sw_sync_work_task [qca_ssdk]
[38386.053999] pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[38386.060075] pc : update_config+0xac/0xb8
[38386.066928] lr : update_config+0xac/0xb8
[38386.071094] sp : ffffffc0822dbab0
[38386.075000] x29: ffffffc0822dbab0 x28: 000000000000000a x27: ffffff8002800010
[38386.078219] x26: ffffffc078f57490 x25: ffffffc078f54bc8 x24: ffffffc0822dbd50
[38386.085336] x23: ffffff80023de600 x22: 0000000007735940 x21: ffffffc080a44828
[38386.092454] x20: ffffffc080d0c6b0 x19: 0000000000000000 x18: ffffffc080c7bd78
[38386.099572] x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000129
[38386.106691] x14: 0000000000000129 x13: 00000000ffffffea x12: ffffffc080cd3d20
[38386.113809] x11: ffffffc080c7bd78 x10: ffffffc080cd3d78 x9 : 0000000000000001
[38386.120928] x8 : 0000000000000001 x7 : 0000000000017fe8 x6 : 0000000000000001
[38386.128045] x5 : ffffff801fed1750 x4 : 0000000000000000 x3 : 0000000000000027
[38386.135163] x2 : 0000000000000027 x1 : 0000000000000023 x0 : 000000000000003a
[38386.142283] Call trace:
[38386.149390]  update_config+0xac/0xb8
[38386.151651]  clk_rcg2_configure+0x84/0x94
[38386.155470]  clk_rcg2_set_rate_and_parent+0x64/0x80
[38386.159377]  clk_change_rate+0x7c/0x294
[38386.164063]  clk_core_set_rate_nolock+0x15c/0x25c
[38386.167884]  clk_set_rate+0x38/0x14c
[38386.172743]  ssdk_uniphy_clock_rate_set+0x48/0xbc [qca_ssdk]
[38386.176393]  ssdk_port_speed_clock_set+0xb4/0x184 [qca_ssdk]
[38386.182036]  adpt_hppe_port_bridge_txmac_set+0xbc/0x2d8 [qca_ssdk]
[38386.187678]  adpt_hppe_gcc_port_speed_clock_set+0xdc/0x1d0 [qca_ssdk]
[38386.193669]  qca_hppe_mac_sw_sync_task+0x640/0xb7c [qca_ssdk]
[38386.200179]  qca_mac_sw_sync_work_task+0x44/0x3d8 [qca_ssdk]
[38386.205907]  process_one_work+0x17c/0x2f4
[38386.211633]  worker_thread+0x2f4/0x4dc
[38386.215539]  kthread+0xdc/0xe0
[38386.219184]  ret_from_fork+0x10/0x20
[38386.222224] ---[ end trace 0000000000000000 ]---
[38386.226916] ------------[ cut here ]------------
[38386.230558] nss_port5_tx_clk_src: rcg didn't update its configuration.
…
[38409.394077] nss_port5_rx_clk_src: rcg didn't update its configuration.
…
[42693.692886] nss_port5_rx_clk_src: rcg didn't update its configuration.
…
[42693.975102] nss_port5_tx_clk_src: rcg didn't update its configuration.
…
[42716.083906] nss_port5_rx_clk_src: rcg didn't update its configuration.
…
[42716.359519] nss_port5_tx_clk_src: rcg didn't update its configuration.
…
[63842.006254] nss_port5_rx_clk_src: rcg didn't update its configuration.
…
[63842.281866] nss_port5_tx_clk_src: rcg didn't update its configuration.
…
[469451.034818] nss_port5_rx_clk_src: rcg didn't update its configuration.
…
[469451.313729] nss_port5_tx_clk_src: rcg didn't update its configuration.
…
[471792.618296] nss_port5_rx_clk_src: rcg didn't update its configuration.
…
[471792.897207] nss_port5_tx_clk_src: rcg didn't update its configuration.
…
[471816.058305] nss_port5_rx_clk_src: rcg didn't update its configuration.
…
[471816.337230] nss_port5_tx_clk_src: rcg didn't update its configuration.
…
[944893.588781] nss_port5_rx_clk_src: rcg didn't update its configuration.
…
[944893.867690] nss_port5_tx_clk_src: rcg didn't update its configuration.
…
[944917.028623] nss_port5_rx_clk_src: rcg didn't update its configuration.
…
[944917.307532] nss_port5_tx_clk_src: rcg didn't update its configuration.
…
[1017727.465957] nss_port5_rx_clk_src: rcg didn't update its configuration.
…
[1017727.748181] nss_port5_tx_clk_src: rcg didn't update its configuration.
…
[1017750.905835] nss_port5_rx_clk_src: rcg didn't update its configuration.
…
[1017751.188053] nss_port5_tx_clk_src: rcg didn't update its configuration.

I haven’t tried applying the patch that had previously fixed the problem for me. I did find a recent change https://github.com/openwrt/openwrt/pull/18795 which might be related to this. I will upgrade and see what happens.

1 Like

Yesterday, now that https://firmware-selector.openwrt.org/ is available again, I upgraded to a fresh snapshot that is based on a 6.12 kernel. In git history I found that target/linux/qualcommax/patches-6.6/0044-v6.10-clk-qcom-gcc-ipq8074-rework-nss_port5-6-clock-to-mul.patch was removed as part of removing the 6.6 patches. The only references to nss_port5_rx_clk in the current 6.12 based main branch are in the files target/linux/qualcommax/files/arch/arm64/boot/dts/qcom/ipq*-ess.dtsi which are part of the upstream Linux kernel.

In other words, whatever the issue was, was likely related to the backported patches. My router has now been running more than 78,000 seconds and there is no message like this in dmesg. I will check again after some days before declaring this problem solved.