public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: itpenguin <info@itpenguin.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Re[6]: 3.4-rc smpboot: do_boot_cpu failed(-1) to wakeup CPU#1
Date: Sun, 22 Mar 2020 16:42:58 -0700 (MST)	[thread overview]
Message-ID: <1584920578289-0.post@n7.nabble.com> (raw)
In-Reply-To: <0c5a4ca9d877c3d5b5ed57b96bfc0532@teksavvy.com>

I'm a little bit confused about this thread, because I'm facing a similiar
problem on my system:

I have a CentOS 7.7 AltArch i386 installation:
Linux erbusze 3.10.0-1062.18.1.el7.centos.plus.i686 #1 SMP Wed Mar 18
12:57:13 UTC 2020 i686 i686 i386 GNU/Linux

on this CPU:
smpboot: CPU0: Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz (fam: 06, model: 5e,
stepping: 03)

with these boot errors:
[    0.160538] Kernel panic - not syncing: Fatal exception
[   10.166450] smpboot: do_boot_cpu failed(-1) to wakeup CPU#1

I tried several different values of cpu_init_udelay in the kernel command
boot line, but with no changes to the described behaviour.



--
Sent from: http://linux-kernel.2935.n7.nabble.com/

  reply	other threads:[~2020-03-22 23:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-14 16:20 3.4-rc smpboot: do_boot_cpu failed(-1) to wakeup CPU#1 shrybman
2015-10-14 17:40 ` shrybman
2015-10-14 19:25 ` Donald Parsons
2015-10-15  0:17   ` Re[2]: " shrybman
2015-10-15  2:09     ` Brown, Len
2015-10-15  2:45       ` Donald Parsons
2015-10-15  2:53         ` Brown, Len
2015-10-15 20:21           ` Donald Parsons
2015-10-16  0:03             ` Brown, Len
2015-10-15  3:45       ` Re[4]: " shrybman
2015-10-15 22:55         ` Brown, Len
2015-10-15 23:13           ` Re[6]: " shrybman
2015-10-16  1:06             ` Brown, Len
2015-10-16  2:03               ` shrybman
2020-03-22 23:42                 ` itpenguin [this message]
2015-10-15 23:19         ` Re[4]: " Brown, Len

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1584920578289-0.post@n7.nabble.com \
    --to=info@itpenguin.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox