From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <49E4750B.6060602@domain.hid> Date: Tue, 14 Apr 2009 13:35:39 +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> <49DC6612.40802@domain.hid> <1239696760.5780.12.camel@domain.hid> <49E45473.4050409@domain.hid> <1239708396.5780.34.camel@domain.hid> In-Reply-To: <1239708396.5780.34.camel@domain.hid> Content-Type: text/plain; charset=ISO-8859-15 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 wrote: > On Tue, 2009-04-14 at 11:16 +0200, Jan Kiszka wrote: >> Vikesh Rambaran wrote: >>> Hi >>> Hope everybody had a good Easter weekend :) >> Yeah, sunny and relaxing, just a little bit hacking. 8) >> > > Great, R&R always helps ! > >> NMI watchdog, see Xenomai machine kconfig menu, use nmi_watchdog=2 to >> finally enable it at the kernel command line. >> > > There are build issues with NMI enabled. > > Would you prefer testing with the latest git updates, or can i just > replace the following in hal32.c (line 139) > > - die_nmi(regs, buf); > + die_nmi(buf, regs, 1); If your CPU is not too new, this may suffice. Otherwise you should switch over to the development head (upcoming 2.5) as there we have up-to-date NMI support. BTW, trying 2.5-devel might be useful anyway to check if the picture changes (maybe we even see a clearer error with that branch...). Jan -- Siemens AG, Corporate Technology, CT SE 2 Corporate Competence Center Embedded Linux