I think that it has. The 3.2 kernel is not causing this garbage to come and didnt panick. All other env is completely the same. The latest update didn't fix the problem. I've just rebooted back to 3.2 because of a cursor garbage.