Re: [Announce] 2.6.29-rc6-rt3 (was 2.6.29-rc6-rt2)

[Fernando Lopez-Lezcano]

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


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/