[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1A7043D5F58CCB44A599DFD55ED4C948469380B6@fmsmsx115.amr.corp.intel.com>
Date: Thu, 15 Oct 2015 23:19:29 +0000
From: "Brown, Len" <len.brown@...el.com>
To: shrybman <shrybman@...savvy.com>,
Donald Parsons <dparsons@...ghtdsl.net>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: Re[4]: 3.4-rc smpboot: do_boot_cpu failed(-1) to wakeup CPU#1
> > > You have similar hardware:
> > >
> > > Shane:
> > >
> > > smpboot: CPU0: Intel(R) Core(TM)2 CPU 6400 @ 2.13GHz (fam:
> 06,
> > model: 0f, stepping: 06)
> > >
> > > Donald:
> > >
> > > CPU : Intel Core 2 CPU 6600 @ 2.4GHz
> > >
> > > I think I can get ahold of a core2 6xxx box tomorrow.
>
> Intel(R) Core(TM)2 CPU E6800 @ 2.93GHz
>
> is working for me with latest upstream.
> (It is on an Intel D975 XBX motherboard)
Good news - I reproduced the failure on a similar box, an Intel D975xbx2:
[ 0.000000] Linux version 4.3.0-rc5+ (lenb@z87) (gcc version 4.9.2 20150212 (Red Hat 4.9.2-6) (GCC) ) #375 SMP Thu Oct 15 18:17:04 EDT 2015
...
[ 0.084000] smpboot: CPU0: Intel(R) Core(TM)2 Quad CPU @ 2.66GHz (family: 0x6, model: 0xf, stepping: 0x7)
[ 0.084000] Performance Events: PEBS fmt0-, 4-deep LBR, Core2 events, Intel PMU driver.
[ 0.084000] perf_event_intel: PEBS disabled due to CPU errata
[ 0.084000] ... version: 2
[ 0.084000] ... bit width: 40
[ 0.084000] ... generic registers: 2
[ 0.084000] ... value mask: 000000ffffffffff
[ 0.084000] ... max period: 000000007fffffff
[ 0.084000] ... fixed-purpose events: 3
[ 0.084000] ... event mask: 0000000700000003
[ 0.084000] x86: Booting SMP configuration:
[ 0.084000] .... node #0, CPUs: #1
[ 10.080003] smpboot: do_boot_cpu failed(-1) to wakeup CPU#1
[ 10.080175] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
[ 10.080334] #2 #3
[ 10.084017] x86: Booted up 1 node, 3 CPUs
[ 10.084120] smpboot: Total of 3 processors activated (16001.58 BogoMIPS)
Powered by blists - more mailing lists