From: Dave Jones <davej@redhat.com>
To: CAI Qian <caiqian@redhat.com>
Cc: Christoph Lameter <cl@linux.com>,
David Rientjes <rientjes@google.com>,
linux-mm <linux-mm@kvack.org>,
linux-kernel@vger.kernel.org, Oleg Nesterov <oleg@redhat.com>
Subject: Re: BUG at kmem_cache_alloc
Date: Tue, 26 Mar 2013 15:53:44 -0400 [thread overview]
Message-ID: <20130326195344.GA1578@redhat.com> (raw)
In-Reply-To: <1122269504.6445741.1364290347815.JavaMail.root@redhat.com>
On Tue, Mar 26, 2013 at 05:32:27AM -0400, CAI Qian wrote:
> Still running and will update ASAP. One thing I noticed was that trinity
> threw out this error before the kernel crash.
>
> BUG!:
> CHILD (pid:28825) GOT REPARENTED! parent pid:19380. Watchdog pid:19379
>
> BUG!:
> Last syscalls:
> [0] pid:28515 call:settimeofday callno:10356
> [1] pid:28822 call:setgid callno:322
> [2] pid:28581 call:init_module callno:3622
> [3] pid:28825 call:readlinkat callno:403
> child 28581 exiting
> child 28515 exiting
> ...killed.
When this happens, it usually means that the parent segfaulted.
I've been trying to reproduce a few reports of this for a while
without success. If you get time, running trinity inside gdb should
be enough to get a useful backtrace.
(Or run with -D, and collect coredumps [there will a lot], and match the
core to the pid of the process we're interested in)
Dave
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Dave Jones <davej@redhat.com>
To: CAI Qian <caiqian@redhat.com>
Cc: Christoph Lameter <cl@linux.com>,
David Rientjes <rientjes@google.com>,
linux-mm <linux-mm@kvack.org>,
linux-kernel@vger.kernel.org, Oleg Nesterov <oleg@redhat.com>
Subject: Re: BUG at kmem_cache_alloc
Date: Tue, 26 Mar 2013 15:53:44 -0400 [thread overview]
Message-ID: <20130326195344.GA1578@redhat.com> (raw)
In-Reply-To: <1122269504.6445741.1364290347815.JavaMail.root@redhat.com>
On Tue, Mar 26, 2013 at 05:32:27AM -0400, CAI Qian wrote:
> Still running and will update ASAP. One thing I noticed was that trinity
> threw out this error before the kernel crash.
>
> BUG!:
> CHILD (pid:28825) GOT REPARENTED! parent pid:19380. Watchdog pid:19379
>
> BUG!:
> Last syscalls:
> [0] pid:28515 call:settimeofday callno:10356
> [1] pid:28822 call:setgid callno:322
> [2] pid:28581 call:init_module callno:3622
> [3] pid:28825 call:readlinkat callno:403
> child 28581 exiting
> child 28515 exiting
> ...killed.
When this happens, it usually means that the parent segfaulted.
I've been trying to reproduce a few reports of this for a while
without success. If you get time, running trinity inside gdb should
be enough to get a useful backtrace.
(Or run with -D, and collect coredumps [there will a lot], and match the
core to the pid of the process we're interested in)
Dave
next prev parent reply other threads:[~2013-03-26 19:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1089649229.4894208.1363925156257.JavaMail.root@redhat.com>
2013-03-22 4:18 ` BUG at kmem_cache_alloc CAI Qian
2013-03-22 4:18 ` CAI Qian
2013-03-22 9:35 ` David Rientjes
2013-03-22 9:35 ` David Rientjes
2013-03-25 5:37 ` CAI Qian
2013-03-25 5:37 ` CAI Qian
2013-03-25 7:42 ` CAI Qian
2013-03-25 7:42 ` CAI Qian
2013-03-25 18:00 ` Christoph Lameter
2013-03-25 18:00 ` Christoph Lameter
2013-03-26 9:32 ` CAI Qian
2013-03-26 9:32 ` CAI Qian
2013-03-26 19:53 ` Dave Jones [this message]
2013-03-26 19:53 ` Dave Jones
2013-03-28 7:49 ` CAI Qian
2013-03-28 7:49 ` CAI Qian
2013-03-28 14:27 ` Dave Jones
2013-03-28 14:27 ` Dave Jones
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=20130326195344.GA1578@redhat.com \
--to=davej@redhat.com \
--cc=caiqian@redhat.com \
--cc=cl@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=oleg@redhat.com \
--cc=rientjes@google.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 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.