Bug 22226 - [945] DRI memory manager reports 18014398509481940 kB
Summary: [945] DRI memory manager reports 18014398509481940 kB
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: Other All
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-11 01:07 UTC by Priit Laes (irc: plaes)
Modified: 2017-07-24 23:10 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description Priit Laes (irc: plaes) 2009-06-11 01:07:20 UTC 
Xorg.0.log:
[snip]
(II) AIGLX: Resuming AIGLX clients after VT switch
(II) intel(0): Fixed memory allocation layout:
(II) intel(0): 0x00000000-0xffffffffffff4fff: DRI memory manager (18014398509481940 kB)
(II) intel(0): 0x00000000:            end of aperture
(II) intel(0): BO memory allocation layout:
(II) intel(0): 0x00000000:            start of memory manager
(II) intel(0): 0x00c00000-0x00ffffff: front buffer (4096 kB) X tiled
(II) intel(0): 0x00b00000-0x00b09fff: HW cursors (40 kB)
(II) intel(0): 0xffffffffffff5000:            end of memory manager
[/snip]

Chipset: 945GM
(--) PCI:*(0@0:2:0) Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller rev 3, Mem @ 0xee100000/524288, 0xd0000000/268435456, 0xee200000/262144, I/O @ 0x00001800/8
(--) PCI: (0@0:2:1) Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller rev 3, Mem @ 0xee180000/524288

Kernel: 2.6.30
Arch: x86_64
Distro: Gentoo
Machine: Lenovo x60s (Thinkpad)

x11-libs/libdrm-2.4.11
media-libs/mesa-7.4.2
x11-base/xorg-server-1.6.1.901-r3
x11-drivers/xf86-video-intel-2.7.1
Comment 1 Jesse Barnes 2009-06-16 18:23:05 UTC 
Should be fixed by this commit, which will be in 2.8.

commit 1c68bc376a9cb3c0a010c8e28f69a776755c8f64
Author: Jesse Barnes <jbarnes@virtuousgeek.org>
Date:   Wed May 13 13:19:53 2009 -0700

    Add new have_gem flag

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.