Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1248301
| From | shrybman <shrybman@teksavvy.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re[6]: 3.4-rc smpboot: do_boot_cpu failed(-1) to wakeup CPU#1 |
| Date | 2015-10-16 04:10 +0200 |
| Message-ID | <qk2CZ-he-3@gated-at.bofh.it> (permalink) |
| References | (3 earlier) <qjG9s-AK-17@gated-at.bofh.it> <qjHId-2KW-5@gated-at.bofh.it> <qjZF8-3XH-9@gated-at.bofh.it> <qjZYt-4zh-11@gated-at.bofh.it> <qk1GW-7np-7@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
> 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
--
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/
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
3.4-rc smpboot: do_boot_cpu failed(-1) to wakeup CPU#1 shrybman <shrybman@teksavvy.com> - 2015-10-14 18:40 +0200
Re: 3.4-rc smpboot: do_boot_cpu failed(-1) to wakeup CPU#1 shrybman <shrybman@teksavvy.com> - 2015-10-14 19:50 +0200
Re: 3.4-rc smpboot: do_boot_cpu failed(-1) to wakeup CPU#1 Donald Parsons <dparsons@brightdsl.net> - 2015-10-14 22:20 +0200
Re[2]: 3.4-rc smpboot: do_boot_cpu failed(-1) to wakeup CPU#1 shrybman <shrybman@teksavvy.com> - 2015-10-15 02:20 +0200
RE: Re[2]: 3.4-rc smpboot: do_boot_cpu failed(-1) to wakeup CPU#1 "Brown, Len" <len.brown@intel.com> - 2015-10-15 04:10 +0200
RE: Re[2]: 3.4-rc smpboot: do_boot_cpu failed(-1) to wakeup CPU#1 Donald Parsons <dparsons@brightdsl.net> - 2015-10-15 04:50 +0200
RE: Re[2]: 3.4-rc smpboot: do_boot_cpu failed(-1) to wakeup CPU#1 "Brown, Len" <len.brown@intel.com> - 2015-10-15 05:00 +0200
RE: Re[2]: 3.4-rc smpboot: do_boot_cpu failed(-1) to wakeup CPU#1 Donald Parsons <dparsons@brightdsl.net> - 2015-10-15 22:30 +0200
RE: Re[2]: 3.4-rc smpboot: do_boot_cpu failed(-1) to wakeup CPU#1 "Brown, Len" <len.brown@intel.com> - 2015-10-16 02:10 +0200
Re[4]: 3.4-rc smpboot: do_boot_cpu failed(-1) to wakeup CPU#1 shrybman <shrybman@teksavvy.com> - 2015-10-15 05:50 +0200
RE: Re[4]: 3.4-rc smpboot: do_boot_cpu failed(-1) to wakeup CPU#1 "Brown, Len" <len.brown@intel.com> - 2015-10-16 01:00 +0200
Re[6]: 3.4-rc smpboot: do_boot_cpu failed(-1) to wakeup CPU#1 shrybman <shrybman@teksavvy.com> - 2015-10-16 01:20 +0200
RE: Re[6]: 3.4-rc smpboot: do_boot_cpu failed(-1) to wakeup CPU#1 "Brown, Len" <len.brown@intel.com> - 2015-10-16 03:10 +0200
Re[6]: 3.4-rc smpboot: do_boot_cpu failed(-1) to wakeup CPU#1 shrybman <shrybman@teksavvy.com> - 2015-10-16 04:10 +0200
RE: Re[4]: 3.4-rc smpboot: do_boot_cpu failed(-1) to wakeup CPU#1 "Brown, Len" <len.brown@intel.com> - 2015-10-16 01:30 +0200
csiph-web