All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: Ingo Molnar <mingo@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	Mike Galbraith <efault@gmx.de>
Subject: Re: [GIT PULL] scheduler changes for v4.3
Date: Tue, 1 Sep 2015 09:08:56 +0200	[thread overview]
Message-ID: <20150901070856.GA430@x4> (raw)
In-Reply-To: <20150831172453.GA5429@gmail.com>

On 2015.08.31 at 19:24 +0200, Ingo Molnar wrote:
> Please pull the latest sched-core-for-linus git tree from:
> 
>    git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git sched-core-for-linus
> 
>    # HEAD: ff277d4250fe715b6666219b1a3423b863418794 sched/deadline: Fix comment in enqueue_task_dl()

Linus,

your merge (commit a1d8561172f369ba) breaks booting on my machine.

I wrote down the backtrace:

map_vsyscall
kvm_arch_hardware_setup
map_vsyscall
kvm_init
map_vsyscall
do_one_initcall
kernel_init_freeable
rest_init
kernel_init
ret_from_fork
rest_init

RIP: svm_hardware_setup

Reverting your merge resolution fixes the issue:

diff --git a/kernel/cpu.c b/kernel/cpu.c
index 82cf9dff4295..873aa0757b04 100644
--- a/kernel/cpu.c
+++ b/kernel/cpu.c
@@ -397,12 +397,11 @@ static int _cpu_down(unsigned int cpu, int tasks_frozen)
 	 * Prevent irq alloc/free while the dying cpu reorganizes the
 	 * interrupt affinities.
 	 */
-	irq_lock_sparse();
 
 	/*
 	 * So now all preempt/rcu users must observe !cpu_active().
 	 */
-	err = stop_machine(take_cpu_down, &tcd_param, cpumask_of(cpu));
+	err = __stop_machine(take_cpu_down, &tcd_param, cpumask_of(cpu));
 	if (err) {
 		/* CPU didn't die: tell everyone.  Can't complain. */
 		cpu_notify_nofail(CPU_DOWN_FAILED | mod, hcpu);

-- 
Markus

  reply	other threads:[~2015-09-01  7:15 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-31 17:24 [GIT PULL] scheduler changes for v4.3 Ingo Molnar
2015-09-01  7:08 ` Markus Trippelsdorf [this message]
2015-09-01  7:27   ` Ingo Molnar
2015-09-01  7:44     ` Markus Trippelsdorf
2015-09-01  8:38       ` Ingo Molnar
2015-09-01  8:44         ` Markus Trippelsdorf
2015-09-01  8:56           ` Ingo Molnar
2015-09-01 10:04             ` commit 3c2e7f7de3 (KVM use NPT page attributes) causes boot failures Markus Trippelsdorf
2015-09-01 13:00               ` Xiao Guangrong
2015-09-01 13:56                 ` Markus Trippelsdorf
2015-09-01 22:31                   ` Xiao Guangrong
2015-09-02  3:50                     ` Markus Trippelsdorf
2015-09-02  9:17                       ` Xiao Guangrong
2015-09-02  9:38                         ` Markus Trippelsdorf
2015-09-02 10:27                           ` Xiao Guangrong
2015-09-02 10:54                             ` Markus Trippelsdorf
2015-09-02 10:57                               ` Xiao Guangrong
2015-09-01  8:50         ` [GIT PULL] scheduler changes for v4.3 Markus Trippelsdorf
2015-09-01  8:18     ` Markus Trippelsdorf
2015-09-01  8:39       ` Markus Trippelsdorf

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=20150901070856.GA430@x4 \
    --to=markus@trippelsdorf.de \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=efault@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.