Are you sure 9c3f3794 fixes it? I'm not a kernel expert but since the backtrace differs and, according to the commit message, I'd say it's a different issue.
We could try backporting it manually and check but maybe reverting 2ad4caea651 suffices until
ubuntu guys fix the bug in a future tag?
Are you sure 9c3f3794 fixes it? I'm not a kernel expert but since the backtrace differs and, according to the commit message, I'd say it's a different issue.
We could try backporting it manually and check but maybe reverting 2ad4caea651 suffices until
ubuntu guys fix the bug in a future tag?