I can confirm that the bug still occurs in 4.19.0-041900rc5-generic.
The first kernel on which this error occurred was 4.17.0-6-generic. Before that, I used 4.15.0-25-generic which works perfectly.
I can confirm that the bug still occurs in 4.19.0- 041900rc5- generic.
The first kernel on which this error occurred was 4.17.0-6-generic. Before that, I used 4.15.0-25-generic which works perfectly.