From: Tang Chen <tangchen@cn.fujitsu.com>
To: Dave Jones <davej@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: hang on early boot, numa init code stack overflow?
Date: Thu, 23 Jan 2014 07:39:27 +0800 [thread overview]
Message-ID: <52E056AF.8060005@cn.fujitsu.com> (raw)
In-Reply-To: <20140122163244.GA24936@redhat.com>
On 01/23/2014 12:32 AM, Dave Jones wrote:
> 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
Will send a patch to fix it today.
Thanks.
>
> Dave
>
>
prev parent reply other threads:[~2014-01-22 23:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-22 16:32 hang on early boot, numa init code stack overflow? Dave Jones
2014-01-22 23:39 ` Tang Chen [this message]
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=52E056AF.8060005@cn.fujitsu.com \
--to=tangchen@cn.fujitsu.com \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--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