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:15:53 -0400 [thread overview]
Message-ID: <20130613201553.GA32137@redhat.com> (raw)
In-Reply-To: <CA+ydwtrxkFecyx5mK_ogvV+MP+iHmTFYySLXRjHOT0cZQmeidw@mail.gmail.com>
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).
> trinity: malloc.c:3616: _int_malloc: Assertion `(unsigned long)(size)
> >= (unsigned long)(nb)' failed.
This is trinity corrupting itself. Seen this occasionally for a while now,
but haven't had time to track it down. Need to spend some time
with scripts/test-all-sequentially.sh to figure out a) which syscall
is causing it, and b) what memory it's scribbling over.
> I collected bunch of cores with -D and see this a lot, related perhaps:
>
> Core was generated by `./trinity -q -l off -C40 -D'.
> Program terminated with signal 11, Segmentation fault.
> #0 mkcall (childno=childno@entry=1) at syscall.c:292
> 292 syscalls_32bit[call32].entry->flags &= ~ACTIVE;
> #0 mkcall (childno=childno@entry=1) at syscall.c:292
> #1 0x0000000000407e8c in do_random_syscalls (childno=childno@entry=1)
> at random-syscalls.c:125
Can you see what syscalls_32bit, and call32 are at that point ?
Also a backtrace might be useful.
Is it always the 32bit path ?
Dave
next prev parent reply other threads:[~2013-06-13 20:15 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 [this message]
2013-06-13 20:33 ` 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=20130613201553.GA32137@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