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

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: <0c5a4ca9d877c3d5b5ed57b96bfc0532@teksavvy.com>
Date:	Thu, 15 Oct 2015 22:03:38 -0400
From:	shrybman <shrybman@...savvy.com>
To:	"Donald Parsons" <dparsons@...ghtdsl.net>,
	"Brown, Len" <len.brown@...el.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re[6]: 3.4-rc smpboot: do_boot_cpu failed(-1) to wakeup CPU#1

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