On Tue, Apr 26, 2011 at 2:38 PM, warmcat <email address hidden> wrote:
> Seems to be two different issues, one is the original bug report and
> this other random thing.
It's actually the same thing. The problematic part here is the
GFX_FIFO_UNDERFLOW, that disables the GFX and then you need to blank
it again if you want to have your screen back.
> On my tree, with my config, I don't see this at all. Blanking occurs
> but I can every time bring it back by waving the mouse a couple of
> seconds without these errors.
That's fine, it also works the same way with our kernel. The underflow
issue happened when I was using the board, not when it was idle.
> Is the kernel you're seeing this with maybe having CPU_FREQ enabled?
> I'm running with it disabled.
On Tue, Apr 26, 2011 at 2:38 PM, warmcat <email address hidden> wrote:
> Seems to be two different issues, one is the original bug report and
> this other random thing.
It's actually the same thing. The problematic part here is the
GFX_FIFO_UNDERFLOW, that disables the GFX and then you need to blank
it again if you want to have your screen back.
> On my tree, with my config, I don't see this at all. Blanking occurs
> but I can every time bring it back by waving the mouse a couple of
> seconds without these errors.
That's fine, it also works the same way with our kernel. The underflow
issue happened when I was using the board, not when it was idle.
> Is the kernel you're seeing this with maybe having CPU_FREQ enabled?
> I'm running with it disabled.
It's also disabled for Natty.