mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: shrybman <shrybman@teksavvy.com>
To: "Donald Parsons" <dparsons@brightdsl.net>,
	"Brown, Len" <len.brown@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re[6]: 3.4-rc smpboot: do_boot_cpu failed(-1) to wakeup CPU#1
Date: Thu, 15 Oct 2015 22:03:38 -0400	[thread overview]
Message-ID: <0c5a4ca9d877c3d5b5ed57b96bfc0532@teksavvy.com> (raw)
In-Reply-To: <1A7043D5F58CCB44A599DFD55ED4C9484693815B@fmsmsx115.amr.corp.intel.com>

> try booting upstream with "cpu_init_udelay=1".
> If it works, then it actually implicates this commit:
> 
> a9bcaa02a5104ace6a9d9e4a9cd9192a9e7744d6
> ("x86/smpboot: Remove SIPI delays from cpu_up()")
> 
> Unfortunately the commit message for that on is erroneous --
> "cpu_init_udelay=10000" is actually a NO-OP,
> because that matches the compiled-in default.
> Indeed, any non-zero value bug 10000 should work.


That does seem to work. Heh, I tried that with 10000 last week.


Thanks,


Shane




  reply	other threads:[~2015-10-16  2:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-14 16:20 shrybman
2015-10-14 17:40 ` shrybman
2015-10-14 19:25 ` Donald Parsons
2015-10-15  0:17   ` Re[2]: " shrybman
2015-10-15  2:09     ` Brown, Len
2015-10-15  2:45       ` Donald Parsons
2015-10-15  2:53         ` Brown, Len
2015-10-15 20:21           ` Donald Parsons
2015-10-16  0:03             ` Brown, Len
2015-10-15  3:45       ` Re[4]: " shrybman
2015-10-15 22:55         ` Brown, Len
2015-10-15 23:13           ` Re[6]: " shrybman
2015-10-16  1:06             ` Brown, Len
2015-10-16  2:03               ` shrybman [this message]
2020-03-22 23:42                 ` itpenguin
2015-10-15 23:19         ` Re[4]: " Brown, Len

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=0c5a4ca9d877c3d5b5ed57b96bfc0532@teksavvy.com \
    --to=shrybman@teksavvy.com \
    --cc=dparsons@brightdsl.net \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®