Instead of trying the 3.5-rc2 kernel listed above, the first time, I tried the current mainline 3.6.0. Unfortunately this bug is back in 3.6.0.
Using 3.5-rc2 does fix this bug.
Instead of trying the 3.5-rc2 kernel listed above, the first time, I tried the current mainline 3.6.0. Unfortunately this bug is back in 3.6.0.
Using 3.5-rc2 does fix this bug.