WARNING: at kernel/lockdep.c:2662 check_flags

From: Zdenek Kabelac
Date: Fri Mar 14 2008 - 19:52:24 EST


Hi

I'm getting this warning trace with current kernel git tree:

[ 0.003346] ------------[ cut here ]------------
[ 0.003346] WARNING: at kernel/lockdep.c:2662 check_flags+0x18d/0x1a0()
[ 0.003346] Modules linked in:
[ 0.003346] Pid: 0, comm: swapper Not tainted 2.6.25-rc5-replic-server #55
[ 0.003346]
[ 0.003346] Call Trace:
[ 0.003346] [<ffffffff8103c0ef>] warn_on_slowpath+0x5f/0x90
[ 0.003346] [<ffffffff81013858>] ? native_sched_clock+0x78/0x80
[ 0.003346] [<ffffffff81063edd>] ? __lock_acquire+0x35d/0x1160
[ 0.003346] [<ffffffff8103599a>] ? hrtick_set+0x7a/0x130
[ 0.003346] [<ffffffff812f5a65>] ? _spin_unlock_irqrestore+0x65/0x90
[ 0.003346] [<ffffffff812f5a45>] ? _spin_unlock_irqrestore+0x45/0x90
[ 0.003346] [<ffffffff8106157a>] ? get_lock_stats+0x2a/0x70
[ 0.003346] [<ffffffff812f9590>] ? __atomic_notifier_call_chain+0x0/0xd0
[ 0.003346] [<ffffffff81060add>] check_flags+0x18d/0x1a0
[ 0.003346] [<ffffffff81064d3d>] lock_acquire+0x5d/0xe0
[ 0.003346] [<ffffffff812f95eb>] __atomic_notifier_call_chain+0x5b/0xd0
[ 0.003346] [<ffffffff8100a140>] ? mwait_idle+0x0/0x60
[ 0.003346] [<ffffffff8100b520>] ? default_idle+0x0/0x80
[ 0.003346] [<ffffffff812f9671>] atomic_notifier_call_chain+0x11/0x20
[ 0.003346] [<ffffffff8100b4b3>] cpu_idle+0xe3/0x150
[ 0.003346] [<ffffffff812ef0a5>] start_secondary+0x407/0x462
[ 0.003346]
[ 0.003346] ---[ end trace ca143223eefdc828 ]---
[ 0.003346] possible reason: unannotated irqs-on.
[ 0.003346] irq event stamp: 18
[ 0.003346] hardirqs last enabled at (17): [<ffffffff8105f4e5>]
tick_nohz_stop_sched_tick+0xe5/0x390
[ 0.003346] hardirqs last disabled at (18): [<ffffffff8100b435>]
cpu_idle+0x65/0x150
[ 0.003346] softirqs last enabled at (0): [<ffffffff8103a29e>]
copy_process+0x41e/0x17a0
[ 0.003346] softirqs last disabled at (0): [<0000000000000000>] 0x0


Zdenek
--
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/