Closed DiegoDassie closed 2 years ago
sorry, don't know much about that, i mostly focus on the user space, not the kernel side.
from a quick check about the log and related code, it looks like a mutex(rport->mutex) been held after exited the charger detect work, which might be expected(not a good practice though), since it seems like a state machine, and would unlock it somewhere else.
so it might or might not related to your hang. for a hang, normally people might need to check with fiq/watchdog/jtag
Goodmorning Jeffy,
I have been running the rockchip kernel 4.19 _(kernel-4.19-2022_0118) on my Yocto for a custom RK3399 board and noticed that sometimes at startup a non fatal kernel hang is reported from the USB subsystem, because I'm not able to easily reproduce the hang I decided to investigate and enabled the kernel lock debugging I think I found a possible deadlock that seems to be related to the USB hang I am getting, here is the relevant kernel log:
Do you think you could take a look at it?
Thanks.