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

Date:	Sun, 11 Jan 2009 14:51:45 +0100
From:	"Jan Dittmer" <jdi@....org>
To:	linux-kernel@...r.kernel.org, eric.anholt@...tel.com,
	airlied@...ux.ie
Subject: intel kms "Failed to allocate space for kernel memory manager"

[ the xorg@fdo list requires subscription, so perhaps someone might forward it
  there. It would be nice if those lists had a 'quiet' subscription
mode, ie. without
  any mails. ]

Hi,

using the latest git checkout of the xf86 intel driver
(f1e9ca4e4fb3ddb083252aea79c67c5e5e71f29c),
xorg 1.5.3 and kernel 2.6.28 git head
(3d14bdad40315b54470cb7812293d14c8af2bf7d), both from
10/January, the inteldrmfb module correctly initializes the display to
its native mode (1440x900),
Lenovo X300, but X fails to start with the following error:

(WW) xf86AcquireGART: AGPIOC_ACQUIRE failed (Device or resource busy)
(EE) GARTInit: AGPIOC_INFO failed (Invalid argument)
(WW) intel(0): /dev/agpgart is either not available, or no memory is available
for allocation.  Using pre-allocated memory only.
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 10, (OK)
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 10, (OK)
drmOpenByBusid: Searching for BusID pci:0000:00:02.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 10, (OK)
drmOpenByBusid: drmOpenMinor returns 10
drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
(II) [drm] DRM interface version 1.3
(II) [drm] DRM open master succeeded.
(II) intel(0): [drm] Using the DRM lock SAREA also for drawables.
(II) intel(0): [drm] framebuffer mapped by ddx driver
(II) intel(0): [drm] added 1 reserved context for kernel
(II) intel(0): X context handle = 0x1
(II) intel(0): [drm] installed DRM signal handler
(**) intel(0): Framebuffer compression disabled
(**) intel(0): Tiling enabled
(EE) intel(0): Failed to allocate space for kernel memory manager
(==) intel(0): VideoRam: 7676 KB
(II) intel(0): Attempting memory allocation with tiled buffers.
(EE) intel(0): Failed to allocate framebuffer. Is your VideoRAM set too low?
(II) intel(0): Tiled allocation failed.
(II) intel(0): Attempting memory allocation with untiled buffers.
(EE) intel(0): Failed to allocate framebuffer. Is your VideoRAM set too low?
(II) intel(0): Untiled allocation failed.
(II) intel(0): Couldn't allocate 3D memory, disabling DRI.
(II) intel(0): Attempting memory allocation with untiled buffers.
(EE) intel(0): Failed to allocate framebuffer. Is your VideoRAM set too low?
(II) intel(0): Untiled allocation failed.
(EE) intel(0): Couldn't allocate video memory

The complete log and dmesg is attached.

Relevant xorg.conf entry:
Section "Device"
       Identifier      "Configured Video Device"
       Option "RenderAccel" "on"
       Option "XvMCSurface" "7"
       Option "XvMC" "on"
       Option "Legacy3D" "off"
EndSection

How can I fix this? As I said, the hardware is a Lenovo X300, GM965
graphics. Is this a kernel or xorg driver bug?

Thanks,

Jan

ps: Kernel Mode Setting severly lacks documentation...

-- 
Jan Dittmer <jdi@....org>

Download attachment "Xorg.0.log.dysfunc" of type "application/octet-stream" (13222 bytes)

Download attachment "dmesg.modeset" of type "application/octet-stream" (63089 bytes)