> > Update: compiling the kernel without preemption seems to fix it. What's
> > needed to make critical sections in the framebuffer code preemption safe?
> > (local_irq_save() didn't help, FWIW)
>
> Ahhhhh.... that explains it ! Do no use CONFIG_PREEMPT if you want some
> thing that works ;) Preempt is a toy that isn't quite right yet
Well, it did improve responsiveness, from my experience. Shame ...
> (actually, some arch code and drivers aren't). I'm not sure what's up
> with it yet, it may be more than just adding a local_irq_save indeed.
OK, back to the drawing board. The rivafb blank problems were with
CONFIG_PREEMPT as well :-(
Michael
