From: Toshi Kani <toshi.kani@hp.com>
To: Chen Gang <gang.chen@asianux.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>,
the arch/x86 maintainers <x86@kernel.org>,
"Yu, Fenghua" <fenghua.yu@intel.com>,
"rafael.j.wysocki@intel.com" <rafael.j.wysocki@intel.com>,
"isimatu.yasuaki@jp.fujitsu.com" <isimatu.yasuaki@jp.fujitsu.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Suggestion] about calling debug_hotplug_cpu() which enabled by 'allmodconfig' for a x86_64 dual core laptop.
Date: Wed, 02 Oct 2013 09:28:45 -0600 [thread overview]
Message-ID: <1380727725.5429.13.camel@misato.fc.hp.com> (raw)
In-Reply-To: <524B8E97.1030707@asianux.com>
On Wed, 2013-10-02 at 03:10 +0000, Chen Gang wrote:
> Hello Maintainers:
>
> Under my x86_64 dual core laptop, I build kernel next-20130927 with
> 'allmodconfig', and install it, the machine can not start. Related
> information is:
>
> after call debug_hotplug_cpu(), output "cpu 0 is offline" .... and then "Failed to execute /init".
>
> After remove "_debug_hotplug_cpu(0, 0);", can pass the issue (but will
> fail in another place). I guess, the reason is my laptop cpu is not
> 'hotplug', but have to call debug_hotplug_cpu() with allmodconfig.
>
>
> I will continue analyzing, welcome any additional suggestions or
> completions.
allmodconfig sets CONFIG_DEBUG_HOTPLUG_CPU0 to y (which is defined as
"def_bool n"), which puts CPU0 offline during boot for testing. This
debug feature is causing the problem on your laptop. I am not familiar
with allmodconfig, but it seems that it enables all the config options,
preferably with 'm'.
Thanks,
-Toshi
next prev parent reply other threads:[~2013-10-02 15:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-02 3:10 [Suggestion] about calling debug_hotplug_cpu() which enabled by 'allmodconfig' for a x86_64 dual core laptop Chen Gang
2013-10-02 15:28 ` Toshi Kani [this message]
2013-10-02 16:41 ` Chen Gang F T
2013-10-02 19:33 ` Toshi Kani
2013-10-03 0:49 ` Chen Gang
2013-10-03 14:21 ` Chen Gang
2013-10-03 15:07 ` Toshi Kani
2013-10-04 9:27 ` Chen Gang
2013-10-03 14:51 ` Toshi Kani
2013-10-04 10:54 ` Chen Gang F T
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=1380727725.5429.13.camel@misato.fc.hp.com \
--to=toshi.kani@hp.com \
--cc=fenghua.yu@intel.com \
--cc=gang.chen@asianux.com \
--cc=hpa@zytor.com \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rafael.j.wysocki@intel.com \
--cc=tglx@linutronix.de \
--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 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.