The bug seems to be fixed in current stable. After fast-forward upgrade from 2.6.32-30 to 2.6.32-34squeeze1, the trip points have remained exactly the same (see previous email). Pavel