Noone knows? So far I've found one other phone with the same problem, possibly more. It seems that framebuffer console wants to start another framebuffer, earlier than the normal one. What happens is that the "earlier" fb starts fine, but when it's time to start the normal one, it can't as the earlier fb has a lock on. I've tried to unregister it, but without success. And when I do a query on what framebuffers are registered, it shows 0 (registered_fb).
kolmapäev, 14. märts 2012 15:30.20 UTC+2 kirjutas Rudolf Tammekivi: > > After closer inspection, the fbcon seems to have some kind of "lock" that > doesn't allow other frame buffer to take over. > > It gives a "BUG: Scheduling while atomic" on the screen, after that there > are many stack trace and then it crashes. > > I've tracked the position aswell, drivers/video/fbmem.c, in function > do_register_framebuffer and the call > fb_notifier_call_chain(FB_EVENT_FB_REGISTERED, &event); After that I get > the scheduling error messages. > > Is it because the earlier framebuffer is not unregistered? > -- unsubscribe: android-kernel+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-kernel
