I've seen this as well (on an xM) but can't reproduce it on 2.6.35-1006.12, so the commit mentioned by John must have fixed this.
I've seen this as well (on an xM) but can't reproduce it on 2.6.35-1006.12, so the commit mentioned by John must have fixed this.