From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Gleixner Subject: Re: [ANNOUNCE] 3.0.6-rt17 Date: Sat, 8 Oct 2011 00:02:12 +0200 (CEST) Message-ID: References: <4E8F3605.6060104@localhost> <4E8F58ED.9060702@localhost> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: LKML , linux-rt-users To: Fernando Lopez-Lezcano Return-path: Received: from www.linutronix.de ([62.245.132.108]:44586 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753195Ab1JGWCQ (ORCPT ); Fri, 7 Oct 2011 18:02:16 -0400 In-Reply-To: <4E8F58ED.9060702@localhost> Sender: linux-rt-users-owner@vger.kernel.org List-ID: On Fri, 7 Oct 2011, Fernando Lopez-Lezcano wrote: > On 10/07/2011 10:25 AM, Fernando Lopez-Lezcano wrote: > > On 10/06/2011 06:15 PM, Thomas Gleixner wrote: > > > Dear RT Folks, > > > > > > I'm pleased to announce the 3.0.6-rt17 release. > > > > Hi and thanks again. So far this one is not hanging which is very good > > news. But I still see the hrtimer_fixup_activate warnings I reported for > > rt16... > > I tried rt17 on my workstation and it froze after a few minutes (quad core > intel based desktop). Reset button freeze. Then I set up my serial console and > tried it out. I could not get it to freeze permanently but I got _many_ > hrtimer_fixup_activate warnings and while the console is sending those the > gnome interface freezes (this is on fc14). So it is not very usable for > debugging... > > Just tried again after another reboot (@ 115200 baud) and it worked for a > while. Then it started spewing messages again and it is again unusable. I'm > attaching a trace of what was sent to the serial console while the machine > froze temporarily. Does adding nohz=off to the kernel commandline solve it? You probably posted your .config before, but could you please send it again (private mail is fine). Thanks, tglx