linux-kernel - Re: intel kms "Failed to allocate space for kernel memory manager"

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] [day] [month] [year] [list]

Message-Id: <200901121519.18693.jbarnes@virtuousgeek.org>
Date:	Mon, 12 Jan 2009 15:19:17 -0800
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	"Jan Dittmer" <jdi@....org>
Cc:	"Dave Airlie" <airlied@...il.com>,
	"Diego Calleja" <diegocg@...il.com>, linux-kernel@...r.kernel.org,
	eric.anholt@...el.com, airlied@...ux.ie
Subject: Re: intel kms "Failed to allocate space for kernel memory manager"

On Monday, January 12, 2009 2:29 pm Jan Dittmer wrote:
> On Mon, Jan 12, 2009 at 11:08 PM, Jan Dittmer <jdi@....org> wrote:
> > On Mon, Jan 12, 2009 at 10:53 PM, Jesse Barnes <jbarnes@...tuousgeek.org> 
wrote:
> >>> name of display: :0.0
> >>> libGL: XF86DRIGetClientDriverName: 1.9.0 i965 (screen 0)
> >>> libGL: OpenDriver: trying /usr/local/lib/dri/i965_dri.so
> >>> drmOpenDevice: node name is /dev/dri/card0
> >>> drmOpenDevice: open result is 4, (OK)
> >>> drmOpenByBusid: Searching for BusID pci:0000:00:02.0
> >>> drmOpenDevice: node name is /dev/dri/card0
> >>> drmOpenDevice: open result is 4, (OK)
> >>> drmOpenByBusid: drmOpenMinor returns 4
> >>> drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
> >>> libGL error: drmMap of framebuffer failed (Resource temporarily
> >>> unavailable) libGL error: reverting to software direct rendering
> >>>
> >>> ?
> >>> This is with latest mesa git libGL. Any special compilation options for
> >>> mesa?
> >>
> >> Nope, not afaik.  Are you sure UXA is enabled?  And that Mesa was built
> >> against the same libdrm bits as your 2D driver?  If so, then I guess
> >> it's time to file a bug. :)
> >
> > With the patches againg 29-rc1 from here
> > http://git.kernel.org/?p=linux/kernel/git/airlied/drm-2.6.git;a=commitdif
> >f;h=3a03ac1a0223f779a3de313523408ddb099e5679;hp=dc1336ff4fe08ae7cfe8301bfd
> >7f0b2cfd31d20a and here
> > http://groups.google.com/group/linux.kernel/msg/26aa0471cfb54b06?dmode=so
> >urce&output=gplain at least glxinfo works.
>
> Using drm-intel-next from anholt on top, I've working GL (yeah!) but
> get millions of
> [  649.472172] [drm:drm_wait_vblank] *ERROR* failed to acquire vblank
> counter, -22
> [  649.512429] [drm:drm_wait_vblank] *ERROR* failed to acquire vblank
> counter, -22
> [  649.554513] [drm:drm_wait_vblank] *ERROR* failed to acquire vblank
> counter, -22
> [  649.596972] [drm:drm_wait_vblank] *ERROR* failed to acquire vblank
> counter, -22
> [  649.638744] [drm:drm_wait_vblank] *ERROR* failed to acquire vblank
> counter, -22
>
> entries in my log. libGL says
>
> do_wait: drmWaitVBlank returned -1, IRQs don't seem to be working
> correctly. Try adjusting the vblank_mode configuration parameter.

Those errors indicate that Mesa is trying to wait on a vblank event from a 
disabled pipe.  Interrupts should work fine on the other pipe though 
(assuming you have at least *one* display going! :).

If you can get a backtrace of what's calling this, we should be able to fix 
Mesa to prevent it.

-- 
Jesse Barnes, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/