What about just checking the time before and after the nanosleep and if it lasted longer than expected bumping the text two pixels instead of one? That would keep you from burning excess CPU and (assuming this problem doesn't happen for every call) still keep the scrolling relatively smooth.

-Mike