<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 11/05/2015 07:02 AM, David Gibson
wrote:<br>
</div>
<blockquote cite="mid:20151105123243.47dda843@voom.fritz.box"
type="cite">
<pre wrap="">On Wed, 4 Nov 2015 14:54:51 +0100
Laurent Vivier <a class="moz-txt-link-rfc2396E" href="mailto:lvivier@redhat.com"><lvivier@redhat.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">
On 04/11/2015 13:34, Hari Bathini wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On 10/16/2015 12:30 AM, Laurent Vivier wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On kexec, all secondary offline CPUs are onlined before
starting the new kernel, this is not done in the case of kdump.
If kdump is configured and a kernel crash occurs whereas
some secondaries CPUs are offline (SMT=off),
the new kernel is not able to start them and displays some
"Processor X is stuck.".
Starting with POWER8, subcore logic relies on all threads of
core being booted. So, on startup kernel tries to start all
threads, and asks OPAL (or RTAS) to start all CPUs (including
threads). If a CPU has been offlined by the previous kernel,
it has not been returned to OPAL, and thus OPAL cannot restart
it: this CPU has been lost...
Signed-off-by: Laurent Vivier<a class="moz-txt-link-rfc2396E" href="mailto:lvivier@redhat.com"><lvivier@redhat.com></a>
</pre>
</blockquote>
<pre wrap="">
Hi Laurent,
</pre>
</blockquote>
<pre wrap="">
Hi Hari,
</pre>
<blockquote type="cite">
<pre wrap="">Sorry for jumping too late into this.
</pre>
</blockquote>
<pre wrap="">
better late than never :)
</pre>
<blockquote type="cite">
<pre wrap="">Are you seeing this issue even with the below patches:
pseries:
<a class="moz-txt-link-freetext" href="http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=c1caae3de46a072d0855729aed6e793e536a4a55">http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=c1caae3de46a072d0855729aed6e793e536a4a55</a>
</pre>
</blockquote>
</blockquote>
<pre wrap="">
Unfortunately, this is unlikely to be relevant - this fixes a failure
while setting up the kexec. The problem we see occurs once we've
booted the second kernel and it's attempting to bring up secondary CPUs.
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">opal/powernv:
<a class="moz-txt-link-freetext" href="https://github.com/open-power/skiboot/commit/9ee56b5">https://github.com/open-power/skiboot/commit/9ee56b5</a>
</pre>
</blockquote>
<pre wrap="">
Very interesting. Is there a way to have a firmware with the fix ?
</pre>
</blockquote>
<pre wrap="">
>From Laurent's analysis of the crash, I don't think this will be</pre>
</blockquote>
<br>
<br>
<blockquote cite="mid:20151105123243.47dda843@voom.fritz.box"
type="cite">
<pre wrap="">
relevant either, but I'm not sure. It would be very interesting to
know which (if any) released firmwares include this patch so we can
test it.
</pre>
</blockquote>
<br>
Hi Laurent/David,<br>
<br>
I am not so sure on this. While I get back on this, can you confirm
you are<br>
seeing the issue in both PowerVM (pseries) and baremetal (powernv).
What is<br>
the kernel version where the issue is seen for PowerVM and/or
baremetal.<br>
Also, for baremetal, can you mention the OPAL version on which the
issue is<br>
reproducible. If a bug is raised for this, I would be happy to be
pointed to,<br>
to get more information on this.<br>
<br>
Thanks<br>
Hari<br>
<br>
<blockquote cite="mid:20151105123243.47dda843@voom.fritz.box"
type="cite">
<pre wrap="">
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Linuxppc-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Linuxppc-dev@lists.ozlabs.org">Linuxppc-dev@lists.ozlabs.org</a>
<a class="moz-txt-link-freetext" href="https://lists.ozlabs.org/listinfo/linuxppc-dev">https://lists.ozlabs.org/listinfo/linuxppc-dev</a></pre>
</blockquote>
<br>
</body>
</html>