From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <4A02DEB0.70508@domain.hid> Date: Thu, 07 May 2009 15:14:24 +0200 From: Gilles Chanteperdrix MIME-Version: 1.0 References: <1043994168.4085071240493189508.JavaMail.root@domain.hid> <49F06D77.7050103@domain.hid> <1241695394.6157.7.camel@domain.hid> <4A02D4C2.3060009@domain.hid> <4A02D609.2010202@domain.hid> <1241700440.6157.15.camel@domain.hid> <1241701380.26544.724.camel@domain.hid> In-Reply-To: <1241701380.26544.724.camel@domain.hid> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai-help] Problem of freeze List-Id: Help regarding installation and common use of Xenomai List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Philippe Gerum Cc: xenomai-help , Jan Kiszka Philippe Gerum wrote: > On Thu, 2009-05-07 at 14:47 +0200, Raistlin wrote: >> On Thu, 2009-05-07 at 14:37 +0200, Gilles Chanteperdrix wrote: >>>> As usual, please send us /proc/interrupts, /proc/xenomai/irq, your >>>> .config, and the version of the I-pipe patch you use. >>>> >> I will. >> >>>> Run the latency and switchtest tests, and tell us if you have the freeze >>>> with them too. >> It has happened once during a test (latency I think), but I've also been >> (next times, after reboot) able to run both of them without any issue. >> >> Anyway, as soon as I reboot I'll run all the tests again. >> >>> Also, Benoit's problem was not in fact due to xenomai but to gnome power >>> management. >> I see... Well, of course, all is possible... I'm using >> gnome-power-manager too, but while running plain Ubuntu kernel no freeze >> happens, but... I mean... Who knows?!?! > > The point is not about blaming Gnome PM, but we do know for sure that > power management related drivers may have adverse effects on a > Xenomai-patched kernel - see the troubleshooting guide. If your kernel > enable those, and Gnome PM triggers actions on those such as CPU freq > governors, bad things may happen. > > You .config will confirm or not whether this assumption is correct. The problem could also be that gnome-power-management is trying to use services from the kernel which are not available because power management is disabled in kernel configuration. -- Gilles.