All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
To: kernel list <linux-kernel@vger.kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>,
	stable@kernel.org, greg@kroah.com,
	Andy Whitcroft <apw@shadowen.org>,
	Balbir Singh <balbir@linux.vnet.ibm.com>
Subject: [BUG] 2.6.24.4 kernel warning at kernel/lockdep.c:2662 check_flags()
Date: Mon, 31 Mar 2008 23:13:39 +0530	[thread overview]
Message-ID: <47F122CB.4000702@linux.vnet.ibm.com> (raw)

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.

                 reply	other threads:[~2008-03-31 17:43 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=47F122CB.4000702@linux.vnet.ibm.com \
    --to=kamalesh@linux.vnet.ibm.com \
    --cc=apw@shadowen.org \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=stable@kernel.org \
    /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.