From: shrybman <shrybman@teksavvy.com>
To: linux-kernel@vger.kernel.org
Cc: len.brown@intel.com, dparsons@brightdsl.net
Subject: 3.4-rc smpboot: do_boot_cpu failed(-1) to wakeup CPU#1
Date: Wed, 14 Oct 2015 12:20:20 -0400 [thread overview]
Message-ID: <505f039bc185286b1295600807741499@teksavvy.com> (raw)
All 3.4-rc kernels I have tried displayed this issue.
This report looks similar https://lkml.org/lkml/2015/9/26/165.
I also have a Core 2 cpu on a Asus P5B (not deluxe) board.
...
ACPI: Core revision 20150818
ACPI: 1 ACPI AML tables successfully acquired and loaded
Mount-cache hash table entries: 8192 (order: 4, 65536 bytes)
Mountpoint-cache hash table entries: 8192 (order: 4, 65536 bytes)
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
mce: CPU supports 6 MCE banks
CPU0: Thermal monitoring enabled (TM2)
process: using mwait in idle threads
Last level iTLB entries: 4KB 128, 2MB 4, 4MB 4
Last level dTLB entries: 4KB 256, 2MB 0, 4MB 32, 1GB 0
Freeing SMP alternatives memory: 20K (ffffffff819b5000 - ffffffff819ba000)
ftrace: allocating 18583 entries in 73 pages
..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
smpboot: CPU0: Intel(R) Core(TM)2 CPU 6400 @ 2.13GHz (fam: 06, model: 0f, stepping: 06)
Performance Events: PEBS fmt0-, 4-deep LBR, Core2 events, Intel PMU driver.
perf_event_intel: PEBS disabled due to CPU errata
... version: 2
... bit width: 40
... generic registers: 2
... value mask: 000000ffffffffff
... max period: 000000007fffffff
... fixed-purpose events: 3
... event mask: 0000000700000003
x86: Booting SMP configuration:
.... node #0, CPUs: #1
smpboot: do_boot_cpu failed(-1) to wakeup CPU#1
x86: Booted up 1 node, 1 CPUs
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.
Regards,
Shane
next reply other threads:[~2015-10-14 16:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-14 16:20 shrybman [this message]
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
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
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=505f039bc185286b1295600807741499@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®