From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Tue, 20 May 2014 14:27:29 +0200 From: =?utf-8?q?Petr_Cervenka?= References: <20140502141307.B6A14EC0@centrum.cz>, <53639AC8.1000507@xenomai.org>, <20140506101735.3A0BEBEB@centrum.cz>, <5368A3A2.1010302@xenomai.org>, <20140506112918.F5E14FAA@centrum.cz>, <5368DC2C.5000505@xenomai.org>, <20140507151310.0F980ADD@centrum.cz>, <536BA891.3060605@xenomai.org>, <20140512143736.8105A76F@centrum.cz> <5370C807.7050809@xenomai.org> In-Reply-To: <5370C807.7050809@xenomai.org> MIME-Version: 1.0 Message-Id: <20140520142729.DABA4B8B@centrum.cz> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Subject: Re: [Xenomai] =?utf-8?q?non-blocking_rt=5Ftask=5Fsuspend=28NULL=29?= List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: =?utf-8?q?Philippe_Gerum?= Cc: Xenomai > Od: Philippe Gerum > >>> >>> Thanks. Could you drop the previous instrumentation patches, and give a try at this one? It fixes a flaw in the logic for maintaining the thread information bits, which may have caused the issue you observed: >>> >>> diff --git a/ksrc/nucleus/pod.c b/ksrc/nucleus/pod.c >>> index 0a2ee19..22fa91d 100644 >>> --- a/ksrc/nucleus/pod.c >>> +++ b/ksrc/nucleus/pod.c >>> @@ -1391,7 +1391,8 @@ void xnpod_suspend_thread(xnthread_t *thread, xnflags_t mask, >>> } >>> #endif /* CONFIG_XENO_OPT_PERVASIVE */ >>> >>> - xnthread_clear_info(thread, XNRMID | XNTIMEO | XNBREAK | XNWAKEN | XNROBBED); >>> + xnthread_clear_info(thread, XNRMID | XNTIMEO | XNBREAK | \ >>> + XNWAKEN | XNROBBED | XNKICKED); >>> } >>> >>> /* Don't start the timer for a thread indefinitely delayed by >>> >> >> I applied the new patch and I was not able to reproduce the -EINTR problem to this moment. But one of the machines I tried during long term test over the weekend got frozen. But it could be also from different reason. What do you think? > >Could you enable all debug features (CONFIG_XENO_OPT_DEBUG), and >particularly CONFIG_XENO_OPT_WATCHDOG? The system will be significantly >slowed down due to the consistency checks on all internal lists (i.e. >DEBUG_QUEUES), but this may give us some hints about the freeze. > I have enabled almost all debug features and tortured several PCs for a week without a single problem. Thank you all for your help. Petr