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>
Subject: Re: [Announce] 2.6.29-rc6-rt3 (was 2.6.29-rc6-rt2)
Date: Wed, 25 Feb 2009 12:52:40 -0800 [thread overview]
Message-ID: <1235595160.9252.49.camel@localhost.localdomain> (raw)
In-Reply-To: <1235513895.3816.11.camel@localhost.localdomain>
On Tue, 2009-02-24 at 14:18 -0800, Fernando Lopez-Lezcano wrote:
> 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!
I see this when going through a suspend/wakeup cycle on my laptop (but
no side effects I can see):
BUG: sleeping function called from invalid context at
kernel/rtmutex.c:683
in_atomic(): 0, irqs_disabled(): 1, pid: 8829, name: pm-suspend
Pid: 8829, comm: pm-suspend Not tainted
2.6.29-0.1.rt3.1.rc6.fc9.ccrma.i686.rtPAE #1
Call Trace:
[<c06e62cf>] ? rt_spin_lock_slowlock+0x0/0x1db
[<c043216b>] __might_sleep+0xec/0xf1
[<c045716e>] rt_spin_lock_fastlock+0x27/0x5e
[<c06e6b2e>] rt_spin_lock+0xd/0xf
[<c040dc4e>] read_persistent_clock+0xe/0x25
[<c045057c>] timekeeping_suspend+0x9/0x94
[<c05c13fd>] sysdev_suspend+0x67/0x175
[<c045c508>] suspend_devices_and_enter+0xea/0x179
[<c045c6ec>] enter_state+0x130/0x190
[<c045c7e0>] state_store+0x94/0xa8
[<c045c74c>] ? state_store+0x0/0xa8
[<c053b9d5>] kobj_attr_store+0x1a/0x22
[<c04e8091>] sysfs_write_file+0xb7/0xe2
[<c04e7fda>] ? sysfs_write_file+0x0/0xe2
[<c04ab325>] vfs_write+0x84/0xdf
[<c04ab419>] sys_write+0x3b/0x60
[<c0408bab>] sysenter_do_call+0x12/0x2c
-- Fernando
next prev parent reply other threads:[~2009-02-25 20:52 UTC|newest]
Thread overview: 24+ 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
2009-02-25 20:52 ` Fernando Lopez-Lezcano [this message]
2009-02-26 3:45 ` [Announce] 2.6.29-rc6-rt3 (was 2.6.29-rc6-rt2) 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
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=1235595160.9252.49.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.