All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chen Gang <gang.chen@asianux.com>
To: Thomas Gleixner <tglx@linutronix.de>,
	"mingo@redhat.com" <mingo@redhat.com>,
	"H. Peter Anvin" <hpa@zytor.com>
Cc: the arch/x86 maintainers <x86@kernel.org>,
	"Yu, Fenghua" <fenghua.yu@intel.com>,
	toshi.kani@hp.com, rafael.j.wysocki@intel.com,
	isimatu.yasuaki@jp.fujitsu.com,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [Suggestion] about calling debug_hotplug_cpu() which enabled by 'allmodconfig' for a x86_64 dual core laptop.
Date: Wed, 02 Oct 2013 11:10:15 +0800	[thread overview]
Message-ID: <524B8E97.1030707@asianux.com> (raw)

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.

Thanks.
-- 
Chen Gang

             reply	other threads:[~2013-10-02  3:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-02  3:10 Chen Gang [this message]
2013-10-02 15:28 ` [Suggestion] about calling debug_hotplug_cpu() which enabled by 'allmodconfig' for a x86_64 dual core laptop Toshi Kani
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=524B8E97.1030707@asianux.com \
    --to=gang.chen@asianux.com \
    --cc=fenghua.yu@intel.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=toshi.kani@hp.com \
    --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.