From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Fri, 23 Dec 2011 15:25:30 -0500
Message-ID: <20111223202530.GO27742@domain.hid>
References: <20111223173309.GM27742@domain.hid>
	<4EF4C5A5.6000105@domain.hid>
	<20111223183246.GN27742@domain.hid>
	<4EF4DFAB.9040406@domain.hid>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4EF4DFAB.9040406@domain.hid>
From: lsorense@domain.hid (Lennart Sorensen)
Subject: Re: [Xenomai-core] CONFIG_XENO_HW_UNLOCKED_SWITCH=y causes random
 process corruption in xenomai 2.6.0 on powerpc.
List-Id: Xenomai life and development <xenomai.xenomai.org>
List-Unsubscribe: <https://mail.gna.org/options/xenomai-core>,
	<mailto:xenomai-core-request@domain.hid>
List-Archive: </public/xenomai-core>
List-Post: <mailto:xenomai@xenomai.org>
List-Help: <mailto:xenomai-core-request@domain.hid>
List-Subscribe: <https://mail.gna.org/listinfo/xenomai-core>,
	<mailto:xenomai-core-request@domain.hid>
To: Philippe Gerum <rpm@xenomai.org>
Cc: xenomai@xenomai.org

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.

-- 
Len Sorensen