ODD memory usage with KDE4
Hi All! OS: debian lenny (+sid + experimental) DE: KDE4 4.0.80 X: 1:7.3+10 kernel: v2.6.26-rc3-git8 + madwifi 23491 root 20 0 :__510m___ 141m 3320 S6 28.5 12:16.65 Xorg total used free sharedbuffers cached Mem:509624 457480 52144 0 0 147120 -/+ buffers/cache: 310360 199264 Swap: 2097144 2007121896432 01:38:34 up 11:19, 1 user, load average: 0.34, 0.37, 0.53 MemTotal: 509624 kB MemFree: 52040 kB Buffers: 0 kB Cached: 147132 kB SwapCached: 27684 kB Active: 356956 kB Inactive:50132 kB HighTotal: 0 kB HighFree:0 kB LowTotal: 509624 kB LowFree: 52040 kB SwapTotal: 2097144 kB SwapFree: 1896432 kB Dirty: 176 kB Writeback: 0 kB AnonPages: 243304 kB Mapped: 59148 kB Slab:29556 kB SReclaimable:17608 kB SUnreclaim: 11948 kB PageTables: 5340 kB NFS_Unstable:0 kB Bounce: 0 kB WritebackTmp:0 kB CommitLimit: 2351956 kB Committed_AS: 1091924 kB VmallocTotal: 509944 kB VmallocUsed: 4804 kB VmallocChunk: 504308 kB HugePages_Total: 0 HugePages_Free: 0 HugePages_Rsvd: 0 HugePages_Surp: 0 Hugepagesize: 2048 kB Active / Total Objects (% used): 91430 / 127004 (72.0%) Active / Total Slabs (% used) : 4665 / 4665 (100.0%) Active / Total Caches (% used) : 58 / 69 (84.1%) Active / Total Size (% used) : 19633.87K / 28675.89K (68.5%) Minimum / Average / Maximum Object : 0.01K / 0.23K / 16.12K OBJS ACTIVE USE OBJ SIZE SLABS OBJ/SLAB CACHE SIZE NAME 14675 11669 79%0.16K587 25 2348K dentry 14391 7765 53%0.10K369 39 1476K selinux_inode_security 9968 5457 54%0.50K623 16 4984K xfs_inode 9936 5447 54%0.62K828 12 6624K xfs_vnode 9154 8024 87%0.09K199 46 796K vm_area_struct 8245 8245 100%0.05K 97 85 388K sysfs_dir_cache 7332 4663 63%0.29K564 13 2256K radix_tree_node 6912 5505 79%0.02K 27 256 108K kmalloc-16 6580 1946 29%0.14K235 28 940K sigqueue 5008 4088 81%0.25K313 16 1252K kmalloc-256 4800 1532 31%0.06K 75 64 300K buffer_head 4692 4690 99%0.04K 46 102 184K Acpi-Operand 3584 3575 99%0.01K 7 51228K kmalloc-8 3400 3008 88%0.05K 40 85 160K anon_vma 3328 3293 98%0.03K 26 128 104K kmalloc-32 2880 2093 72%0.06K 45 64 180K kmalloc-64 1808 1443 79%0.50K113 16 904K kmalloc-512 1664 1206 72%0.12K 52 32 208K kmalloc-128 924919 99%0.73K 42 22 672K shmem_inode_cache 884851 96%0.61K 68 13 544K proc_inode_cache 850850 100%0.02K 5 17020K Acpi-Namespace 688668 97%2.00K 43 16 1376K kmalloc-2048 630538 85%0.09K 15 4260K kmalloc-96 588565 96%0.14K 21 2884K idr_layer_cache 459349 76%0.08K 9 5136K task_delay_info 378301 79%0.75K 18 21 288K sock_inode_cache 351261 74%0.59K 27 13 216K inode_cache 342252 73%0.88K 19 18 304K UNIX -- Thanks, Oliver -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ODD memory usage with KDE4
On Wed, 2008-05-28 at 01:30 +0200, Oliver Pinter wrote: > > 23491 root 20 0 :__510m___ 141m 3320 S6 28.5 12:16.65 Xorg The X server's virtual size includes device mappings such as video RAM, the MMIO register aperture etc. Which video card and driver are you using, how much video RAM does the card have? Etc. -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ODD memory usage with KDE4
it is after 10+ hours uptime 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc RV350 AP [Radeon9600] [1002:4150] 01:00.1 Display controller [0380]: ATI Technologies Inc RV350 AP [Radeon 9600] (Secondary) [1002:4170] lspci -xxx: 01:00.0 VGA compatible controller: ATI Technologies Inc RV350 AP [Radeon 9600] 00: 02 10 50 41 07 01 b0 02 00 00 00 03 04 40 80 00 10: 08 00 00 e0 01 c0 00 00 00 00 9f fe 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 4b 17 20 7c 30: 00 00 9c fe 58 00 00 00 00 00 00 00 00 01 08 00 40: 00 00 00 00 00 00 00 00 00 00 00 00 4b 17 20 7c 50: 01 00 02 06 00 00 00 00 02 50 30 00 1b 02 00 ff 60: 02 43 00 1f 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 05 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01:00.1 Display controller: ATI Technologies Inc RV350 AP [Radeon 9600] (Secondary) 00: 02 10 70 41 07 00 b0 02 00 00 80 03 04 40 00 00 10: 08 00 00 d0 00 00 9e fe 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 4b 17 21 7c 30: 00 00 00 00 50 00 00 00 00 00 00 00 ff 00 08 00 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 50: 01 00 02 06 00 00 00 00 02 50 30 00 1b 02 00 ff 60: 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Xorg's radeon driver reg00: base=0x ( 0MB), size= 512MB: write-back, count=1 reg01: base=0xfc00 (4032MB), size= 32MB: write-combining, count=1 reg02: base=0xe000 (3584MB), size= 256MB: write-combining, count=2 video ram: 256M agp aperture: 32M -- and it is after 20min: 3902 root 20 0 362m 81m 4920 R5 16.4 1:34.13 Xorg On 5/28/08, Michel Dänzer <[EMAIL PROTECTED]> wrote: > On Wed, 2008-05-28 at 01:30 +0200, Oliver Pinter wrote: >> >> 23491 root 20 0 :__510m___ 141m 3320 S6 28.5 12:16.65 Xorg > > The X server's virtual size includes device mappings such as video RAM, > the MMIO register aperture etc. Which video card and driver are you > using, how much video RAM does the card have? Etc. > > > -- > Earthling Michel Dänzer | http://tungstengraphics.com > Libre software enthusiast | Debian, X and DRI developer > -- Thanks, Oliver -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ODD memory usage with KDE4
and again... top - 17:53:21 up 4:07, 1 user, load average: 1.09, 0.66, 0.57 Tasks: 144 total, 2 running, 142 sleeping, 0 stopped, 0 zombie Cpu0 : 6.0%us, 3.0%sy, 0.0%ni, 91.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st Cpu1 : 2.9%us, 0.0%sy, 0.0%ni, 97.1%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st Mem:509624k total, 504456k used, 5168k free,0k buffers Swap: 2097144k total, 628108k used, 1469036k free,89072k cached Change delay from 1.0 to: PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 4287 oliver20 0 135m 24m 15m S4 4.9 16:33.16 amarokapp 3911 root 20 0 978m 219m 3256 S3 44.1 18:39.75 Xorg <<< 4239 oliver20 0 59220 14m 10m S3 2.8 3:28.39 kwin 4243 oliver20 0 102m 23m 12m S2 4.7 6:29.18 plasma 924 root 15 -5 000 S1 0.0 0:07.91 scsi_eh_1 7118 oliver20 0 152m 56m 23m S1 11.4 0:58.48 konqueror 8061 oliver20 0 2324 1152 880 R1 0.2 0:00.02 top 1 root 20 0 2036 640 616 S0 0.1 0:01.42 init 2 root 15 -5 000 S0 0.0 0:00.00 kthreadd 3 root RT -5 000 S0 0.0 0:00.00 migration/0 4 root 15 -5 000 S0 0.0 0:02.07 ksoftirqd/0 5 root RT -5 000 S0 0.0 0:00.20 watchdog/0 6 root RT -5 000 S0 0.0 0:00.00 migration/1 7 root 15 -5 000 S0 0.0 0:02.40 ksoftirqd/1 8 root RT -5 000 S0 0.0 0:00.05 watchdog/1 9 root 15 -5 000 S0 0.0 0:00.29 events/0 10 root 15 -5 000 S0 0.0 0:00.63 events/1 On 5/28/08, Oliver Pinter <[EMAIL PROTECTED]> wrote: > original non hacked and nor flashed card, > > Priority: optional > Section: x11 > Installed-Size: 1024 > Maintainer: Debian X Strike Force > Architecture: i386 > Version: 1:6.8.0-1 > -- > Thanks, > Oliver > -- Thanks, Oliver -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ODD memory usage with KDE4
On Fri, 2008-05-30 at 11:01 +0200, Oliver Pinter wrote: > I found the ground of the BUG (it think): > > many hundred of this line is in Xorg.log: > > enable montype: 1 No, that's just a harmless driver debugging message. If you really want to get to the bottom of this, first of all you should rule out that it's a client leaking server resources. E.g., if you restart all your clients (or at least the usual suspects such as iceweasel), does the memory usage go back or at least stop growing for a while? If so, it's probably a client issue. Otherwise, you'll have to try and find the leak with specialized tools such as memprof or valgrind. Anything else just isn't very useful. -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ODD memory usage with KDE4
xorg.conf: --8<-- # xorg.conf (xorg X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the xorg.conf manual page. # (Type "man xorg.conf" at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section "Files" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "kbd" Option "CoreKeyboard" Option "XkbRules" "xorg" Option "XkbModel" "pc104" Option "XkbLayout" "hu" Option "XkbOptions""ctrl:swapcaps" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "CorePointer" Option "Device""/dev/input/mice" Option "Protocol" "ImPS/2" Option "Emulate3Buttons" "true" EndSection Section "Device" Identifier "ati_r9600" Driver "ati" BusID "PCI:1:0:0" EndSection Section "Monitor" Identifier "T710B" Option "DPMS" HorizSync 30-71 VertRefresh 50-160 EndSection Section "Screen" Identifier "Default Screen" Device "ati_r9600" Monitor "T710B" DefaultDepth24 SubSection "Display" Modes "1152x864" "1024x768" EndSubSection EndSection Section "ServerLayout" Identifier "Default Layout" Screen "Default Screen" InputDevice "Generic Keyboard" InputDevice "Configured Mouse" EndSection #Section "Extensions" # Option "Composite" "Enable" #EndSection -->8-- -- Thanks, Oliver -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ODD memory usage with KDE4
hmm very interest.. with glxgears i become this warning: [EMAIL PROTECTED]:~$ glxgears *WARN_ONCE* File r300_mem.c function r300_mem_alloc line 225 Ran out of GART memory (for 1048576)! Please consider adjusting GARTSize option. *** 8014 frames in 5.0 seconds = 1602.617 FPS 8525 frames in 5.0 seconds = 1704.836 FPS 8508 frames in 5.0 seconds = 1701.421 FPS On 5/30/08, Michel Dänzer <[EMAIL PROTECTED]> wrote: > On Fri, 2008-05-30 at 11:01 +0200, Oliver Pinter wrote: >> I found the ground of the BUG (it think): >> >> many hundred of this line is in Xorg.log: >> >> enable montype: 1 > > No, that's just a harmless driver debugging message. > > If you really want to get to the bottom of this, first of all you should > rule out that it's a client leaking server resources. E.g., if you > restart all your clients (or at least the usual suspects such as > iceweasel), does the memory usage go back or at least stop growing for a > while? If so, it's probably a client issue. > > Otherwise, you'll have to try and find the leak with specialized tools > such as memprof or valgrind. > > Anything else just isn't very useful. > > > -- > Earthling Michel Dänzer | http://tungstengraphics.com > Libre software enthusiast | Debian, X and DRI developer > -- Thanks, Oliver -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ODD memory usage with KDE4
after googling, found this: Option "GARTSize" "64" the glxgears warning shuted up, but the memorie use bad ... On 6/1/08, Oliver Pinter <[EMAIL PROTECTED]> wrote: > hmm very interest.. > > with glxgears i become this warning: > > [EMAIL PROTECTED]:~$ glxgears > *WARN_ONCE* > File r300_mem.c function r300_mem_alloc line 225 > Ran out of GART memory (for 1048576)! > Please consider adjusting GARTSize option. > *** > 8014 frames in 5.0 seconds = 1602.617 FPS > 8525 frames in 5.0 seconds = 1704.836 FPS > 8508 frames in 5.0 seconds = 1701.421 FPS > > > On 5/30/08, Michel Dänzer <[EMAIL PROTECTED]> wrote: >> On Fri, 2008-05-30 at 11:01 +0200, Oliver Pinter wrote: >>> I found the ground of the BUG (it think): >>> >>> many hundred of this line is in Xorg.log: >>> >>> enable montype: 1 >> >> No, that's just a harmless driver debugging message. >> >> If you really want to get to the bottom of this, first of all you should >> rule out that it's a client leaking server resources. E.g., if you >> restart all your clients (or at least the usual suspects such as >> iceweasel), does the memory usage go back or at least stop growing for a >> while? If so, it's probably a client issue. >> >> Otherwise, you'll have to try and find the leak with specialized tools >> such as memprof or valgrind. >> >> Anything else just isn't very useful. >> >> >> -- >> Earthling Michel Dänzer | http://tungstengraphics.com >> Libre software enthusiast | Debian, X and DRI developer >> > > > -- > Thanks, > Oliver > -- Thanks, Oliver -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
