Re: [PATCH net v7 0/6] net: wwan: t7xx: fix TX push kthread soft lockup on suspend and RX stop issues

From: Tim JH Chen

Date: Thu Nov 19 2026 - 21:42:47 EST


> - Whether the issue was actually triggered, or is only theoretical
> (e.g. found by LLM and not proven at runtime). If it was triggered
> please include the symptoms, like the stack trace or kernel messages.

Per patch:

1/6: Triggered. Soft lockup in an s2idle rtcwake loop (SIM registered,
ASPM L1 enabled) on 6.19 with the unmodified driver, on the 981st
cycle, captured with kdump:

watchdog: BUG: soft lockup - CPU#4 stuck for 26s! [dpmaif_tx_hw_pu:764]
RIP: 0010:ktime_get_mono_fast_ns+0x2e/0xe0
Call Trace:
? t7xx_pci_enable_sleep+0x44/0x90 [mtk_t7xx]
t7xx_dpmaif_tx_hw_push_thread+0x1f9/0x490 [mtk_t7xx]
kthread+0x10b/0x220

With the series applied, 10024 cycles of the same loop completed
without a soft lockup.

2/6 and 3/6: Not observed; found by code review. -EACCES is only
returned while runtime PM is disabled and the device is not active,
and I have not seen these paths hit at runtime.

4/6: Triggered in the field, reported by Andreas Haerter on the v6
thread (Closes: link in the patch). After "SAP suspend error: -110"
every runtime resume failed, the TX push kthread exited, and a later
write to the PCI remove attribute crashed in kthread_stop() with a
NULL worker_private and then hung in D state.

5/6: The symptom was triggered, the exact path is not proven. In two
overnight runs on 6.19 with an earlier test build that did not have
this patch, a modem exception was followed by closing the wwan netdev
hanging in napi_synchronize() with rtnl held, and every other rtnl
user hung behind it:

NetworkManager:
msleep
t7xx_ccmni_disable_napi+0x42
t7xx_ccmni_close
__dev_close_many
__dev_change_flags
netif_change_flags
do_setlink
__rtnl_newlink
rtnl_newlink

The not-started early return that this patch fixes is the path I
believe left NAPI_STATE_SCHED set, but I did not capture the poll
itself. With the patch applied, "Work RXQ: 1 has not been started" was
logged twice in a later run without a hang, but no modem exception
occurred in that run, so the exception case is not verified on
hardware.

6/6: Not observed; found by code review.