From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <4C2A7586.5070107@domain.hid> Date: Wed, 30 Jun 2010 00:36:54 +0200 From: Gilles Chanteperdrix MIME-Version: 1.0 References: <8EA2C2C4116BF44AB370468FBF85A777016574B413@domain.hid> <4C2A078E.80009@domain.hid> <8EA2C2C4116BF44AB370468FBF85A7770165815E06@domain.hid> <4C2A74C0.2000909@domain.hid> In-Reply-To: <4C2A74C0.2000909@domain.hid> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai-help] machine hangs running oprofile on xenomai kernel List-Id: Help regarding installation and common use of Xenomai List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka Cc: "xenomai@xenomai.org" Jan Kiszka wrote: > [please do not top-post] > > Sydir, Jerry wrote: >> Hi Jan, >> >> Thanks for your reply. I tried loading the oprofile module with timer=1 and oprofile seems to work (doesn't hang the system and spits out some results). So it appears that the use of NMIs are the problem. Do you have any suggestions on what to try next? > > Now someone would have to dig into the code path taken by oprofile > during NMI handling to find the reason for the lock-up. Did you have any > real-time jobs running when starting the profiling, or was Xenomai idle? > > On the other hand, oprofile is a legacy interface. It probably makes > more sense to try and, if required, fix perf instead. Could not there be some bad interaction with Xenomai NMI watchdog? -- Gilles.