From: amit@amit-agarwal.co.in (Amit Agarwal)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Memory allocation problems on RHEL 6.3 kernel version 2.6.32-279.el6.x86_64
Date: Mon, 14 Jul 2014 12:34:50 +0530 [thread overview]
Message-ID: <53C38112.9000109@amit-agarwal.co.in> (raw)
In-Reply-To: <1dde84a7.f6ae.14733a2d968.Coremail.shhuiw@163.com>
On 14-07-2014 12:20, shhuiw wrote:
> Will you please show us your application code, if possible? Or at
> least the mmap part.
The application code is proprietary, so I cannot disclose that.
For the mmap part, we are not doing mmap explicitly in our code, rather
the binary is linked to some dynamic library (here in the strace that I
took, it was oracle client). Application crashes while doing mmap for
the oracle library, here is the trace:
----- Call Stack Trace -----
calling call entry argument values in hex
location type point (? means dubious value)
-------------------- -------- --------------------
----------------------------
mmap(offset=33230848, len=2068480) failed with errno=12 for the file
./libclntsh.so.11.1
mmap(offset=33230848, len=2068480) failed with errno=12 for the file
./libclntsh.so.11.1
kpedbg_dmp_stack()+ call 556FC244 FFE3D814 ? 0 ?
219
kpeDbgCrash()+72 call 556F06E4 0 ? 5 ? FFE3D8E4 ?
A42C90 ?
4 ? FFE3D890 ?
56AA4FDF call 55701184 0 ? 5 ? 56E2AEFC ? 2
? 4 ?
50 ? 4 ? FFE3E8FD ?
56785C74 call 00000000 FFE3D8F4 ? 56F27E60 ?
<stripped> signal 00000000 B ? FFE3EDAC ? FFE3EE2C ?
PKc()+255
<stripped> call _ZN11CThreadDataC1E FFE3F2C8 ? FFE3F32E ? 13 ?
<stripped> PKc() 5720C14A ? 57144297 ? 0 ?
)+127
start_thread()+201 call 00000000 92ECDD8 ? FFE3FB70 ?
FFE3FB70 ? FFE3FB70 ?
clone()+94 call 00000000 FFE3FB70 ? 0 ? 0 ? 0
? 0 ?
0 ?
We have tried by reducing the footprint for our application by
decreasing the application caching of some data and see that the
application can come up properly until the VIRT in top command output is
about 2.8GB after which application starts crashing.
> So that we can figure out the testcase to reproduce on our boxes.
--
Thanks,
-aka
http://blog.amit-agarwal.co.in
next prev parent reply other threads:[~2014-07-14 7:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-09 12:23 Memory allocation problems on RHEL 6.3 kernel version 2.6.32-279.el6.x86_64 Amit Agarwal
2014-07-10 5:03 ` Greg KH
2014-07-11 4:38 ` Amit Agarwal
2014-07-10 5:42 ` shhuiw
2014-07-11 8:01 ` Amit Agarwal
2014-07-14 6:50 ` shhuiw
2014-07-14 7:04 ` Amit Agarwal [this message]
2014-07-14 9:40 ` shhuiw
2014-07-14 12:16 ` Amit Agarwal
2014-07-10 6:08 ` Rik van Riel
2014-07-10 7:06 ` shhuiw
2014-07-11 4:52 ` Amit Agarwal
2014-07-11 5:42 ` shhuiw
2014-07-11 5:46 ` Amit Agarwal
2014-07-11 6:59 ` Dave Tian
2014-07-11 12:02 ` Amit Agarwal
2014-07-11 4:50 ` Amit Agarwal
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=53C38112.9000109@amit-agarwal.co.in \
--to=amit@amit-agarwal.co.in \
--cc=kernelnewbies@lists.kernelnewbies.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.