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:	Sat, 7 Feb 2009 22:45:16 +0100
From:	wixor <wixorpeek@...il.com>
To:	Alexey Dobriyan <adobriyan@...il.com>
Cc:	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 did this:

    /* for dual-fb must viafb_SAMM_ON=1 and viafb_dual_fb=1 */
    if (!viafb_SAMM_ON)
        viafb_dual_fb = 0;

    DEBUG_MSG(KERN_INFO "before first ioremap\n");

    /* Set up I2C bus stuff */
    viafb_create_i2c_bus(viaparinfo);

    viafb_init_chip_info();
    viafb_get_fb_info(&viaparinfo->fbmem, &viaparinfo->memsize);
    viaparinfo->fbmem_free = viaparinfo->memsize;
    viaparinfo->fbmem_used = 0;
    viaparinfo->fbmem_virt = ioremap_nocache(viaparinfo->fbmem,
        viaparinfo->memsize);
    viafbinfo->screen_base = (char *)viaparinfo->fbmem_virt;

    if (!viaparinfo->fbmem_virt) {
        printk(KERN_INFO "ioremap failed\n");
        return -1;
    }

    DEBUG_MSG(KERN_INFO "after first ioremap\n");

    viafb_get_mmio_info(&viaparinfo->mmio_base, &viaparinfo->mmio_len);
    viaparinfo->io_virt = ioremap_nocache(viaparinfo->mmio_base,
        viaparinfo->mmio_len);

    DEBUG_MSG(KERN_INFO "after second ioremap\n");

It was the first one indeed. Full dmesg and config attached.

--
wixor

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

Download attachment "config" of type "application/octet-stream" (55628 bytes)