From: Donald Parsons <dparsons@brightdsl.net>
To: "Brown, Len" <len.brown@intel.com>
Cc: shrybman <shrybman@teksavvy.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: Re[2]: 3.4-rc smpboot: do_boot_cpu failed(-1) to wakeup CPU#1
Date: Thu, 15 Oct 2015 16:21:16 -0400 [thread overview]
Message-ID: <1444940476.6000.15.camel@falcon.homelinux.org> (raw)
In-Reply-To: <1A7043D5F58CCB44A599DFD55ED4C94846937781@fmsmsx115.amr.corp.intel.com>
On Thu, 2015-10-15 at 02:53 +0000, Brown, Len wrote:
> > > > Did you try reverting the "x86/smpboot: Remove
> > APIC.wait_for_init_deassert
> > > > and atomic init_deasserted" patch?
> > >
> > > Yes, please let me know if reverting that patch helps you too.
> >
> > How? Please send a patch or git cmd(s). I have the
> > git/stable/linux-stable.git on my PC. Thanks.
>
> git log calls it this:
>
> commit 656bba306827a44ed73b3f93f75bb3147de17fae
> Author: Len Brown <len.brown@intel.com>
> Date: Sun Aug 16 11:45:48 2015 -0400
>
> x86/smpboot: Remove APIC.wait_for_init_deassert and atomic init_deasserted
>
> So you want to simply do this:
>
> $ git revert 656bba306827a44ed73b3f93f75bb3147de17fae
>
> build and test.
I did the revert in linux-stable (last tag being v4.3-rc4) gave a revert
description so it would be applied.
built and tested. Result: did not help, still missing the second core.
I am sure the revert happened but I am uncertain as to how to build in a
git tree. I think I did it correctly
cp .config into linux-stable tree
edit Makefile to add -rev to: EXTRAVERSION = -rc4-rev
make oldconfig
make -j3 >> ../mak/mak_430-rc4-rev.log 2>&1 &
The before/after kernels are:
3965280 Oct 4 15:20 vmlinuz-4.3.0-rc4
3965408 Oct 15 13:45 vmlinuz-4.3.0-rc4-rev
The reverted vmlinuz is 128 bytes bigger; .config's are identical. I
see the revert adds back in some code so sizes seem appropriate.
Don
next prev parent reply other threads:[~2015-10-15 20:21 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 ` 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 [this message]
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=1444940476.6000.15.camel@falcon.homelinux.org \
--to=dparsons@brightdsl.net \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shrybman@teksavvy.com \
/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®