From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <536A1529.8070508@xenomai.org> Date: Wed, 07 May 2014 13:12:41 +0200 From: Gilles Chanteperdrix MIME-Version: 1.0 References: , <533FED48.6000409@xenomai.org>, , <53418206.1040601@xenomai.org> , <53676B5B.3020409@xenomai.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai] problem with Task management services: Synchronous message passing List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: mobin Motallebizadeh , "xenomai@xenomai.org" On 05/07/2014 01:07 PM, mobin Motallebizadeh wrote: > > >> Date: Mon, 5 May 2014 12:43:39 +0200 From: >> gilles.chanteperdrix@xenomai.org To: mobin.seven@live.com; >> xenomai@xenomai.org Subject: Re: [Xenomai] problem with Task >> management services: Synchronous message passing >> >> On 05/05/2014 11:01 AM, mobin Motallebizadeh wrote: >>> >>> >>>> Date: Sun, 6 Apr 2014 18:34:14 +0200 From: >>>> gilles.chanteperdrix@xenomai.org To: mobin.seven@live.com CC: >>>> xenomai@xenomai.org Subject: Re: [Xenomai] problem with Task >>>> management services: Synchronous message passing >>>> >>>> On 04/06/2014 06:19 PM, mobin Motallebizadeh wrote: >>>>> I dont know what to do with kernel console.please explain >>>>> more. I'm running a x86_64 mint Linux pc (core i7) >>>> >>>> Send us to us what the kernel console tell you... we can not >>>> guess what the issue is if you do not send us information about >>>> it. >>>> >>>> Also, the xenomai mailing list is an old fashioned mailing list >>>> where we do not top post. So please, no top posting. >>>> >>>> -- Gilles. >>> >>> The attachment is the log from netconsole.Thanks in advance >> >> The error is on the first line of the logs: >> >> [ 111.023581] Watchdog detected hard LOCKUP on cpu 0 [ >> 128.060170] BUG: soft lockup - CPU#1 stuck for 23s! [satch:2028] >> >> Your program has spinned 23s without relinquishing cpu. >> >> >> -- Gilles. > > I changed the code with bounding tasks running time with TIMEOUT. > this time log says its a bug at task.c . why this is happening? is it > a real bug? Do you have the same bug if you sleep a reasonable time between sending messages instead of sleeping 40 nanoseconds? -- Gilles.