linux-kernel - RE: Re[2]: 3.4-rc smpboot: do_boot

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1444877109.5998.4.camel@falcon.homelinux.org>
Date:	Wed, 14 Oct 2015 22:45:09 -0400
From:	Donald Parsons <dparsons@...ghtdsl.net>
To:	"Brown, Len" <len.brown@...el.com>
Cc:	shrybman <shrybman@...savvy.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: Re[2]: 3.4-rc smpboot: do_boot_cpu failed(-1) to wakeup CPU#1

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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/