On Saturday 08 Jan 2011 00:16:40 Thomas Lübking wrote:
>
> Can you actually confirm that the RAM hunger is distributed evenly among
> your running applications ("top") and not everything is just sucked by
> only one (X11?) process?
>
> Usually graphical stuff (including and good god esp. opengl) ends up in
> your VRAM (ie. on the GPU), you can query the used X11 resources by
> "xrestop"
>
> in doubt: ask your distro whether they run anything (everything...) by
> "--graphicssystem raster" and then tell them to stop doing this ;-)
>
> > I would have expected that opengl should put stuff into system memory as
> > it's ment to do it's own memory mangement, at least for some stff etc...
>
Ok, I've loged out of KDE and back in again .
/var/log/Xorg.0.log looks like this around the nvidia driver details.
(II) Module wfb: vendor="X.Org Foundation"
compiled for 1.7.6, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.4
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"
(II) Module "ramdac" already built-in
(II) NVIDIA(0): Creating default Display subsection in Screen section
"Default Screen" for depth/fbbpp 24/32
(**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
(==) NVIDIA(0): RGB weight 888
(==) NVIDIA(0): Default visual is TrueColor
(==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
(**) NVIDIA(0): Option "NoLogo" "True"
(**) Jan 07 05:25:59 NVIDIA(0): Enabling RENDER acceleration
(II) Jan 07 05:25:59 NVIDIA(0): Support for GLX with the Damage and Composite
X extensions is
(II) Jan 07 05:25:59 NVIDIA(0): enabled.
(II) Jan 07 05:26:00 NVIDIA(0): NVIDIA GPU GeForce 7900 GS (G71) at PCI:1:0:0
(GPU-0)
(--) Jan 07 05:26:00 NVIDIA(0): Memory: 524288 kBytes
(--) Jan 07 05:26:00 NVIDIA(0): VideoBIOS: 05.71.22.39.00
(II) Jan 07 05:26:00 NVIDIA(0): Detected PCI Express Link width: 16X
(--) Jan 07 05:26:00 NVIDIA(0): Interlaced video modes are supported on this
GPU
(--) Jan 07 05:26:00 NVIDIA(0): Connected display device(s) on GeForce 7900 GS
at PCI:1:0:0
(--) Jan 07 05:26:00 NVIDIA(0): Idek Iiyama (CRT-0)
(--) Jan 07 05:26:00 NVIDIA(0): Idek Iiyama (CRT-0): 400.0 MHz maximum pixel
clock
(II) Jan 07 05:26:00 NVIDIA(0): Assigned Display Device: CRT-0
(==) Jan 07 05:26:00 NVIDIA(0):
(==) Jan 07 05:26:00 NVIDIA(0): No modes were requested; the default mode
"nvidia-auto-select"
(==) Jan 07 05:26:00 NVIDIA(0): will be used as the requested mode.
(==) Jan 07 05:26:00 NVIDIA(0):
(II) Jan 07 05:26:00 NVIDIA(0): Validated modes:
(II) Jan 07 05:26:00 NVIDIA(0): "nvidia-auto-select"
(II) Jan 07 05:26:00 NVIDIA(0): Virtual screen size determined to be 1600 x
1200
(--) Jan 07 05:26:00 NVIDIA(0): DPI set to (112, 112); computed from
"UseEdidDpi" X config
(--) Jan 07 05:26:00 NVIDIA(0): option
(==) Jan 07 05:26:00 NVIDIA(0): Enabling 32-bit ARGB GLX visuals.
(--) Depth 24 pixmap format is 32 bpp
(II) Jan 07 05:26:00 NVIDIA(0): Initialized GPU GART.
(II) Jan 07 05:26:00 NVIDIA(0): ACPI: failed to connect to the ACPI event
daemon; the daemon
(II) Jan 07 05:26:00 NVIDIA(0): may not be running or the
"AcpidSocketPath" X
(II) Jan 07 05:26:00 NVIDIA(0): configuration option may not be set
correctly. When the
(II) Jan 07 05:26:00 NVIDIA(0): ACPI event daemon is available, the NVIDIA
X driver will
(II) Jan 07 05:26:00 NVIDIA(0): try to use it to receive ACPI event
notifications. For
(II) Jan 07 05:26:00 NVIDIA(0): details, please see the "ConnectToAcpid"
and
(II) Jan 07 05:26:00 NVIDIA(0): "AcpidSocketPath" X configuration options
in Appendix B: X
(II) Jan 07 05:26:00 NVIDIA(0): Config Options in the README.
(II) Jan 07 05:26:00 NVIDIA(0): Setting mode "nvidia-auto-select"
(II) Loading extension NV-GLX
(II) Jan 07 05:26:00 NVIDIA(0): Initialized OpenGL Acceleration
(==) NVIDIA(0): Disabling shared memory pixmaps
(II) Jan 07 05:26:00 NVIDIA(0): Initialized X Rendering Acceleration
(==) NVIDIA(0): Backing store disabled
(==) NVIDIA(0): Silken mouse enabled
(==) NVIDIA(0): DPMS enabled
(II) Loading extension NV-CONTROL
(II) Loading extension XINERAMA
(==) RandR enabled
(II) Initializing built-in extension Generic Event Extension
(II) Initializing built-in extension SHAPE
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension BIG-REQUESTS
(II) Initializing built-in extension SYNC
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-MISC
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) Initializing extension GLX
-----SNIP---------
(II) Logitech USB RECEIVER: Close
(II) UnloadModule: "evdev"
(II) Open ACPI successful (/var/run/acpid.socket)
(II) APM registered successfully
(II) Jan 08 05:14:38 NVIDIA(0): Initialized GPU GART.
(II) Jan 08 05:14:38 NVIDIA(0): Setting mode "nvidia-auto-select"
(II) Jan 08 05:14:38 NVIDIA(0): Initialized OpenGL Acceleration
(==) NVIDIA(0): Disabling shared memory pixmaps
(II) Jan 08 05:14:38 NVIDIA(0): Initialized X Rendering Acceleration
(==) NVIDIA(0): DPMS enabled
(==) RandR enabled
(II) Initializing extension GLX
(II) XKB: reuse xkmfile
/var/lib/xkb/server-02D8252E59564A234380F1E5417646A9DB3B7452.xkm
(II) config/udev: Adding input device Power Button (/dev/input/event1)
> yes, as last resort - but your GPU can carry some windows before mapping to
> sysram.
> please notice that ARGB enabled windows will take 33% more memory than
> "ordinary" ones. konsole and most plasma-desktop windows use ARGB and we
> recently figured that apparently gdk driven GL clients (like at least eg.
> cairo-dock) will make all Qt clients (or rather everything?) use ARGB
> drawables
also dmesg is showing a few quite specific segfaults with kmail
Jan 7 16:01:05 oliverthered-desktop kernel: [41164.733086] klammail[17781]:
segfault at ffffffffffffffa8 ip 00007f23d4a0635e sp 00007fffd85
079f0 error 4 in libc-2.11.1.so[7f23d49bd000+17a000]
Jan 8 01:26:52 oliverthered-desktop kernel: [75109.879548] klammail[353]:
segfault at ffffffffffffffa8 ip 00007f8cf22c035e sp 00007fff87ebcb90 error 4 in
libc-2.11.1.so[7f8cf2277000+17a000]
I've also got this one for dropbox, but I know that was caused the a file with
the name dropbox in ~ and dropbox wanted to use a directory of that name.
Then after renaming the file dropbox.py (as it as a python script)
dropbox would segfault, until I created the directory. So that ones a dropbox
fault,
Jan 7 06:27:16 oliverthered-desktop kernel: [ 6735.655565] dropbox[5546]:
segfault at 0 ip 00007fb73f35cb94 sp 00007fb73690bdf0 error 4 in
libwx_baseud-2.8.so.0[7fb73f28f000+13a000]
>
> the nvidia driver has however it's very own pitfall.
> call "nvidia-settgins -a PixmapCache=0; nvidia-settgins -a PixmapCache=1"
> from time to time (every 30 minutes and right after your desktop is
> loaded) to improve performance...
>
> sidenote:
> consider to split up the mail, strip it a bit ... more... and resend it
> =P
>
> Cheers,
> Thomas
>
> >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to
> >> unsubscribe <<
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
