From: Dmitriy Cherkasov <dmitriy@mperpetuo.com>
To: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: [Xenomai] Soft lockup on arm64
Date: Tue, 2 Feb 2016 14:44:32 -0800 [thread overview]
Message-ID: <56B13150.2090606@mperpetuo.com> (raw)
Hello.
We are seeing a possible SMP bug on arm64. When running the attached test
program on the 410c board, the following message appears, usually followed
by a complete lockup:
Message from syslogd@linaro-developer at Jul 3 18:51:00 ...
kernel:[ 284.102490] NMI watchdog: BUG: soft lockup - CPU#2 stuck for
23s! [xeno_sleep:962]
An important observation is when I set the affinity for the realtime thread
to a specific core, the problem goes away. I suspect there is an issue with
CPU migration that triggers most often when sleeping for a short interval.
I have not tested this on any other platform, so I am not sure if this is
arm64 specific. Any help would be greatly appreciated.
Test setup:
410c/Debian with Jorge's latest ipipe and xenomai trees.
Thanks,
Dmitriy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: xeno_sleep.c
Type: text/x-csrc
Size: 1294 bytes
Desc: not available
URL: <http://xenomai.org/pipermail/xenomai/attachments/20160202/9960c0e1/attachment.c>
reply other threads:[~2016-02-02 22:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=56B13150.2090606@mperpetuo.com \
--to=dmitriy@mperpetuo.com \
--cc=xenomai@xenomai.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 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.