From: Abdul Haleem <abdhalee@linux.vnet.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-next <linux-next@vger.kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Rob Herring <robh@kernel.org>, Paul Mackerras <paulus@samba.org>
Subject: Re: [linux-next][DLPAR CPU][Oops] Bad kernel stack pointer
Date: Fri, 22 Sep 2017 15:27:04 +0530 [thread overview]
Message-ID: <1506074224.17232.8.camel@abdul.in.ibm.com> (raw)
In-Reply-To: <878th9lhpe.fsf@concordia.ellerman.id.au>
On Wed, 2017-09-20 at 21:42 +1000, Michael Ellerman wrote:
> Abdul Haleem <abdhalee@linux.vnet.ibm.com> writes:
>
> > Hi,
> >
> > Dynamic CPU remove operation resulted in Kernel Panic on today's
> > next-20170915 kernel.
> >
> > Machine Type: Power 7 PowerVM LPAR
> > Kernel : 4.13.0-next-20170915
> > config : attached
> > test: DLPAR CPU remove
> >
> >
> > dmesg logs:
> > ----------
> > cpu 37 (hwid 37) Ready to die...
> > cpu 38 (hwid 38) Ready to die...
> > cpu 39 (hwid 39)
> > ******* RTAS CReady to die...
> > ALL BUFFER CORRUPTION *******
>
> Cool. Does that come from RTAS itself? I have never seen that happen
> before.
Not sure, the var logs does not have any messages captured. This is
first time we hit this type of issue.
>
> Is this easily reproducible?
I am unable to reproduce it again. I will keep an eye on our CI runs for
few more runs.
--
Regard's
Abdul Haleem
IBM Linux Technology Centre
next prev parent reply other threads:[~2017-09-22 9:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-18 10:08 [linux-next][DLPAR CPU][Oops] Bad kernel stack pointer Abdul Haleem
2017-09-18 12:44 ` Rob Herring
2017-09-19 13:34 ` Abdul Haleem
2017-09-20 11:42 ` Michael Ellerman
2017-09-22 9:57 ` Abdul Haleem [this message]
2017-09-22 12:26 ` Michael Ellerman
2017-09-22 12:38 ` Abdul Haleem
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=1506074224.17232.8.camel@abdul.in.ibm.com \
--to=abdhalee@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=robh@kernel.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).