Created attachment 97008 [details] [review] workaround Does that attached kernel patch fix the issue?