linux-kernel - [BUG] 2.6.24.4 kernel warning at kernel/lockdep.c:2662 check

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Mon, 31 Mar 2008 23:13:39 +0530
From:	Kamalesh Babulal <kamalesh@...ux.vnet.ibm.com>
To:	kernel list <linux-kernel@...r.kernel.org>
CC:	Ingo Molnar <mingo@...e.hu>, stable@...nel.org, greg@...ah.com,
	Andy Whitcroft <apw@...dowen.org>,
	Balbir Singh <balbir@...ux.vnet.ibm.com>
Subject: [BUG] 2.6.24.4 kernel warning at kernel/lockdep.c:2662 check_flags()

Hi,

Kernel warning is seen while booting up 2.6.24.4 kernel on x86_64 box
with the CONFIG_DEBUG_LOCKDEP enabled.

WARNING: at kernel/lockdep.c:2662 check_flags()
Pid: 0, comm: swapper Not tainted 2.6.24.4 #1

Call Trace:
 [<ffffffff8025b02a>] check_flags+0xc6/0x19e
 [<ffffffff8025eb82>] lock_acquire+0x53/0xb2
 [<ffffffff804b51ac>] __atomic_notifier_call_chain+0x50/0xaf
 [<ffffffff8020af14>] mwait_idle+0x0/0x50
 [<ffffffff804b521a>] atomic_notifier_call_chain+0xf/0x11
 [<ffffffff8020ab7e>] __exit_idle+0x27/0x29
 [<ffffffff8020ae90>] cpu_idle+0xa8/0xe2
 [<ffffffff80220679>] start_secondary+0x3c6/0x3d5

possible reason: unannotated irqs-on.
irq event stamp: 720
hardirqs last  enabled at (719): [<ffffffff804b1f6a>] trace_hardirqs_on_thunk+0x35/0x3a
hardirqs last disabled at (720): [<ffffffff8020ae84>] cpu_idle+0x9c/0xe2
softirqs last  enabled at (718): [<ffffffff80241b40>] __do_softirq+0xd9/0xe2
softirqs last disabled at (713): [<ffffffff8020d49c>] call_softirq+0x1c/0x28

-- 
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/