I have submitted this bug on 4.4 as recommended by a colleague, but the issue continued to persist in 4.9 and 4.10 in the same manner and dmesg emitted the same messages I point out here.
I have submitted this bug on 4.4 as recommended by a colleague, but the issue continued to persist in 4.9 and 4.10 in the same manner and dmesg emitted the same messages I point out here.