From: Dave Jones <davej@redhat.com>
To: Michael Ellerman <michael@ellerman.id.au>
Cc: trinity@vger.kernel.org
Subject: Re: Fwd: Trinity 1.4 tarball release.
Date: Wed, 21 May 2014 23:50:45 -0400 [thread overview]
Message-ID: <20140522035045.GB21777@redhat.com> (raw)
In-Reply-To: <1400730073.14864.5.camel@concordia>
On Thu, May 22, 2014 at 01:41:13PM +1000, Michael Ellerman wrote:
> [main] Registered 6 fd providers.
> [main] Couldn't find socket cachefile. Regenerating.
> [main] created 375 sockets
> [main] Generating file descriptors
> [main] Added 276 filenames from /dev
> [main] Something went wrong during nftw(/proc). (-1:Value too large for defined data type)
that's curious, but probably not fatal.
> [child6:56655] ipc (117) returned ENOSYS, marking as inactive.
> [child11:56660] BUG!: CHILD (pid:56660) GOT REPARENTED! parent pid:47159. Watchdog pid:47158
This is usually indicative of the main pid segfaulting.
If you run with -D, you'll get coredumps (though also of the child
processes, so there's going to be a lot of them if it runs enough)
You should able to find the one that corresponds to the main pid though,
and get a backtrace.
> I/O possible
Also weird.
I'll dig into it some more tomorrow if you don't beat me to it.
As a last resort, you might be able to bisect between todays changes
(I'd say start at c19c0ef3973bf816025a2aef5ae5dbd00ca5c9eb).
There's only one bad commit in that range, which is
4401f6d0f0bfdeb92595520dc3be23dee32efc77. If the bisect lands on that,
do git show 4401f6d0f0bfdeb92595520dc3be23dee32efc77| patch -p1 on top of it.
Dave
prev parent reply other threads:[~2014-05-22 3:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-12 17:43 Fwd: Trinity 1.4 tarball release Dave Jones
2014-05-13 6:43 ` Michael Ellerman
2014-05-13 14:00 ` Dave Jones
2014-05-14 7:26 ` Michael Ellerman
2014-05-14 13:35 ` Dave Jones
2014-05-22 2:40 ` Michael Ellerman
2014-05-22 3:40 ` Dave Jones
2014-05-22 3:43 ` Michael Ellerman
2014-05-22 3:41 ` Michael Ellerman
2014-05-22 3:50 ` Dave Jones [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=20140522035045.GB21777@redhat.com \
--to=davej@redhat.com \
--cc=michael@ellerman.id.au \
--cc=trinity@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 read-only IMAP folder(s) and NNTP newsgroup(s).