From: Dalibor Straka <dast@panelnet.cz>
To: linux-kernel@vger.kernel.org
Subject: Possible bug in ACPI
Date: Tue, 19 Sep 2006 23:47:24 +0200 [thread overview]
Message-ID: <20060919214724.GB2073@panelnet.cz> (raw)
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
next reply other threads:[~2006-09-19 21:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-19 21:47 Dalibor Straka [this message]
2006-09-19 22:03 ` Jiri Slaby
2006-09-19 22:22 ` Dalibor Straka
2006-09-19 23:33 ` Andrew Morton
2006-09-20 7:11 ` Jarek Poplawski
2006-09-20 9:28 ` Tomasz Torcz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060919214724.GB2073@panelnet.cz \
--to=dast@panelnet.cz \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®