From mboxrd@z Thu Jan 1 00:00:00 1970 From: "??" Date: Thu, 8 Mar 2012 11:13:16 +0800 Message-ID: <001501ccfcd9$67d9ede0$378dc9a0$@q@domain.hid> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0016_01CCFD1C.75FD2DE0" Content-Language: zh-cn Subject: [Xenomai-help] Xenomai stop working List-Id: Help regarding installation and common use of Xenomai List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: xenomai@xenomai.org This is a multi-part message in MIME format. ------=_NextPart_000_0016_01CCFD1C.75FD2DE0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi I have installed xenomai-2.5.6 on imx53 quick start board with Linux 2.6.35, it works well but stop working when I do some kernel real time task. When it stop working, system is not totally down, it will be recovered after about 8~9 minutes, which comes regularly. Console operation is as normal if no IO task and without increasing of timer interrupt count(cat /proc/interrupt) before xenomai coming back. I have also tested it with Linux 2.6.38 and xenomai-2.6.0, nothing has changed. Maybe there are some bugs in my task code, or some misuse of the skin interface. I need help to get some idea: 1 Is there any situation lead to such case(stalled about 8~9 minutes)? 2 Can ipipe trace and proc information give anything useful, which I have to get deeper into implements. ------=_NextPart_000_0016_01CCFD1C.75FD2DE0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi

  I have = installed xenomai-2.5.6 on imx53 quick start board with Linux 2.6.35, it = works well but stop working when I do some kernel real time = task.

  When it = stop working, system is not totally down, it will be recovered after = about 8~9 minutes, which comes regularly. = Console operation is as normal if no IO task and without increasing of = timer interrupt count(cat /proc/interrupt) before xenomai coming back. I = have also tested it with Linux 2.6.38 and xenomai-2.6.0, nothing has = changed.

  Maybe = there are some bugs in my task code, or some misuse of the skin = interface. I need help to get some idea:

  1 Is there = any situation lead to such case(stalled about 8~9 = minutes)?

  2 Can = ipipe trace and proc information give anything useful, which I have to = get deeper into implements.

 <= /span>

------=_NextPart_000_0016_01CCFD1C.75FD2DE0--