public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Matt Fleming <matt@codeblueprint.co.uk>
Cc: kernel test robot <ying.huang@linux.intel.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	lkp@01.org, LKML <linux-kernel@vger.kernel.org>,
	Andy Lutomirski <luto@amacapital.net>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>, Borislav Petkov <bp@alien8.de>,
	Laszlo Ersek <lersek@redhat.com>
Subject: Re: [lkp] [x86/setup] f5f3497cad: BUG: kernel boot crashed
Date: Tue, 3 Nov 2015 09:07:34 +0100	[thread overview]
Message-ID: <20151103080734.GA20008@gmail.com> (raw)
In-Reply-To: <20151102162551.GB2331@codeblueprint.co.uk>


* Matt Fleming <matt@codeblueprint.co.uk> wrote:

> On Wed, 28 Oct, at 01:41:51PM, kernel test robot wrote:
> > FYI, we noticed the below changes on
> > 
> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> > commit f5f3497cad8c8416a74b9aaceb127908755d020a ("x86/setup: Extend low identity map to cover whole kernel range")
> > 
> > 
> > +------------------------------------------------+------------+------------+
> > |                                                | 8a53554e12 | f5f3497cad |
> > +------------------------------------------------+------------+------------+
> > | boot_successes                                 | 19         | 10         |
> > | boot_failures                                  | 2          | 9          |
> > | IP-Config:Auto-configuration_of_network_failed | 2          | 2          |
> > | BUG:kernel_boot_crashed                        | 0          | 7          |
> > +------------------------------------------------+------------+------------+
> > 
> > 
> > [    0.053410] smpboot: CPU0: GenuineIntel GenuineIntel QEMU Virtual CPU version 2.4.0QEMU Virtual CPU version 2.4.0 (family: 0x6, model: 0x6 (family: 0x6, model: 0x6, stepping: 0x3)
> > , stepping: 0x3)
> > [    0.056666] Performance Events: 
> > [    0.056666] Performance Events: no PMU driver, software events only.
> > no PMU driver, software events only.
> > [    0.060520] CPU 1 irqstacks, hard=8a832000 soft=8a834000
> > [    0.060520] CPU 1 irqstacks, hard=8a832000 soft=8a834000
> > [    0.061605] x86: Booting SMP configuration:
> > [    0.061605] x86: Booting SMP configuration:
> > [    0.062445] .... node  #0, CPUs:  
> > [    0.062445] .... node  #0, CPUs:         #1 #1
> > Elapsed time: 10
> > BUG: kernel boot crashed
> 
> Yikes! Yeah, I can reproduce this. It appears the STARTUP IPI code is
> triggering this crash in wakeup_secondary_cpu_via_init().
> 
> I'll take a look unless anyone else has any bright ideas?

Unfortunately this commit is now part of the v4.3 kernel, so we need a quick 
solution or a quick revert.

Thanks,

	Ingo

  reply	other threads:[~2015-11-03  8:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-28  5:41 [lkp] [x86/setup] f5f3497cad: BUG: kernel boot crashed kernel test robot
2015-11-02 16:28 ` Matt Fleming
2015-11-03  8:07   ` Ingo Molnar [this message]
2015-11-03 14:06     ` Matt Fleming
2015-11-04 10:51       ` [tip:x86/urgent] x86/setup: Fix recent boot crash on 32-bit SMP machines tip-bot for Matt Fleming

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=20151103080734.GA20008@gmail.com \
    --to=mingo@kernel.org \
    --cc=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=lersek@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=luto@amacapital.net \
    --cc=matt@codeblueprint.co.uk \
    --cc=pbonzini@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=ying.huang@linux.intel.com \
    /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