All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@elte.hu>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Fernando Pablo Lopez-Lezcano <nando@ccrma.Stanford.EDU>
Subject: Re: [Announce] 2.6.29-rc6-rt2
Date: Tue, 24 Feb 2009 14:18:15 -0800	[thread overview]
Message-ID: <1235513895.3816.11.camel@localhost.localdomain> (raw)
In-Reply-To: <alpine.LFD.2.00.0902241729590.3523@localhost.localdomain>

On Tue, 2009-02-24 at 17:30 +0100, Thomas Gleixner wrote:
> On Tue, 24 Feb 2009, Thomas Gleixner wrote:
> > >  [<c0440ef1>] internal_add_timer+0x88/0x8c
> > 
> > Can you try to enable the following config options:
> > 
> > CONFIG_DEBUG_OBJECTS
> > CONFIG_DEBUG_OBJECTS_FREE
> > CONFIG_DEBUG_OBJECTS_TIMERS
> > CONFIG_DEBUG_OBJECTS_ENABLE_DEFAULT
> 
> Don't bother. Just noticed that this is nf_conntrack context. Working
> on that right now.

I'm running rc6-rt3 and that problem seem to be gone (uptime of 2.5
hours in my desktop, 1.33 hours on my laptop, both running FC9 with a
2.6.29 version of the Planet CCRMA rt kernel). So far so good!

Thanks!!
-- Fernando



  reply	other threads:[~2009-02-24 22:18 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-24  0:57 [Announce] 2.6.29-rc6-rt2 Fernando Lopez-Lezcano
2009-02-24 10:29 ` Thomas Gleixner
2009-02-24 16:30   ` Thomas Gleixner
2009-02-24 22:18     ` Fernando Lopez-Lezcano [this message]
2009-02-25 20:52       ` [Announce] 2.6.29-rc6-rt3 (was 2.6.29-rc6-rt2) Fernando Lopez-Lezcano
2009-02-26  3:45         ` Fernando Lopez-Lezcano
2009-03-13 22:53           ` [Announce] 2.6.29-rc7-rt1 Fernando Lopez-Lezcano
2009-03-14  7:46             ` Thomas Gleixner
2009-03-21 18:44               ` [Announce] 2.6.29-rc8-rt2 Fernando Lopez-Lezcano
2009-03-21 18:49                 ` Ingo Molnar
2009-03-21 19:06                   ` Fernando Lopez-Lezcano
2009-03-21 19:27                     ` Fernando Lopez-Lezcano
2009-03-22  2:07                       ` Fernando Lopez-Lezcano
2009-03-22 13:09                         ` Ingo Molnar
2009-03-22 21:43                           ` Fernando Lopez-Lezcano
2009-03-23  8:07                             ` Ingo Molnar
2009-03-24  3:13                               ` Fernando Lopez-Lezcano
2009-03-24  8:11                                 ` Thomas Gleixner
2009-03-24  8:12                                   ` Thomas Gleixner
2009-03-25  3:54                                     ` Fernando Lopez-Lezcano
2009-03-25  7:27                                       ` Thomas Gleixner
2009-03-25 12:57                                         ` Ingo Molnar
2009-03-25 18:45                                         ` Fernando Lopez-Lezcano
2009-03-26  3:48                                           ` Fernando Lopez-Lezcano
  -- strict thread matches above, loose matches on Subject: below --
2009-02-11 22:43 [Announce] 2.6.29-rc4-rt1 Thomas Gleixner
2009-02-12 22:56 ` [Announce] 2.6.29-rc4-rt2 Thomas Gleixner
2009-02-23 19:44   ` [Announce] 2.6.29-rc6-rt2 Thomas Gleixner
2009-02-24 17:51     ` Thomas Gleixner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1235513895.3816.11.camel@localhost.localdomain \
    --to=nando@ccrma.stanford.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.