If the bug still exists in v3.10-rc1, I can perform a kernel bisect to identify the commit that introduced this regression in 3.9.0-1
If the bug still exists in v3.10-rc1, I can perform a kernel bisect to identify the commit that introduced this regression in 3.9.0-1