(In reply to Johan Thorén from comment #29)
> I've now verified that the error still occurs with or without that command
> issued, especially when coming back from suspend.
hmm, i was expecting this command to improve the issue, if it would improve the issue, then we could think of a watermark issue.
(In reply to Johan Thorén from comment #29)
> I've now verified that the error still occurs with or without that command
> issued, especially when coming back from suspend.
hmm, i was expecting this command to improve the issue, if it would improve the issue, then we could think of a watermark issue.