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

Groups > linux.kernel > #1246992 > unrolled thread

3.4-rc smpboot: do_boot_cpu failed(-1) to wakeup CPU#1

Started byshrybman <shrybman@teksavvy.com>
First post2015-10-14 18:40 +0200
Last post2015-10-16 01:30 +0200
Articles 15 — 3 participants

Back to article view | Back to linux.kernel

Contents

  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

#1246992 — 3.4-rc smpboot: do_boot_cpu failed(-1) to wakeup CPU#1

Fromshrybman <shrybman@teksavvy.com>
Date2015-10-14 18:40 +0200
Subject3.4-rc smpboot: do_boot_cpu failed(-1) to wakeup CPU#1
Message-ID<qjxfT-493-63@gated-at.bofh.it>
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

--
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]

#1247033

Fromshrybman <shrybman@teksavvy.com>
Date2015-10-14 19:50 +0200
Message-ID<qjylA-5Hm-1@gated-at.bofh.it>
In reply to#1246992
> All 3.4-rc kernels I have tried displayed this issue.


Stupid typo, that should be kernel v4.3-rc.

--
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]

#1247129

FromDonald Parsons <dparsons@brightdsl.net>
Date2015-10-14 22:20 +0200
Message-ID<qjAGK-O8-19@gated-at.bofh.it>
In reply to#1246992
On Wed, 2015-10-14 at 12:20 -0400, shrybman wrote:
> 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.


As a followup, I updated compiler to gcc-5.2 (no help or change).
I also tried suggested /vmlinuz-4.3.0-rc3 parameter in grub: 
        "cpu_init_udelay=10000"
which did not help getting missing CPU back online.

So all linux-4.3.0-rc[15] lose the second CPU core.

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]

#1247269

Fromshrybman <shrybman@teksavvy.com>
Date2015-10-15 02:20 +0200
Message-ID<qjEqZ-6uo-7@gated-at.bofh.it>
In reply to#1247129
..snip..

> >  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.
> 
> 
> As a followup, I updated compiler to gcc-5.2 (no help or change).
> I also tried suggested /vmlinuz-4.3.0-rc3 parameter in grub: 
>         "cpu_init_udelay=10000"
> which did not help getting missing CPU back online.


Did you try reverting the "x86/smpboot: Remove APIC.wait_for_init_deassert
and atomic init_deasserted"  patch?





--
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]

#1247322

From"Brown, Len" <len.brown@intel.com>
Date2015-10-15 04:10 +0200
Message-ID<qjG9s-AK-17@gated-at.bofh.it>
In reply to#1247269
RG9uYWxkLCBTaGFuZSwNClRoYW5rcyBmb3IgcmVwb3J0aW5nIHRoaXMuDQoNCj4gPiBJIGFsc28g
dHJpZWQgc3VnZ2VzdGVkIC92bWxpbnV6LTQuMy4wLXJjMyBwYXJhbWV0ZXIgaW4gZ3J1YjoNCj4g
PiAgwqAgwqAgwqAgwqAiY3B1X2luaXRfdWRlbGF5PTEwMDAwIg0KPiA+IHdoaWNoIGRpZCBub3Qg
aGVscCBnZXR0aW5nIG1pc3NpbmcgQ1BVIGJhY2sgb25saW5lLg0KDQpyaWdodCwgaWYgdGhlIGlz
c3VlIGlzIGNhdXNlZCBieSB0aGUgcGF0Y2ggYmVsb3csDQp0aGF0IGNtZGxpbmUgd2lsbCBub3Qg
aGVscC4NCg0KPiBEaWQgeW91IHRyeSByZXZlcnRpbmcgdGhlICJ4ODYvc21wYm9vdDogUmVtb3Zl
IEFQSUMud2FpdF9mb3JfaW5pdF9kZWFzc2VydA0KPiBhbmQgYXRvbWljIGluaXRfZGVhc3NlcnRl
ZCLCoCBwYXRjaD8NCg0KWWVzLCBwbGVhc2UgbGV0IG1lIGtub3cgaWYgcmV2ZXJ0aW5nIHRoYXQg
cGF0Y2ggaGVscHMgeW91IHRvby4NCg0KWW91IGhhdmUgc2ltaWxhciBoYXJkd2FyZToNCg0KU2hh
bmU6DQoNCnNtcGJvb3Q6IENQVTA6IEludGVsKFIpIENvcmUoVE0pMiBDUFUgICAgICAgICAgNjQw
MCAgQCAyLjEzR0h6IChmYW06IDA2LCBtb2RlbDogMGYsIHN0ZXBwaW5nOiAwNikNCg0KRG9uYWxk
Og0KDQpDUFUgOiBJbnRlbCBDb3JlIDIgQ1BVIDY2MDAgQCAyLjRHSHoNCg0KSSB0aGluayBJIGNh
biBnZXQgYWhvbGQgb2YgYSBjb3JlMiA2eHh4IGJveCB0b21vcnJvdy4NClBsZWFzZSBzZW5kIG1l
IHlvdXIgLmNvbmZpZyBkaXJlY3RseSwgYW5kIEknbGwgc2VlIGlmIEkgY2FuIHJlcHJvZHVjZSB0
aGUgaXNzdWUuDQoNCnRoYW5rcywNCi1MZW4NCg0K
--
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]

#1247356

FromDonald Parsons <dparsons@brightdsl.net>
Date2015-10-15 04:50 +0200
Message-ID<qjGMa-1of-9@gated-at.bofh.it>
In reply to#1247322
On Thu, 2015-10-15 at 02:09 +0000, Brown, Len wrote:
> Donald, Shane,
> Thanks for reporting this.
> 
> > > I also tried suggested /vmlinuz-4.3.0-rc3 parameter in grub:
> > >         "cpu_init_udelay=10000"
> > > which did not help getting missing CPU back online.
> 
> right, if the issue is caused by the patch below,
> that cmdline will not help.
> 
> > Did you try reverting the "x86/smpboot: Remove APIC.wait_for_init_deassert
> > and atomic init_deasserted"  patch?
> 
> Yes, please let me know if reverting that patch helps you too.

How?  Please send a patch or git cmd(s).    I have the
    git/stable/linux-stable.git  on my PC.   Thanks.


> 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

Mine is also same (fam: 06, model: 0f, stepping: 06).

> I think I can get ahold of a core2 6xxx box tomorrow.
> Please send me your .config directly, and I'll see if I can reproduce the issue.

Will do.

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]

#1247359

From"Brown, Len" <len.brown@intel.com>
Date2015-10-15 05:00 +0200
Message-ID<qjGVQ-1zi-1@gated-at.bofh.it>
In reply to#1247356
> > > Did you try reverting the "x86/smpboot: Remove
> APIC.wait_for_init_deassert
> > > and atomic init_deasserted"  patch?
> >
> > Yes, please let me know if reverting that patch helps you too.
> 
> How?  Please send a patch or git cmd(s).    I have the
>     git/stable/linux-stable.git  on my PC.   Thanks.

git log calls it this:

commit 656bba306827a44ed73b3f93f75bb3147de17fae
Author: Len Brown <len.brown@intel.com>
Date:   Sun Aug 16 11:45:48 2015 -0400

    x86/smpboot: Remove APIC.wait_for_init_deassert and atomic init_deasserted

So you want to simply do this:

$ git revert 656bba306827a44ed73b3f93f75bb3147de17fae

build and test.

cheers,
-Len


--
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]

#1248148

FromDonald Parsons <dparsons@brightdsl.net>
Date2015-10-15 22:30 +0200
Message-ID<qjXjX-DP-9@gated-at.bofh.it>
In reply to#1247359
On Thu, 2015-10-15 at 02:53 +0000, Brown, Len wrote:
> > > > Did you try reverting the "x86/smpboot: Remove
> > APIC.wait_for_init_deassert
> > > > and atomic init_deasserted"  patch?
> > >
> > > Yes, please let me know if reverting that patch helps you too.
> > 
> > How?  Please send a patch or git cmd(s).    I have the
> >     git/stable/linux-stable.git  on my PC.   Thanks.
> 
> git log calls it this:
> 
> commit 656bba306827a44ed73b3f93f75bb3147de17fae
> Author: Len Brown <len.brown@intel.com>
> Date:   Sun Aug 16 11:45:48 2015 -0400
> 
>     x86/smpboot: Remove APIC.wait_for_init_deassert and atomic init_deasserted
> 
> So you want to simply do this:
> 
> $ git revert 656bba306827a44ed73b3f93f75bb3147de17fae
> 
> build and test.

I did the revert in linux-stable (last tag being v4.3-rc4) gave a revert
description so it would be applied.

built and tested.  Result:  did not help, still missing the second core.

I am sure the revert happened but I am uncertain as to how to build in a
git tree.  I think I did it correctly
   cp .config into   linux-stable   tree
   edit Makefile to add -rev to: EXTRAVERSION = -rc4-rev
   make oldconfig
   make -j3 >> ../mak/mak_430-rc4-rev.log 2>&1 &

The before/after kernels are:
    3965280 Oct  4 15:20 vmlinuz-4.3.0-rc4
    3965408 Oct 15 13:45 vmlinuz-4.3.0-rc4-rev
The reverted vmlinuz is 128 bytes bigger;  .config's are identical.  I
see the revert adds back in some code so sizes seem appropriate.

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]

#1248266

From"Brown, Len" <len.brown@intel.com>
Date2015-10-16 02:10 +0200
Message-ID<qk0KS-5Z0-15@gated-at.bofh.it>
In reply to#1248148
> I did the revert in linux-stable (last tag being v4.3-rc4) gave a revert
> description so it would be applied.
> 
> built and tested.  Result:  did not help, still missing the second core.

Same result here.

upstream failed to bring up CPU #1 on 5/5 boots

    Revert "x86/smpboot: Remove APIC.wait_for_init_deassert and atomic init_deasserted"

    This reverts commit 656bba306827a44ed73b3f93f75bb3147de17fae.

Still fails the same way.

Adding "cpu_init_udelay=10000"

does not help.

commence bisect...

cheers,
-Len


--
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]

#1247376

Fromshrybman <shrybman@teksavvy.com>
Date2015-10-15 05:50 +0200
Message-ID<qjHId-2KW-5@gated-at.bofh.it>
In reply to#1247322
> Donald, Shane,
> Thanks for reporting this.

Sure! Thanks for looking into it.

> 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.


Maybe the mobo/bios? We both have the same Asus P5B as well. Donald said he has the deluxe version while I have the plain version.



--
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]

#1248234

From"Brown, Len" <len.brown@intel.com>
Date2015-10-16 01:00 +0200
Message-ID<qjZF8-3XH-9@gated-at.bofh.it>
In reply to#1247376
PiA+IFlvdSBoYXZlIHNpbWlsYXIgaGFyZHdhcmU6DQo+ID4NCj4gPiBTaGFuZToNCj4gPg0KPiA+
IHNtcGJvb3Q6IENQVTA6IEludGVsKFIpIENvcmUoVE0pMiBDUFUgwqAgwqAgwqAgwqAgwqA2NDAw
IMKgQCAyLjEzR0h6IChmYW06IDA2LA0KPiBtb2RlbDogMGYsIHN0ZXBwaW5nOiAwNikNCj4gPg0K
PiA+IERvbmFsZDoNCj4gPg0KPiA+IENQVSA6IEludGVsIENvcmUgMiBDUFUgNjYwMCBAIDIuNEdI
eg0KPiA+DQo+ID4gSSB0aGluayBJIGNhbiBnZXQgYWhvbGQgb2YgYSBjb3JlMiA2eHh4IGJveCB0
b21vcnJvdy4NCg0KSW50ZWwoUikgQ29yZShUTSkyIENQVSAgICAgICAgIEU2ODAwICBAIDIuOTNH
SHoNCg0KaXMgd29ya2luZyBmb3IgbWUgd2l0aCBsYXRlc3QgdXBzdHJlYW0uDQooSXQgaXMgb24g
YW4gSW50ZWwgRDk3NSBYQlggbW90aGVyYm9hcmQpDQoNCnBsZWFzZSBzZW5kIG1lIHRoZSAuY29u
ZmlnIHlvdSBhcmUgdXNpbmcNCnRoYXQgZmFpbHMgYW5kIEknbGwgdHJ5IHRoYXQuDQoNCnRoYW5r
cywNCi1MZW4NCg0K
--
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]

#1248243

Fromshrybman <shrybman@teksavvy.com>
Date2015-10-16 01:20 +0200
Message-ID<qjZYt-4zh-11@gated-at.bofh.it>
In reply to#1248234

[Multipart message — attachments visible in raw view] — view raw

I sent my config directly but here it is again.

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

#1248285

From"Brown, Len" <len.brown@intel.com>
Date2015-10-16 03:10 +0200
Message-ID<qk1GW-7np-7@gated-at.bofh.it>
In reply to#1248243
dHJ5IGJvb3RpbmcgdXBzdHJlYW0gd2l0aCAiY3B1X2luaXRfdWRlbGF5PTEiLg0KSWYgaXQgd29y
a3MsIHRoZW4gaXQgYWN0dWFsbHkgaW1wbGljYXRlcyB0aGlzIGNvbW1pdDoNCg0KYTliY2FhMDJh
NTEwNGFjZTZhOWQ5ZTRhOWNkOTE5MmE5ZTc3NDRkNg0KKCJ4ODYvc21wYm9vdDogUmVtb3ZlIFNJ
UEkgZGVsYXlzIGZyb20gY3B1X3VwKCkiKQ0KDQpVbmZvcnR1bmF0ZWx5IHRoZSBjb21taXQgbWVz
c2FnZSBmb3IgdGhhdCBvbiBpcyBlcnJvbmVvdXMgLS0NCiJjcHVfaW5pdF91ZGVsYXk9MTAwMDAi
IGlzIGFjdHVhbGx5IGEgTk8tT1AsDQpiZWNhdXNlIHRoYXQgbWF0Y2hlcyB0aGUgY29tcGlsZWQt
aW4gZGVmYXVsdC4NCkluZGVlZCwgYW55IG5vbi16ZXJvIHZhbHVlIGJ1ZyAxMDAwMCBzaG91bGQg
d29yay4NCg0KdGhhbmtzLA0KLUxlbg0KDQo=
--
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]

#1248301

Fromshrybman <shrybman@teksavvy.com>
Date2015-10-16 04:10 +0200
Message-ID<qk2CZ-he-3@gated-at.bofh.it>
In reply to#1248285
> 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/

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

#1248244

From"Brown, Len" <len.brown@intel.com>
Date2015-10-16 01:30 +0200
Message-ID<qk08a-4Qv-1@gated-at.bofh.it>
In reply to#1247376
PiA+ID4gWW91IGhhdmUgc2ltaWxhciBoYXJkd2FyZToNCj4gPiA+DQo+ID4gPiBTaGFuZToNCj4g
PiA+DQo+ID4gPiBzbXBib290OiBDUFUwOiBJbnRlbChSKSBDb3JlKFRNKTIgQ1BVIMKgIMKgIMKg
IMKgIMKgNjQwMCDCoEAgMi4xM0dIeiAoZmFtOg0KPiAwNiwNCj4gPiBtb2RlbDogMGYsIHN0ZXBw
aW5nOiAwNikNCj4gPiA+DQo+ID4gPiBEb25hbGQ6DQo+ID4gPg0KPiA+ID4gQ1BVIDogSW50ZWwg
Q29yZSAyIENQVSA2NjAwIEAgMi40R0h6DQo+ID4gPg0KPiA+ID4gSSB0aGluayBJIGNhbiBnZXQg
YWhvbGQgb2YgYSBjb3JlMiA2eHh4IGJveCB0b21vcnJvdy4NCj4gDQo+IEludGVsKFIpIENvcmUo
VE0pMiBDUFUgICAgICAgICBFNjgwMCAgQCAyLjkzR0h6DQo+IA0KPiBpcyB3b3JraW5nIGZvciBt
ZSB3aXRoIGxhdGVzdCB1cHN0cmVhbS4NCj4gKEl0IGlzIG9uIGFuIEludGVsIEQ5NzUgWEJYIG1v
dGhlcmJvYXJkKQ0KDQpHb29kIG5ld3MgLSBJIHJlcHJvZHVjZWQgdGhlIGZhaWx1cmUgb24gYSBz
aW1pbGFyIGJveCwgYW4gSW50ZWwgRDk3NXhieDI6DQoNClsgICAgMC4wMDAwMDBdIExpbnV4IHZl
cnNpb24gNC4zLjAtcmM1KyAobGVuYkB6ODcpIChnY2MgdmVyc2lvbiA0LjkuMiAyMDE1MDIxMiAo
UmVkIEhhdCA0LjkuMi02KSAoR0NDKSApICMzNzUgU01QIFRodSBPY3QgMTUgMTg6MTc6MDQgRURU
IDIwMTUNCi4uLg0KWyAgICAwLjA4NDAwMF0gc21wYm9vdDogQ1BVMDogSW50ZWwoUikgQ29yZShU
TSkyIFF1YWQgQ1BVICAgICAgICAgICBAIDIuNjZHSHogKGZhbWlseTogMHg2LCBtb2RlbDogMHhm
LCBzdGVwcGluZzogMHg3KQ0KWyAgICAwLjA4NDAwMF0gUGVyZm9ybWFuY2UgRXZlbnRzOiBQRUJT
IGZtdDAtLCA0LWRlZXAgTEJSLCBDb3JlMiBldmVudHMsIEludGVsIFBNVSBkcml2ZXIuDQpbICAg
IDAuMDg0MDAwXSBwZXJmX2V2ZW50X2ludGVsOiBQRUJTIGRpc2FibGVkIGR1ZSB0byBDUFUgZXJy
YXRhDQpbICAgIDAuMDg0MDAwXSAuLi4gdmVyc2lvbjogICAgICAgICAgICAgICAgMg0KWyAgICAw
LjA4NDAwMF0gLi4uIGJpdCB3aWR0aDogICAgICAgICAgICAgIDQwDQpbICAgIDAuMDg0MDAwXSAu
Li4gZ2VuZXJpYyByZWdpc3RlcnM6ICAgICAgMg0KWyAgICAwLjA4NDAwMF0gLi4uIHZhbHVlIG1h
c2s6ICAgICAgICAgICAgIDAwMDAwMGZmZmZmZmZmZmYNClsgICAgMC4wODQwMDBdIC4uLiBtYXgg
cGVyaW9kOiAgICAgICAgICAgICAwMDAwMDAwMDdmZmZmZmZmDQpbICAgIDAuMDg0MDAwXSAuLi4g
Zml4ZWQtcHVycG9zZSBldmVudHM6ICAgMw0KWyAgICAwLjA4NDAwMF0gLi4uIGV2ZW50IG1hc2s6
ICAgICAgICAgICAgIDAwMDAwMDA3MDAwMDAwMDMNClsgICAgMC4wODQwMDBdIHg4NjogQm9vdGlu
ZyBTTVAgY29uZmlndXJhdGlvbjoNClsgICAgMC4wODQwMDBdIC4uLi4gbm9kZSAgIzAsIENQVXM6
ICAgICAgIzENClsgICAxMC4wODAwMDNdIHNtcGJvb3Q6IGRvX2Jvb3RfY3B1IGZhaWxlZCgtMSkg
dG8gd2FrZXVwIENQVSMxDQpbICAgMTAuMDgwMTc1XSBOTUkgd2F0Y2hkb2c6IGVuYWJsZWQgb24g
YWxsIENQVXMsIHBlcm1hbmVudGx5IGNvbnN1bWVzIG9uZSBody1QTVUgY291bnRlci4NClsgICAx
MC4wODAzMzRdICAjMiAjMw0KWyAgIDEwLjA4NDAxN10geDg2OiBCb290ZWQgdXAgMSBub2RlLCAz
IENQVXMNClsgICAxMC4wODQxMjBdIHNtcGJvb3Q6IFRvdGFsIG9mIDMgcHJvY2Vzc29ycyBhY3Rp
dmF0ZWQgKDE2MDAxLjU4IEJvZ29NSVBTKQ0KDQo=
--
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