On 4/23/2012 12:43:11 Pierre-Louis Bossart wrote :
I'm the one who introduced this warning when I added support for a better delay estimate based on the frame counter instead of bytes submitted (back in September 2011). When writing new data the estimate using the frame counter and the byte count should be identical, but this message shows something goes wrong. Somehow I don't understand how a more precise delay would cause such errors. The delay is only important for pulseaudio, it shouldn't affect plain vanilla alsa.
Could the delay not be the cause, but a side effect ? Unfortunately I don't know anything about the internals here.
What I do know is that there is a lapdesk of another series by the same vendor, that has exactly the same behaviour. I do know those two lapdesks work fine under other OSes.
The problem can also be reproduced under various Linux distributions.
Do you have any idea why keeping my CPU busy removes the problem ? That could be a hint as to where the real problem lies.
You could try and reverse the patch to see if this improves anything? If not, you have another problem in your setup...
By reversing the patch, I made the problem worse.
Is there a way to get more debugging information ? I already tried to get some output with xrun_debug as pointed in the wiki, but things don't look weird to me (I only get logs about hwptr_update and period_update)