From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <4D6CE2E8.2070706@domain.hid> Date: Tue, 01 Mar 2011 13:13:28 +0100 From: Gilles Chanteperdrix MIME-Version: 1.0 References: <4D6B9032.5060907@domain.hid> <4D6B92C8.3070505@domain.hid> <4D6B97E5.5030901@domain.hid> <4D6BA899.90600@domain.hid> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai-help] More blackfin kernel oops under heavy load List-Id: Help regarding installation and common use of Xenomai List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: xenoka09@domain.hid Cc: xenomai@xenomai.org Kolja Waschk wrote: >> I do not really understand what we are talking about. Are we talking >> about Linux select/accept or Xenomai select/accept? Why not using the > > Linux select/accept. Using the blocking accept() would have changed the > behaviour somewhat compared to the original design. Anyway, I think that doesn't > actually matter much. > > I have meanwhile derived a much smaller RTDM driver kernel module, test > application with blocking accept() ;) plus Makefile that do not depend on any > particular external hardware anymore: A SPORT interface (SPORT1 receiver) is > configured with internal clock and frame sync generation and so on itself > generates a lot of interrupts, and this alltogether quite quickly reproduces > the problem on my system. The files together are less than 1000 lines, 20kb. > > I'd really appreciate if you or someone could take a look at it and maybe try > the code on his own bf537 system whether the same faults occur, and why. May I > post the files here (as a zipped attachment? inline)? I've already uploaded > a copy at > >> http://www.ixo.de/tmp/till20110228.tgz Thanks a lot. I do not know much about blackfin, Philippe is the specialist. But having this code will certainly help find the issue. Regards. -- Gilles.