On Thu, Feb 24, 2011 at 5:20 AM, Anca Emanuel <anca.emanuel@xxxxxxxxx> wrote: >> >> Every boot? > > Yes. > >> And just out of interest, what happens if you don't have the vesafb >> driver at all? > > I used 'e' option from grub, removed the 'set gfxpayload = $linux_gfx_mode' > and it works. > > dmesg: http://pastebin.com/JAZsk4vD Hmm. So it definitely seems to be the hand-over. Does this patch make any difference? When we unregister the old framebuffer, we still leave it in the registered_fb[] array, which looks wrong. But it would also be interesting to hear if setting CONFIG_SLUB_DEBUG_ON or CONFIG_DEBUG_PAGEALLOC makes any difference (they'd help detect accesses to free'd data structures). Linus
drivers/video/fbmem.c | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/drivers/video/fbmem.c b/drivers/video/fbmem.c index e2bf953..e8f8925 100644 --- a/drivers/video/fbmem.c +++ b/drivers/video/fbmem.c @@ -1511,6 +1511,7 @@ void remove_conflicting_framebuffers(struct apertures_struct *a, "%s vs %s - removing generic driver\n", name, registered_fb[i]->fix.id); unregister_framebuffer(registered_fb[i]); + registered_fb[i] = NULL; } } }
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
