From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <53E47549.4010904@xenomai.org> Date: Fri, 08 Aug 2014 08:59:21 +0200 From: Philippe Gerum MIME-Version: 1.0 References: <44BE6908-E639-421F-B556-E7B3871402CF@gmail.com> <67B7E374-C4D2-4F83-BA40-B289B15867B9@tuebingen.mpg.de> <53E3B5E3.3090006@xenomai.org> <53E3CD23.5040909@xenomai.org> <53E3D084.2000506@tuebingen.mpg.de> <53E3D2FF.5000407@xenomai.org> <53E3D50D.7060701@tuebingen.mpg.de> <53E3D712.3070801@xenomai.org> <53E3D9F0.5070906@xenomai.org> In-Reply-To: <53E3D9F0.5070906@xenomai.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai] real-time guarantee issues on xenomai 2.6.2.1 List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gilles Chanteperdrix , Ludovic Righetti , Paul Janzen , xenomai@xenomai.org On 08/07/2014 09:56 PM, Gilles Chanteperdrix wrote: > On 08/07/2014 09:44 PM, Philippe Gerum wrote: >> On 08/07/2014 09:35 PM, Ludovic Righetti wrote: >>> >>>> I suspect you could run any loop, like cat /proc/interrupts, and see the >>>> same issue. Are you running with a frame buffer in the no-x mode? >>>> >>> that's what I thought too, but /proc/interrupts or /proc/xenomai/sched >>> (or others) do not seem to create any issue (below the output for >>> interrupts, watching other /proc/ files give similar results). >>> >>> Let me check about the fb. >>> >> >> Just for kicks, could you try this patch ? it does NOT fix anything, >> only maybe papering over an issue we don't know about yet: > > Note that there has already been a thread about this issue in april. > So it looks like nobody cared. -- Philippe.