I am sorry that need your assistance here. Please also tell us if there is an easy way to reproduce this issue on pure devkit. We tried to reproduce this issue for several times but always not able to trigger it. or maybe you could tell us the reproduce rate so that we can estimate how many times we need to hit it.
(although running the system at a higher load seems to trigger it more often).
We were told this info by another customer too. He told us when device is in high temperature, it is easy to hit this issue. As you know high temperature just indicates high workload.
I was looking at the pinmux spreadsheet again. Where does that pin go? It is highlighted in yellow (GPIO), but is it accessible anywhere? Thanks.
This gpio pin is registered by the bluedroid_pm driver to be used for IRQ. That is why the first workaround is to remove this driver. But it is not a good solution I think.