From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <49DC6612.40802@domain.hid> Date: Wed, 08 Apr 2009 10:53:38 +0200 From: Jan Kiszka MIME-Version: 1.0 References: <49C91B24.2020304@domain.hid> <49C95A76.4020802@domain.hid> <49D9E000.4070009@domain.hid> <1239099594.9869.65.camel@domain.hid> <49DB3717.4090402@domain.hid> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai-help] Xenomai LTTng support List-Id: Help regarding installation and common use of Xenomai List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: vikesh rambaran Cc: xenomai-help , Vikesh Rambaran vikesh rambaran wrote: > Hi > > On Tue, Apr 7, 2009 at 1:20 PM, Jan Kiszka wrote: > >> Hmm, maybe we have issues with MTRR again. Can you also try X without >> CONFIG_MTRR set in the kernel? > > > Tried the following combinations on intel and amd platforms > > 1. No MTRR on 2.6.28.7 + Xenomai 2.4.7 for Intel core 2 > 2. No MTRR on 2.6.28.7 + Xenomai 2.4.7 + LTTng for Amd Athlon > > Lockup still persists (: OK, something to rule out. So I'm hoping for serial/netconsole dumps now (don't forget to switch off klogd for this, otherwise the information may get lost between crashing ipipe/xenomai and klogd. > > Going to compare the vanilla installation message log with that of the > xenomai patched installation > ("Unable to set hardware clock" is something i don't remember seeing in the > vanilla logs - will check again) The RTC issue is most probably unrelated, should rather have something to do with conflicting old/new RTC config switches (sorry, don't recall details ATM). Jan -- Siemens AG, Corporate Technology, CT SE 2 Corporate Competence Center Embedded Linux