I see elsewhere noted that this does not occur on 3.2.0-16 but does on 3.2.0-24, a logical test would be to try the interviening kernels and confirm where this was introduced.
I see elsewhere noted that this does not occur on 3.2.0-16 but does on 3.2.0-24, a logical test would be to try the interviening kernels and confirm where this was introduced.