Comment 11 for bug 732912

In response to Jamie's question (Amitk will know better). Display driver hw sucks from ram and blows to an lcd or other graphics . It has to keep up a certain speed to keep the output side happy. To deal with occasional starving on the input side there is usually a fifo. A deeper fifo can help smooth out times when the bus on the input side is over taxed like when some other higher priority block is using lots of memory band width. When the fifo goes completely empty and cannot provide data fast enough for the output that is an underflow which what is happening here.

So the interesting new bit of news is that this apparently happens with the CPU_FREQ scheduler gets set to ondemand. My understanding is that should only be adjusting the CPU clock and not a peripheral clock like the display controller. So this "shouldn't happen".