From: Jim Keniston <jkenisto@us.ibm.com>
To: sourceware-bugzilla@sourceware.org
Cc: systemtap@sources.redhat.com
Subject: Re: [Bug uprobes/7092] New: uprobes probes causing OOM
Date: Wed, 10 Dec 2008 19:53:00 -0000 [thread overview]
Message-ID: <1228938639.4460.4.camel@dyn9047018139.beaverton.ibm.com> (raw)
In-Reply-To: <20081210190833.7092.dsmith@redhat.com>
On Wed, 2008-12-10 at 19:08 +0000, dsmith at redhat dot com wrote:
...
> [1] OOM. When run, the machine gets an OOM in pass 5. The bash prompt is never
> seen. On the console, I see:
>
> agetty invoked oom-killer: gfp_mask=0xd0, order=0, oomkilladj=0
> ...
>
> [2] same as [1]
> [3] works
> [4] works
>
[1], [3], and [4] work for me, but as mentioned in 7082, I'm using odd
bits with at least a partial fix for 7082.
[2] yields a Trace/breakpoint trap, as with 7082, so I'm investigating
both 7082 and 7092 in that light.
next prev parent reply other threads:[~2008-12-10 19:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-10 19:09 dsmith at redhat dot com
2008-12-10 19:53 ` Jim Keniston [this message]
2008-12-10 19:54 ` [Bug uprobes/7092] " jkenisto at us dot ibm dot com
2008-12-11 20:52 ` dsmith at redhat dot com
2008-12-15 19:26 ` dsmith at redhat dot com
2008-12-15 19:40 ` fche at redhat dot com
2009-03-06 17:28 ` fche at redhat dot com
2009-03-09 21:04 ` jkenisto at us dot ibm dot com
2009-03-09 21:06 ` fche at redhat dot com
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=1228938639.4460.4.camel@dyn9047018139.beaverton.ibm.com \
--to=jkenisto@us.ibm.com \
--cc=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sources.redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).