On Tue, May 26, 2015 at 02:37:02PM -0700, Alexandr Morozov wrote: > Ah, sorry. I though it is possible to backport fix to other stable > branches like 3.18 and 3.19. We use 3.19.6 and 3.18.14, seems like > 3.18.14 is last longterm on kernel.org, we can try 3.19.8 too. > Sorry, I might hit wrong maillist for such problem, let me know. We'll > try 3.19.8 in meantime. No that's the right list if you want to contact stable kernel maintainers (including Sasha who maintains 3.18). What you may have to do since you seem to reliably reproduce the issue is to check between 4.0.1 and 4.0.2 which patch fixed the bug, and ensure it gets backported into 3.18. It is possible that it was not identified as needing to be backported. Maybe first wait for the next 3.18 in case the fix is already queue and bisect after that if next 3.18 doesn't fix your issue. Hoping this helps, 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