From mboxrd@z Thu Jan 1 00:00:00 1970 References: <5601A1A1.2020506@siemens.com> <560263A0.4080208@sigmatek.at> <56026810.8040300@sigmatek.at> <56028093.6050805@siemens.com> From: =?UTF-8?Q?Harald_Fe=c3=9fl?= Message-ID: <56040CB1.1020806@sigmatek.at> Date: Thu, 24 Sep 2015 16:46:09 +0200 MIME-Version: 1.0 In-Reply-To: <56028093.6050805@siemens.com> Content-Type: text/plain; charset="utf-8"; format="flowed" Content-Transfer-Encoding: 8bit Subject: Re: [Xenomai] Fwd: Re: Problem that the Linux scheduler is not called for some ms Reply-To: harald.fessl@sigmatek.at List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: jan.kiszka@siemens.com, xenomai@xenomai.org Hi Jan If I activate ftrace, the kernel is crashing while the system is booting. I can not see at the moment where the problem is. Is a ipipe trace also a option for you to get more informations ? If yes a can trace a good and a bad working cycle. Harald Am 23.09.2015 um 12:36 schrieb Jan Kiszka: > On 2015-09-23 10:51, Harald Feßl wrote: >> Hi >> >> The linux tasks are not blocked (not all). >> I think the problem is , that the linux scheduler function in the kernel >> is not called for some ms. >> I have also traced the calls to the scheduler function >> "static int __sched __schedule(void)" >> and sometimes when the decribed problem occur this function is not >> called while no linux task are running. > If no task is runnable, there is also no reason to invoke schedule. > > Please post a ftrace log of your system, covering both a working and a > non-working cycle, including cobalt* and at least sched and irq events. > > Jan >