From: Jan Kiszka <jan.kiszka@domain.hid>
To: Sebastian Smolorz <ssm@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Interrupt shield
Date: Thu, 16 Nov 2006 16:50:31 +0100 [thread overview]
Message-ID: <455C88C7.6080509@domain.hid> (raw)
In-Reply-To: <E1Gke0B-0003BT-CA@mailer.emlix.com>
[-- Attachment #1: Type: text/plain, Size: 933 bytes --]
Sebastian Smolorz wrote:
> Hello,
>
> can anybody confirm this behaviour? If I configure the I-shield into the
> kernel and start the latency test the RT tasks have not activated T_SHIELD
> although the documentation states it (and btw in rt_task_create this bit is
> set). If I try to set T_SHIELD inside the display task, the system hangs, a
> soft lockup appears and sometimes a few correct lines of the display task are
> printed, followed by the next lockup.
>
> Explainable?
>
> I'm testing on ARM with my S3C24xx I-pipe patch.
Have you tried over x86, too? The shield used to be off by default for
quite some time, and it's a fairly special feature. I wouldn't be
surprised if there is some regression sleeping. But it might also be an
ARM-specific issue.
Soft lockup sounds like the shield is not released appropriately again.
The tracer would visualise this nicely in verbose mode...
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
next prev parent reply other threads:[~2006-11-16 15:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-16 9:57 [Xenomai-help] Interrupt shield Sebastian Smolorz
2006-11-16 15:50 ` Jan Kiszka [this message]
2006-11-16 16:03 ` Sebastian Smolorz
2006-11-16 21:32 ` Philippe Gerum
2006-11-17 11:21 ` Philippe Gerum
2006-11-20 9:24 ` Sebastian Smolorz
-- strict thread matches above, loose matches on Subject: below --
2005-12-15 8:02 [Xenomai-help] Interrupt Shield smannori
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=455C88C7.6080509@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=ssm@domain.hid \
--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.