Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1248332 > unrolled thread

[PATCH/RFT 0/2] regression fix: "smpboot: do_boot_cpu failed(-1) to wakeup CPU#1"

Started byLen Brown <lenb@kernel.org>
First post2015-10-16 06:20 +0200
Last post2015-10-16 08:20 +0200
Articles 3 — 3 participants

Back to article view | Back to linux.kernel


Contents

  [PATCH/RFT 0/2] regression fix: "smpboot: do_boot_cpu failed(-1) to wakeup CPU#1" Len Brown <lenb@kernel.org> - 2015-10-16 06:20 +0200
    Re: [PATCH/RFT 0/2] regression fix: "smpboot: do_boot_cpu  failed(-1) to wakeup CPU#1" Donald Parsons <dparsons@brightdsl.net> - 2015-10-16 07:50 +0200
    Re: [PATCH/RFT 0/2] regression fix: "smpboot: do_boot_cpu failed(-1) to wakeup CPU#1" shrybman <shrybman@teksavvy.com> - 2015-10-16 08:20 +0200

#1248332 — [PATCH/RFT 0/2] regression fix: "smpboot: do_boot_cpu failed(-1) to wakeup CPU#1"

FromLen Brown <lenb@kernel.org>
Date2015-10-16 06:20 +0200
Subject[PATCH/RFT 0/2] regression fix: "smpboot: do_boot_cpu failed(-1) to wakeup CPU#1"
Message-ID<qk4EO-3gM-9@gated-at.bofh.it>
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.

thanks,
Len Brown, Intel Open Source Technology Center

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [next] | [standalone]


#1248354 — Re: [PATCH/RFT 0/2] regression fix: "smpboot: do_boot_cpu failed(-1) to wakeup CPU#1"

FromDonald Parsons <dparsons@brightdsl.net>
Date2015-10-16 07:50 +0200
SubjectRe: [PATCH/RFT 0/2] regression fix: "smpboot: do_boot_cpu failed(-1) to wakeup CPU#1"
Message-ID<qk63T-5e3-17@gated-at.bofh.it>
In reply to#1248332
On Fri, 2015-10-16 at 00:14 -0400, Len Brown wrote:
> Shane, Donald,
> Please test this pair of patches.
> 
> If the default kernel still has a problem booting CPU #1 on your Core2 system,
> "cpu_init_udelay=10000" should get you back to the legacy delays.

Applied patches to Linus' 4.3-rc4 (with none of our recently discussed
changes.) 

Result missing CPU is back!

I also tried the "cpu_init_udelay=1" with rc5 and that also gave me back
the missing CPU?  Previously I had tried "cpu_init_udelay=10000" and it
did not get missing CPU back (with rc3 or rc4).

I can do more testing if you need it.

Thanks,
Don



--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]


#1248365

Fromshrybman <shrybman@teksavvy.com>
Date2015-10-16 08:20 +0200
Message-ID<qk6wW-610-17@gated-at.bofh.it>
In reply to#1248332
> 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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web