Thanks for running those two tests. The results would indicate this bug still exists in the mainline kernel and commit f548d99ef4 is not the fix for this bug.
Was there a prior kernel that did not exhibit the bug? If that is the case, and this is a regression, we can perform a kernel bisect to identify the commit that introduced the bug.
Thanks for running those two tests. The results would indicate this bug still exists in the mainline kernel and commit f548d99ef4 is not the fix for this bug.
Was there a prior kernel that did not exhibit the bug? If that is the case, and this is a regression, we can perform a kernel bisect to identify the commit that introduced the bug.