From: Prarit Bhargava <prarit@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: x86@kernel.org
Subject: Lockdep warning with init_espfix_ap()
Date: Thu, 09 Oct 2014 11:35:38 -0400 [thread overview]
Message-ID: <5436AB4A.1080900@redhat.com> (raw)
Non-fatal warning seen with latest kernel tree during kernel boot.
WARNING: CPU: 64 PID: 0 at kernel/locking/lockdep.c:2744
lockdep_trace_alloc+0xdd/0xe0()
DEBUG_LOCKS_WARN_ON(irqs_disabled_flags(flags))
Modules linked in:
CPU: 64 PID: 0 Comm: swapper/64 Not tainted 3.17.0+ #10
Hardware name: Intel Corporation BRICKLAND/BRICKLAND, BIOS
BIVTSDP1.86B.0049.R00.1403081207 03/08/2014
0000000000000000 d27b9ea0e3821f35 ffff88084edc3ce0 ffffffff8171cbd8
ffff88084edc3d28 ffff88084edc3d18 ffffffff8108424d 0000000000000046
0000000000000000 00000000000000d0 0000000000000002 0000000000000000
Call Trace:
[<ffffffff8171cbd8>] dump_stack+0x4d/0x66
[<ffffffff8108424d>] warn_slowpath_common+0x7d/0xa0
[<ffffffff810842cc>] warn_slowpath_fmt+0x5c/0x80
[<ffffffff810e3e2d>] lockdep_trace_alloc+0xdd/0xe0
[<ffffffff811c0aaf>] __alloc_pages_nodemask+0x9f/0x4b0
[<ffffffff81025365>] ? native_sched_clock+0x35/0xa0
[<ffffffff810253d9>] ? sched_clock+0x9/0x10
[<ffffffff8120981a>] alloc_page_interleave+0x3a/0x90
[<ffffffff8120ae8d>] alloc_pages_current+0x17d/0x1f0
[<ffffffff811bab24>] ? __get_free_pages+0x14/0x50
[<ffffffff811bab24>] __get_free_pages+0x14/0x50
[<ffffffff8102225d>] init_espfix_ap+0x17d/0x320
[<ffffffff8105254e>] start_secondary+0x19e/0x350
---[ end trace 2b62d796aa7ae001 ]---
Debugging ... but sorta hoping someone else may have already seen it ;)
P.
next reply other threads:[~2014-10-09 15:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-09 15:35 Prarit Bhargava [this message]
2014-10-15 15:57 ` Lockdep warning with init_espfix_ap() H. Peter Anvin
2014-10-15 16:03 ` Prarit Bhargava
2014-10-15 16:05 ` H. Peter Anvin
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=5436AB4A.1080900@redhat.com \
--to=prarit@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).