From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Sat, 23 Apr 2011 16:21:09 +0200 From: Richard Cochran Message-ID: <20110423142109.GA332@domain.hid> References: <20110409184122.GA11908@domain.hid> <20110409185503.GB11908@domain.hid> <4DA0B580.4070602@domain.hid> <4DA0B878.9010106@domain.hid> <20110410065250.GA28869@domain.hid> <4DA192E0.2090802@domain.hid> <20110414164248.GA4725@domain.hid> <4DA846FF.5040204@domain.hid> <4DB11857.4030604@domain.hid> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4DB11857.4030604@domain.hid> Subject: Re: [Xenomai-core] arm ixp: more trouble with recent xenomai List-Id: Xenomai life and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gilles Chanteperdrix Cc: xenomai@xenomai.org On Fri, Apr 22, 2011 at 07:55:35AM +0200, Gilles Chanteperdrix wrote: > I also had a look at the culprit patch, reducing it to the bare minimum > (no useless whitespace changes and no function moves), and it boils down > to only two differences: > 1- the fact that we use the "generic" clocksource created by > ipipe_tsc_register, which probably has a shift of 25 or 26 bits instead > of the 20 bits shift of the original clocksource, and returns a 64 bits > value instead of 32 bits. > 2- the fact that the tsc update is done with hardware irqs off in the > original patch. Thanks for looking into this for me. I tried the patch, but the result is the same as before: - Kernel freezes immediately if xenomai is not a module. - If xenomai is a module, the nucleus loads, but the first skin module freezes the machine. I will take a closer look next week to see if I can find out at least where the freeze happens. Thanks, Richard