public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: shrybman <shrybman@teksavvy.com>
To: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
	dparsons@brightdsl.net, x86@kernel.org,
	"Len Brown" <lenb@kernel.org>
Subject: Re: [PATCH/RFT 0/2] regression fix: "smpboot: do_boot_cpu failed(-1) to wakeup CPU#1"
Date: Fri, 16 Oct 2015 02:12:35 -0400	[thread overview]
Message-ID: <9b933cf01de22ee9248bf2146df96cc4@teksavvy.com> (raw)
In-Reply-To: <1444968869-21435-1-git-send-email-lenb@kernel.org>

> Shane, Donald,
> Please test this pair of patches.
> 
> If the default kernel still has a problem booting CPU #1 on yoru Core2 system,
> "cpu_init_udelay=10000" should get you back to the legacy delays.


I tried with both patches and it worked fine without cpu_init_udelay.


Thanks,


Shane


      parent reply	other threads:[~2015-10-16  6:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-16  4:14 [PATCH/RFT 0/2] regression fix: "smpboot: do_boot_cpu failed(-1) to wakeup CPU#1" Len Brown
2015-10-16  4:14 ` [PATCH 1/2] x86 smpboot: fix cpu_init_udelay=10000 Len Brown
2015-10-16  4:14   ` [PATCH 2/2] x86 smpboot: fix CPU #1 boot timeout Len Brown
2015-10-19 17:48     ` [tip:x86/urgent] x86/smpboot: Fix " tip-bot for Len Brown
2015-10-16 19:34   ` [PATCH 1/2] x86 smpboot: fix cpu_init_udelay=10000 shrybman
2015-11-03  5:16     ` Len Brown
2015-11-06  2:39       ` shrybman
2015-10-19 17:47   ` [tip:x86/urgent] x86/smpboot: Fix cpu_init_udelay= 10000 corner case boot parameter misbehavior tip-bot for Len Brown
2015-10-16  5:42 ` [PATCH/RFT 0/2] regression fix: "smpboot: do_boot_cpu failed(-1) to wakeup CPU#1" Donald Parsons
2015-10-16  6:12 ` shrybman [this message]

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=9b933cf01de22ee9248bf2146df96cc4@teksavvy.com \
    --to=shrybman@teksavvy.com \
    --cc=dparsons@brightdsl.net \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox