Hi, IIUC, this was long since fixed at the time of your v6.0.8 report. The mainline fix is 557d19675a470bb0a98beccec38c5dc3735c20fa, which was backported to stable (v6.0.16) via 7e686013b7071f4c16644cfad8808e76097724c4. Please try to check more recent kernels prior to reporting. Cheers, David