From: Guenter Roeck <linux@roeck-us.net>
To: linux-kernel@vger.kernel.org
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: qemu:arm test failure due to commit 8053871d0f7f (smp: Fix smp_call_function_single_async() locking)
Date: Sat, 18 Apr 2015 16:40:50 -0700 [thread overview]
Message-ID: <20150418234050.GA5987@roeck-us.net> (raw)
In-Reply-To: <20150418232325.GA22411@roeck-us.net>
On Sat, Apr 18, 2015 at 04:23:25PM -0700, Guenter Roeck wrote:
> Hi all,
>
> my qemu test for arm:vexpress fails with the latest upstream kernel. It fails
> hard - I don't get any output from the console. Bisect points to commit
> 8053871d0f7f ("smp: Fix smp_call_function_single_async() locking").
> Reverting this commit fixes the problem.
>
Additional observation: The system boots if I add "-smp cpus=4" to the qemu
options. It does still hang, however, with "-smp cpus=2" and "-smp cpus=3".
Guenter
next prev parent reply other threads:[~2015-04-18 23:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-18 23:23 qemu:arm test failure due to commit 8053871d0f7f (smp: Fix smp_call_function_single_async() locking) Guenter Roeck
2015-04-18 23:40 ` Guenter Roeck [this message]
2015-04-19 0:04 ` Linus Torvalds
2015-04-19 0:36 ` Guenter Roeck
2015-04-19 1:56 ` Guenter Roeck
2015-04-19 3:39 ` Rabin Vincent
2015-04-19 4:03 ` Guenter Roeck
[not found] ` <CA+55aFw4FSja+VBuCYJ7wLXKVRQZ7w6vOUaUJ4B=FXyBmNkrUg@mail.gmail.com>
2015-04-19 8:56 ` Linus Torvalds
2015-04-19 9:31 ` Ingo Molnar
2015-04-19 14:08 ` Guenter Roeck
2015-04-19 18:01 ` Ingo Molnar
2015-04-19 20:34 ` Linus Torvalds
2015-04-20 5:39 ` Ingo Molnar
2015-04-20 12:17 ` Paul E. McKenney
2015-04-20 15:53 ` Linus Torvalds
2015-04-20 15:41 ` Rabin Vincent
2015-04-20 10:46 ` Geert Uytterhoeven
2015-04-20 10:46 ` Geert Uytterhoeven
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=20150418234050.GA5987@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--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.