From: Paul Gortmaker <paul.gortmaker@windriver•com>
To: Michael Holzheu <holzheu@linux•vnet.ibm.com>
Cc: linux-next@vger•kernel.org, schwidefsky@de•ibm.com
Subject: [next] new fail in linux-next s390 smp
Date: Fri, 26 Jun 2015 13:49:01 -0400 [thread overview]
Message-ID: <20150626174901.GB4633@windriver.com> (raw)
Seen in allnoconfig:
http://kisskb.ellerman.id.au/kisskb/buildresult/12450623/
arch/s390/kernel/setup.c: In function 'setup_arch':
arch/s390/kernel/setup.c:875:2: error: implicit declaration of function
'smp_save_dump_cpus'
make[2]: *** [arch/s390/kernel/setup.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [arch/s390/kernel] Error 2
make: *** [arch/s390] Error 2
make: *** Waiting for unfinished jobs....
1592a8e456436024b6c662f423ce672e672169bb is the first bad commit
commit 1592a8e456436024b6c662f423ce672e672169bb
Author: Michael Holzheu <holzheu@linux•vnet.ibm.com>
Date: Tue May 26 19:05:23 2015 +0200
s390/kdump: fix nosmt kernel parameter
It turned out that SIGP set-multi-threading can only be done once.
Therefore switching to a different MT level after switching to
sclp.mtid_prev in the dump case fails.
As a symptom specifying the "nosmt" parameter currently fails for
the kdump kernel and the kernel starts with multi-threading enabled.
So fix this and issue diag 308 subcode 1 call after collecting the
CPU states for the dump. Also enhance the diag308_reset() function
to
be usable also with enabled lowcore protection and prefix register
!= 0.
After the reset it is possible to switch the MT level again. We have
to do the reset very early in order not to kill the already
initialized
console. Therefore instead of kmalloc() the corresponding memblock
functions have to be used. To avoid copying the sclp cpu code into
sclp_early, we now use the simple sigp loop method for CPU
detection.
Signed-off-by: Michael Holzheu <holzheu@linux•vnet.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de•ibm.com>
:040000 040000 5430eab17daadf67943ab0b5d1979e88c9417e7b
4610519e89468a4c09080f463c31e51fbc2fb4f4 M arch
:040000 040000 46b9da2c2a089589353ad9a55358803989cd9eb7
100d2243c38ece214cffc72f296a8860cff1a0e5 M drivers
bisect run success
next reply other threads:[~2015-06-26 17:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-26 17:49 Paul Gortmaker [this message]
2015-06-29 9:09 ` [next] new fail in linux-next s390 smp Martin Schwidefsky
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=20150626174901.GB4633@windriver.com \
--to=paul.gortmaker@windriver$(echo .)com \
--cc=holzheu@linux$(echo .)vnet.ibm.com \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=schwidefsky@de$(echo .)ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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