Good news.
Patch 628859e8621cb landed in upstream kernel since 4.16 but we have no problem on 5.0 kernel. IIRC we don't have this issue on 4.18. Looks like this is a backport problem and to revert this patch might be the fast/best way.
Good news.
Patch 628859e8621cb landed in upstream kernel since 4.16 but we have no problem on 5.0 kernel. IIRC we don't have this issue on 4.18. Looks like this is a backport problem and to revert this patch might be the fast/best way.