From: Dave Jones <davej@redhat.com>
To: Tommi Rantala <tt.rantala@gmail.com>
Cc: trinity@vger.kernel.org
Subject: Re: msgrcv (70) returned ENOSYS, marking as inactive.
Date: Thu, 13 Jun 2013 16:33:57 -0400 [thread overview]
Message-ID: <20130613203357.GB32137@redhat.com> (raw)
In-Reply-To: <20130613201553.GA32137@redhat.com>
On Thu, Jun 13, 2013 at 04:15:53PM -0400, Dave Jones wrote:
> On Thu, Jun 13, 2013 at 10:41:30PM +0300, Tommi Rantala wrote:
> > Latest trinity from git is constantly complaining:
>
> weird.
>
> > [32492] Random reseed: 3901037224
> > msgrcv (70) returned ENOSYS, marking as inactive.
> > msgrcv (70) returned ENOSYS, marking as inactive.
> > msgrcv (70) returned ENOSYS, marking as inactive.
> > msgrcv (70) returned ENOSYS, marking as inactive.
> > msgrcv (70) returned ENOSYS, marking as inactive.
> > msgrcv (70) returned ENOSYS, marking as inactive.
> > msgrcv (70) returned ENOSYS, marking as inactive.
> > msgrcv (70) returned ENOSYS, marking as inactive.
> > msgrcv (70) returned ENOSYS, marking as inactive.
> > msgrcv (70) returned ENOSYS, marking as inactive.
> > msgrcv (70) returned ENOSYS, marking as inactive.
> > [watchdog] 200253 iterations. [F:161784 S:38468]
> > msgrcv (70) returned ENOSYS, marking as inactive.
> > msgrcv (70) returned ENOSYS, marking as inactive.
> > msgrcv (70) returned ENOSYS, marking as inactive.
> > msgrcv (70) returned ENOSYS, marking as inactive.
> > msgrcv (70) returned ENOSYS, marking as inactive.
> > msgrcv (70) returned ENOSYS, marking as inactive.
> > msgrcv (70) returned ENOSYS, marking as inactive.
>
> puzzling. this should (obviously) only occur once.
> Maybe it's happening once per thread at the same time,
> so they're all racing. (I should add some locking around
> the modifications of the syscall table I suppose).
Something that's even more puzzling about this..
What are the odds all threads hit that at the same time
(unless you did -C msgrcv, which it doesn't look like you
did from the core dump)
I wonder if I've broken seeding again.
Leave logging enabled, and compare a couple of the child logs,
just to make sure they're doing different syscalls.
Would be surprised though, the only thing remotely relevant
that changed is yesterdays rand32 changes in 7d86b1ca5ddc1ac04468d6ee7a0a74e931b67dae
Dave
prev parent reply other threads:[~2013-06-13 20:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-13 19:41 msgrcv (70) returned ENOSYS, marking as inactive Tommi Rantala
2013-06-13 20:15 ` Dave Jones
2013-06-13 20:33 ` 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=20130613203357.GB32137@redhat.com \
--to=davej@redhat.com \
--cc=trinity@vger.kernel.org \
--cc=tt.rantala@gmail.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