mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: shrybman <shrybman@teksavvy.com>
To: "Donald Parsons" <dparsons@brightdsl.net>
Cc: len.brown@intel.com, linux-kernel@vger.kernel.org
Subject: Re[2]: 3.4-rc smpboot: do_boot_cpu failed(-1) to wakeup CPU#1
Date: Wed, 14 Oct 2015 20:17:01 -0400	[thread overview]
Message-ID: <410706506d73adeefedf5b6b21dcc6af@teksavvy.com> (raw)
In-Reply-To: <1444850729.6312.7.camel@falcon.homelinux.org>

..snip..

> >  smpboot: Total of 1 processors activated (4272.42 BogoMIPS)
> >  devtmpfs: initialized
> > I took a guess and got lucky.
> > Reverting "x86/smpboot: Remove APIC.wait_for_init_deassert and atomic init_deasserted" resolved the issue.
> 
> 
> As a followup, I updated compiler to gcc-5.2 (no help or change).
> I also tried suggested /vmlinuz-4.3.0-rc3 parameter in grub: 
>         "cpu_init_udelay=10000"
> which did not help getting missing CPU back online.


Did you try reverting the "x86/smpboot: Remove APIC.wait_for_init_deassert
and atomic init_deasserted"  patch?






  reply	other threads:[~2015-10-15  0:17 UTC|newest]

Thread overview: 17+ 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   ` shrybman [this message]
2015-10-15  2:09     ` Re[2]: " 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
2020-03-22 23:42                 ` itpenguin
2015-10-15 23:19         ` Re[4]: " Brown, Len
2015-10-15 21:18 Re[2]: " shrybman

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=410706506d73adeefedf5b6b21dcc6af@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®