linux-kernel - Re: viafb triggers BUG at mm/vmalloc.c:294 [kernel 2.6.28.3]

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 9 Feb 2009 12:48:22 +0100
From:	wixor <wixorpeek@...il.com>
To:	Nick Piggin <nickpiggin@...oo.com.au>
Cc:	Alexey Dobriyan <adobriyan@...il.com>,
	Arjan van de Ven <arjan@...radead.org>,
	JosephChan@....com.tw, linux-kernel@...r.kernel.org
Subject: Re: viafb triggers BUG at mm/vmalloc.c:294 [kernel 2.6.28.3]

Okay, I'm not quite sure what's happening here (i'm not kernel
developer). That's that I've done:
    printk(KERN_DEBUG "alloc_vmap_area(%lu, %lu, %p,
%p)\n",size,align,vstart,vend);
at the very beginning of alloc_vmap_area,
    printk(KERN_DEBUG "alloc_vmap_area: allocated %p -
%p\n",va->va_start, va->va_end);
at very end and
        WARN(1,KERN_WARNING "alloc_vmap_area failed\n");
before returning EBUSY. Full dmesg attached. What still bugs me is
that video ram is allocated from system memory by bios. Does the
kernel know that and does it try to allocate the framebuffer in that
"video ram"?

Download attachment "dmesg" of type "application/octet-stream" (43477 bytes)