Just checked: the bug still persists with 2.6.35-17 and does not occur with mainline 2.6.35.2 (2.6.35-02063502).
Just checked: the bug still persists with 2.6.35-17 and does not occur with mainline 2.6.35.2 (2.6.35-02063502).