From: Carsten Emde <C.Emde@osadl.org>
To: Jean-Michel Hautbois <jhautbois@gmail.com>
Cc: "Ralf Rösch" <rtlinux@cantastic.org>, linux-rt-users@vger.kernel.org
Subject: Re: Memory leak in 3.4.x-rt ?
Date: Tue, 25 Sep 2012 18:18:31 +0200 [thread overview]
Message-ID: <5061D957.4060305@osadl.org> (raw)
In-Reply-To: <CAL8zT=j5qF=b3bsehLZtV3X7F71LR+aX6L0zGKJqHZd=avkSug@mail.gmail.com>
On 09/25/2012 05:39 PM, Jean-Michel Hautbois wrote:
> 2012/8/24 Ralf Rösch<rtlinux@cantastic.org>:
>> 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.
>> [..]
>> 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
>[..]
> You have a big leak (around 100kB/sec), yes, but can you give us more details ?
> What kind of application ? Network ? video encoder ?
> Which drivers are you using ?
> Did you try using some advanced tools in order to check that your
> application cannot have a memory leak in a specific use case (race
> condition ?) ?
> You will need to be more precise on the memory leak detection, because
> with what you gave, I (maybe others can) cannot help you more...
In a first step, I would propose to run "cat /proc/meminfo" repeatedly
and no longer only check MemFree but check all other variables. One of
them will increase in the same amount as MemFree decreases. Which one is
it? Slab? This information will then lead us where to search further.
-Carsten.
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2012-09-25 16:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-24 12:38 Memory leak in 3.4.x-rt ? Ralf Rösch
2012-09-25 15:39 ` Jean-Michel Hautbois
2012-09-25 16:18 ` Carsten Emde [this message]
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=5061D957.4060305@osadl.org \
--to=c.emde@osadl.org \
--cc=jhautbois@gmail.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=rtlinux@cantastic.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).