All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Lennart Sorensen <lsorense@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] CONFIG_XENO_HW_UNLOCKED_SWITCH=y causes random process corruption in xenomai 2.6.0 on powerpc.
Date: Fri, 23 Dec 2011 22:48:29 +0100	[thread overview]
Message-ID: <4EF4F72D.5010007@domain.hid> (raw)
In-Reply-To: <20111223202530.GO27742@domain.hid>

On 12/23/2011 09:25 PM, Lennart Sorensen wrote:
> On Fri, Dec 23, 2011 at 09:08:11PM +0100, Philippe Gerum wrote:
>> Do you have a typical test scenario which triggers this bug?
>
> It can take a couple of hours under pretty heavy load to get one
> occourance.  But with preemptible context swiches off we haven't seen
> any in a week.
>
> For sure xenomai tasks are handling interrupts quite a lot at the time.
>
> I wish we had a simple test case to show it, but it seems to require
> triggering an interrupt in the middle of a context switch at exactly
> the wrong place.
>

Is it reproducible with the basic latency or cyclic tests if waiting for 
long enough? Running ltp in parallel would trigger a decent load, but 
sometimes two shell loops forking commands in the background are enough 
to trigger a variety of issues when something fragile exists in the mmu 
layer as modified by the I-Pipe.

-- 
Philippe.


  reply	other threads:[~2011-12-23 21:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-23 17:33 [Xenomai-core] CONFIG_XENO_HW_UNLOCKED_SWITCH=y causes random process corruption in xenomai 2.6.0 on powerpc Lennart Sorensen
2011-12-23 18:17 ` Philippe Gerum
2011-12-23 18:32   ` Lennart Sorensen
2011-12-23 20:08     ` Philippe Gerum
2011-12-23 20:25       ` Lennart Sorensen
2011-12-23 21:48         ` Philippe Gerum [this message]
2011-12-23 21:55           ` Lennart Sorensen
2011-12-23 21:58             ` Philippe Gerum
2012-01-04 13:34 ` Philippe Gerum
2018-03-21 15:40   ` [Xenomai] " Frank Benkert
2018-03-21 16:40     ` Philippe Gerum
2018-03-22  7:22       ` Frank Benkert

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=4EF4F72D.5010007@domain.hid \
    --to=rpm@xenomai.org \
    --cc=lsorense@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.