Bug 13179 - 4x repeated - xf86AllocateGARTMemory: allocation of 10 pages failed
Summary: 4x repeated - xf86AllocateGARTMemory: allocation of 10 pages failed
Status: RESOLVED NOTABUG
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: git
Hardware: Other All
: medium minor
Assignee: Wang Zhenyu
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-11-11 04:02 UTC by CIJOML CIJOMLovic CIJOMLov
Modified: 2008-01-06 18:38 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description CIJOML CIJOMLovic CIJOMLov 2007-11-11 04:02:54 UTC
Hi,

maybe this could be told only one times?
------------

drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 8, (OK)
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 8, (OK)
drmOpenByBusid: Searching for BusID pci:0000:00:02.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 8, (OK)
drmOpenByBusid: drmOpenMinor returns 8
drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
(II) intel(0): [drm] DRM interface version 1.3
(II) intel(0): [drm] created "i915" driver at busid "pci:0000:00:02.0"
(II) intel(0): [drm] added 8192 byte SAREA at 0xf8938000
(II) intel(0): [drm] mapped SAREA 0xf8938000 to 0xb7b95000
(II) intel(0): [drm] framebuffer handle = 0xe8000000
(II) intel(0): [drm] added 1 reserved context for kernel
(WW) intel(0): Removed DRI frontbuffer mapping in compatibility mode.
(WW) intel(0): DRIGetDeviceInfo will report incorrect frontbuffer handle.
(==) intel(0): VideoRam: 131072 KB
(**) intel(0): Framebuffer compression enabled
(**) intel(0): Tiling enabled
(II) intel(0): Attempting memory allocation with tiled buffers.
(WW) intel(0): xf86AllocateGARTMemory: allocation of 1536 pages failed
        (Cannot allocate memory)
(WW) intel(0): Allocation error, framebuffer compression disabled
(WW) intel(0): xf86AllocateGARTMemory: allocation of 10 pages failed
        (Cannot allocate memory)
(WW) intel(0): Failed to allocate EXA offscreen memory.
(II) intel(0): Attempting memory allocation with untiled buffers.
(WW) intel(0): xf86AllocateGARTMemory: allocation of 10 pages failed
        (Cannot allocate memory)
(WW) intel(0): Failed to allocate texture space.
(WW) intel(0): Not enough video memory.  Disabling DRI.
(WW) intel(0): xf86AllocateGARTMemory: allocation of 10 pages failed
        (Cannot allocate memory)
(EE) intel(0): Cannot support DRI with frame buffer width > 2048.
(II) intel(0): adjusting plane->pipe mappings to allow for framebuffer compression
(II) intel(0): Page Flipping disabled
(==) intel(0): Write-combining range (0xe8000000,0x8000000)
(II) intel(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000
(WW) intel(0): EXA compatibility mode.  Output rotation rendering performance may suffer
(II) EXA(0): Offscreen pixmap area of 49545216 bytes
(II) EXA(0): Driver registered support for the following operations:
(II)         Solid
(II)         Copy
(II)         Composite (RENDER acceleration)
(==) intel(0): Backing store disabled
(==) intel(0): Silken mouse enabled
(II) intel(0): Initializing HW Cursor
(
Comment 1 Wang Zhenyu 2008-01-03 22:06:53 UTC
Those allocation failure message just happens when we try if large memory pages
allocation could succeed in kernel, which require continual physical pages that
will probably fail. If then, we fall back to splitted pages or disable features.

The message is harmless, and from xserver's xfree86 agp code so driver can't disable it...

Do you have real problems in your case?

Comment 2 CIJOML CIJOMLovic CIJOMLov 2008-01-04 08:18:36 UTC
Not have problems, just seen it in log. Maybe Option switch could be interduced to directly use splitted pages...
Comment 3 Wang Zhenyu 2008-01-06 18:38:16 UTC
I don't think we need new option for this, maybe tell user following failure message is from driver trials, and is harmless. :)

So I'm closing this one now.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.