Suggested Next Steps
1. Recommend enable hardlockup_panic=1 and configure kdump so the next
occurrence captures a vmcore with a full stack trace. This is critical for
root-cause analysis: echo 1 >
/proc/sys/kernel/hardlockup_panic
2. Recommend test with the latest HWE kernel (6.17.0-29 is available) to check
if this is already fixed.
3. Investigate the interaction between rapid veth interface cycling and the
ath10k firmware stats WMI path. The ath10k_debug_fw_stats_request() loop
(debug.c:367) could become pathological if the firmware is
stuck processing network events from veth churn.
4. Check upstream ath10k mailing list ([email protected]) for known
issues with QCA6174 firmware WLAN.RM.4.4.1-00309- under heavy interface cycling.
5. Consider linux-firmware: firmware version WLAN.RM.4.4.1-00309- may have a
known firmware hang path — check if a newer firmware is available for QCA6174
hw3.2.
** Changed in: linux-hwe-6.17 (Ubuntu)
Assignee: (unassigned) => Mehmet Basaran (mehmetbasaran)
** Changed in: linux-hwe-6.17 (Ubuntu)
Assignee: Mehmet Basaran (mehmetbasaran) => (unassigned)
** Changed in: linux-hwe-6.17 (Ubuntu)
Assignee: (unassigned) => AceLan Kao (acelankao)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2152582
Title:
ath10k firmware timeout causes hard lockup on CPU6 when veth
interfaces cycle repeatedly (Docker restart loop)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.17/+bug/2152582/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
