Hello,
I am often running out of memory. It looks like an ACPI code is guilty:
dast@lili:~$ grep -i acpi /proc/slabinfo
Acpi-Operand 3076 3127 64 59 1 : tunables 120 60 8 : slabdata 53 53 0
Acpi-ParseExt 16 59 64 59 1 : tunables 120 60 8 : slabdata 1 1 0
Acpi-Parse 76 92 40 92 1 : tunables 120 60 8 : slabdata 1 1 0
Acpi-State 1644960 1644960 80 48 1 : tunables 120 60 8 : slabdata 34270 34270 0
Acpi-Namespace 1177 1232 32 112 1 : tunables 120 60 8 : slabdata 11 11 0
dast@lili:~$ free
Mem: 899280 892472 6808 0 82212 77936
-/+ buffers/cache: 732324 166956
Swap: 2634620 243052 2404568
dast@lili:~$ uname -a
Linux lili 2.6.18-rc7 #1 SMP Sun Sep 17 15:01:00 CEST 2006 x86_64
Actualy the Acpi-State's memory is increasing slowly in minutes:
Acpi-State 16176 16176 80 48 1 : tunables 120 60 8 : slabdata 337 337 0
Acpi-State 18816 18816 80 48 1 : tunables 120 60 8 : slabdata 392 392 0
Acpi-State 19200 19200 80 48 1 : tunables 120 60 8 : slabdata 400 400 0
Acpi-State 20160 20160 80 48 1 : tunables 120 60 8 : slabdata 420 420 0
I am not familiar with kernel sources, but i can do c pretty well.
BTW: Bios says i have 1024MB, but kernel sees 899MB :-?. The system is
pure HP nx6325. It happens with all the recent kernels .18-rc* .17.* and
debian's distribution 2.6.17-1-amd64-k8-smp.
Please Cc: to me, I read lkml only when I have a good mood.
-- Dalibor Straka
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
