From: "Ralf Rösch" <rtlinux@cantastic.org>
To: linux-rt-users@vger.kernel.org
Subject: Memory leak in 3.4.x-rt ?
Date: Fri, 24 Aug 2012 14:38:11 +0200 [thread overview]
Message-ID: <503775B3.4080504@cantastic.org> (raw)
Hi,
we work on our TX4938 (Toshiba Mips, little endian mode) based embedded
system (motion control)
running successfully a 3.2 RT patched kernel for month now.
I just give a try to a 3.4 RT patched kernel and detected a memory
problem as you can see from the logs below:
3.2 with RT FULL PREEMPT is o.k
3.4 without RT FULL PREEMPT is .ok.
3.4 with RT FULL PREEMPT is not o.k.
Can anyone give me hint in which direction I could go to detect the
problem or has anyone else the same problem?
Thanks and regards
Ralf
Linux MCU 3.2.27-rt40-00027-g8fd8396 #36 PREEMPT RT Mon Aug 20 16:21:04
CEST 2012 mips GNU/Linux
[root@MCU:/opt]# watch -n 1 cat /proc/meminfo | grep MemFree
MemFree: 216992 kB
MemFree: 216992 kB
MemFree: 216944 kB
MemFree: 216992 kB
MemFree: 216992 kB
MemFree: 216992 kB
MemFree: 216992 kB
uname -a
Linux MCU 3.4.9-rt17-11244-gb12622a #23 PREEMPT RT Fri Aug 24 12:15:49
CEST 2012 mips GNU/Linux
[root@MCU:/opt]# watch -n 1 cat /proc/meminfo | grep MemFree
MemFree: 204304 kB
MemFree: 204208 kB
MemFree: 204112 kB
MemFree: 204064 kB
MemFree: 203968 kB
MemFree: 203920 kB
MemFree: 203824 kB
MemFree: 203776 kB
uname -a
Linux MCU 3.4.9-rt17-11244-gb12622a #24 PREEMPT Fri Aug 24 14:15:04 CEST
2012 mips GNU/Linux
[root@MCU:/opt]# watch -n 1 cat /proc/meminfo | grep MemFree
MemFree: 222240 kB
MemFree: 222192 kB
MemFree: 222192 kB
MemFree: 222192 kB
MemFree: 222144 kB
MemFree: 222144 kB
MemFree: 222192 kB
MemFree: 222144 kB
MemFree: 222192 kB
MemFree: 222144 kB
next reply other threads:[~2012-08-24 13:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-24 12:38 Ralf Rösch [this message]
2012-09-25 15:39 ` Memory leak in 3.4.x-rt ? Jean-Michel Hautbois
2012-09-25 16:18 ` Carsten Emde
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=503775B3.4080504@cantastic.org \
--to=rtlinux@cantastic.org \
--cc=linux-rt-users@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;
as well as URLs for NNTP newsgroup(s).