From mboxrd@z Thu Jan 1 00:00:00 1970 From: Philippe Gerum In-Reply-To: <1254853590.3718.28.camel@domain.hid> References: <4AC2448B.1080500@domain.hid> <1254396765.2703.234.camel@domain.hid> <4AC62883.1080908@domain.hid> <1254505304.2703.347.camel@domain.hid> <1254506494.8199.46.camel@domain.hid> <1254510029.2703.355.camel@domain.hid> <1254853590.3718.28.camel@domain.hid> Content-Type: text/plain Date: Tue, 06 Oct 2009 21:55:05 +0200 Message-Id: <1254858905.2784.250.camel@domain.hid> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai-core] RFC: 2.5 todo list. List-Id: Xenomai life and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Andreas Glatz Cc: Xenomai core On Tue, 2009-10-06 at 14:26 -0400, Andreas Glatz wrote: > On Fri, 2009-10-02 at 21:00 +0200, Philippe Gerum wrote: > > On Fri, 2009-10-02 at 14:01 -0400, Andreas Glatz wrote: > > > > > > > > - powerpc32 updates for 2.6.30. Mainly to merge the once experimental > > > > bits that prevent most alignment faults from triggering a secondary mode > > > > switch. Andreas told me this works like a charm on 83xx, and I did not > > > > see any issue on 52xx, 85xx or 86xx either. > > > > > > > > > > Can I get a version of that patch for testing? Is it in your git > > > repository? > > > > I just pushed this commit to my remote tree (ipipe-2.6.30-powerpc > > branch); it should appear in a few hours once mirrored (cron job). > > > > I finally had a chance to test the ipipe-2.6.30-powerpc version > from the git repository. Unfortunately, I noticed that our application > dies after some time and that this behaviour is related to that > alignment patch (if I take it out everything runs fine for > 2 days). > > Currently I'm investigating the reasons for that crash. It has > something to do with floating point registers not being restored > properly. Our alignment exceptions are mainly triggered by accesses > to unaligned floating point data. > Just to check some assumption of mine, could you try running with CONFIG_PREEMPT off (+patch) if this is not the case yet? TIA, > Andreas -- Philippe.