On Tue, Jul 19, 2016 at 08:41:21AM +0000, Joakim Tjernlund wrote: > > Did you try it or at least the kernel which contains it ? It is important > > No I haven't. I myself do not have such a laptop so I must find someone that does > and willing to test stuff for me(I maintain our Linux DE used for in-house development) > All I can say for sure is that 4.1.x works and 4.4.x does not :( OK that's already a good indication. (...) > Yes I get that but I figured that a upstream commit that is marked: > Cc: <stable@xxxxxxxxxxxxxxx> # v4.2+ > already was approved for stable and it would find its way into all relevant branches. Indeed it could be one candidate, so if you can afford to wait for a next release to see if it fixes your problem that's the easiest way. Otherwise you'll have to bisect either between 4.1 and 4.4 to find which one broke, or to test mainline to see if it's fixed again. But given that it was a regression, it's likely that someone else will notice it and propose a fix (possibly the one above). Willy -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html