From: Dave Jones <davej@redhat.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>, tangchen@cn.fujitsu.com
Subject: hang on early boot, numa init code stack overflow?
Date: Wed, 22 Jan 2014 11:32:44 -0500 [thread overview]
Message-ID: <20140122163244.GA24936@redhat.com> (raw)
I'm seeing a hang during boot on my test box running the current tree,
It doesn't always happen, perhaps one in five boots.
I managed to get a partial trace after booting with earlyprintk=vga
dump_stack
panic
? numa_clear_kernel_node_hotplug
__stack_chk_fail
numa_clear_kernel_node_hotplug
? memblock_search_pfn_nid
? __early_pfn_to_nid
numa_init
x86_numa_init
initmem_init
setup_arch
start_kernel
Looks like something overflowed the stack.
This is just a quad-core i5, nothing fancy numa-wise.
This code was added in a0acda917284183f9b71e2d08b0aa0aea722b321
Dave
next reply other threads:[~2014-01-22 16:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-22 16:32 Dave Jones [this message]
2014-01-22 23:39 ` hang on early boot, numa init code stack overflow? Tang Chen
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=20140122163244.GA24936@redhat.com \
--to=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tangchen@cn.fujitsu.com \
--cc=torvalds@linux-foundation.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