Since the problem is now reported on 2.6.32, I'm opening it against "linux" and putting 2.6.20 back to invalid.
Since the problem is now reported on 2.6.32, I'm opening it against "linux" and putting 2.6.20 back to invalid.