I can confirm this issue on a system running 2.6.31.16. The steps laid out in #12 do not have any effect at stopping the issue on 2.6.31.16.
I can confirm this issue on a system running 2.6.31.16. The steps laid out in #12 do not have any effect at stopping the issue on 2.6.31.16.