From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <4B6C2D59.9060200@domain.hid> Date: Fri, 05 Feb 2010 15:38:17 +0100 From: Jan Kiszka MIME-Version: 1.0 References: <20100204105700.GB20669@domain.hid> <4B6ADA01.2080803@domain.hid> <20100205103744.GA12904@domain.hid> <4B6BFEDC.60403@domain.hid> <4B6C1E66.2000008@domain.hid> In-Reply-To: <4B6C1E66.2000008@domain.hid> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai-help] Force switch back to primary domain List-Id: Help regarding installation and common use of Xenomai List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gilles Chanteperdrix Cc: xenomai@xenomai.org Gilles Chanteperdrix wrote: > Henri Roosen wrote: >> Unfortunately I was not able to capture the problem in a basic >> application :-( and I cannot sent our full application as is. It is >> easy to reproduce with our app. >> >> But... As a quick (quick?!) test I disabled CONFIG_XENO_FASTSYNCH. >> Then I could not reproduce the problem anymore. So it I guess it is >> somewhere in that area... >> >> We use the rt_mutex implementation from the Xenomai native skin from user space. > > Maybe you could tell us on what platform you get the problem, and what > is the problem exactly? Does the mutex-torture-native unit test run fine? > > It is very important for us to fix this ASAP, we can not afford to let > people know the bug exist and do nothing. Full ack from my side. We are running this on big-iron x86-64, so far without problems. If there is an issue, we would be happy to know more about it to start digging after the reason. Jan -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux