Re[6]: 3.4-rc smpboot: do_boot_cpu failed(-1) to wakeup CPU#1

2015-10-15 Thread shrybman
> 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=1" is

RE: Re[6]: 3.4-rc smpboot: do_boot_cpu failed(-1) to wakeup CPU#1

2015-10-15 Thread Brown, Len
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=1" is actually a

RE: Re[2]: 3.4-rc smpboot: do_boot_cpu failed(-1) to wakeup CPU#1

2015-10-15 Thread Brown, Len
> 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

RE: Re[4]: 3.4-rc smpboot: do_boot_cpu failed(-1) to wakeup CPU#1

2015-10-15 Thread Brown, Len
> > > 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

Re[6]: 3.4-rc smpboot: do_boot_cpu failed(-1) to wakeup CPU#1

2015-10-15 Thread shrybman
I sent my config directly but here it is again. config-4.3.0-rc5.c-00055-gdacea3b.gz Description: application/gzip

RE: Re[4]: 3.4-rc smpboot: do_boot_cpu failed(-1) to wakeup CPU#1

2015-10-15 Thread Brown, Len
> > 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

Re[2]: 3.4-rc smpboot: do_boot_cpu failed(-1) to wakeup CPU#1

2015-10-15 Thread shrybman
> > 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. Hmm. I have booted this kernel with the reverted patch a couple of times now and it

RE: Re[2]: 3.4-rc smpboot: do_boot_cpu failed(-1) to wakeup CPU#1

2015-10-15 Thread Donald Parsons
On Thu, 2015-10-15 at 02:53 +, 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

Re[6]: 3.4-rc smpboot: do_boot_cpu failed(-1) to wakeup CPU#1

2015-10-15 Thread shrybman
I sent my config directly but here it is again. config-4.3.0-rc5.c-00055-gdacea3b.gz Description: application/gzip

RE: Re[4]: 3.4-rc smpboot: do_boot_cpu failed(-1) to wakeup CPU#1

2015-10-15 Thread Brown, Len
> > > 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

RE: Re[6]: 3.4-rc smpboot: do_boot_cpu failed(-1) to wakeup CPU#1

2015-10-15 Thread Brown, Len
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=1" is actually a

RE: Re[4]: 3.4-rc smpboot: do_boot_cpu failed(-1) to wakeup CPU#1

2015-10-15 Thread Brown, Len
> > 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

Re[6]: 3.4-rc smpboot: do_boot_cpu failed(-1) to wakeup CPU#1

2015-10-15 Thread shrybman
> 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=1" is

RE: Re[2]: 3.4-rc smpboot: do_boot_cpu failed(-1) to wakeup CPU#1

2015-10-15 Thread Brown, Len
> 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

RE: Re[2]: 3.4-rc smpboot: do_boot_cpu failed(-1) to wakeup CPU#1

2015-10-15 Thread Donald Parsons
On Thu, 2015-10-15 at 02:53 +, 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

Re[2]: 3.4-rc smpboot: do_boot_cpu failed(-1) to wakeup CPU#1

2015-10-15 Thread shrybman
> > 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. Hmm. I have booted this kernel with the reverted patch a couple of times now and it

Re[4]: 3.4-rc smpboot: do_boot_cpu failed(-1) to wakeup CPU#1

2015-10-14 Thread shrybman
> 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

RE: Re[2]: 3.4-rc smpboot: do_boot_cpu failed(-1) to wakeup CPU#1

2015-10-14 Thread Brown, Len
> > > 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

RE: Re[2]: 3.4-rc smpboot: do_boot_cpu failed(-1) to wakeup CPU#1

2015-10-14 Thread Donald Parsons
On Thu, 2015-10-15 at 02:09 +, Brown, Len wrote: > Donald, Shane, > Thanks for reporting this. > > > > I also tried suggested /vmlinuz-4.3.0-rc3 parameter in grub: > > > "cpu_init_udelay=1" > > > which did not help getting missing CPU back online. > > right, if the issue is

RE: Re[2]: 3.4-rc smpboot: do_boot_cpu failed(-1) to wakeup CPU#1

2015-10-14 Thread Brown, Len
Donald, Shane, Thanks for reporting this. > > I also tried suggested /vmlinuz-4.3.0-rc3 parameter in grub: > >        "cpu_init_udelay=1" > > 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

Re[2]: 3.4-rc smpboot: do_boot_cpu failed(-1) to wakeup CPU#1

2015-10-14 Thread shrybman
..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

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

2015-10-14 Thread Donald Parsons
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

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

2015-10-14 Thread shrybman
> 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 majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

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

2015-10-14 Thread shrybman
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

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

2015-10-14 Thread shrybman
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

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

2015-10-14 Thread shrybman
> 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 majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

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

2015-10-14 Thread Donald Parsons
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

Re[2]: 3.4-rc smpboot: do_boot_cpu failed(-1) to wakeup CPU#1

2015-10-14 Thread shrybman
..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

Re[4]: 3.4-rc smpboot: do_boot_cpu failed(-1) to wakeup CPU#1

2015-10-14 Thread shrybman
> 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

RE: Re[2]: 3.4-rc smpboot: do_boot_cpu failed(-1) to wakeup CPU#1

2015-10-14 Thread Brown, Len
Donald, Shane, Thanks for reporting this. > > I also tried suggested /vmlinuz-4.3.0-rc3 parameter in grub: > >        "cpu_init_udelay=1" > > 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

RE: Re[2]: 3.4-rc smpboot: do_boot_cpu failed(-1) to wakeup CPU#1

2015-10-14 Thread Donald Parsons
On Thu, 2015-10-15 at 02:09 +, Brown, Len wrote: > Donald, Shane, > Thanks for reporting this. > > > > I also tried suggested /vmlinuz-4.3.0-rc3 parameter in grub: > > > "cpu_init_udelay=1" > > > which did not help getting missing CPU back online. > > right, if the issue is

RE: Re[2]: 3.4-rc smpboot: do_boot_cpu failed(-1) to wakeup CPU#1

2015-10-14 Thread Brown, Len
> > > 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