public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman•id.au>
To: Abdul Haleem <abdhalee@linux•vnet.ibm.com>,
	linuxppc-dev <linuxppc-dev@lists•ozlabs.org>
Cc: 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: [DLPAR CPU][Oops] Bad kernel stack pointer
Date: Wed, 20 Sep 2017 21:42:21 +1000	[thread overview]
Message-ID: <878th9lhpe.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <1505729319.6990.5.camel@abdul.in.ibm.com>

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.

Is this easily reproducible?

cheers

  parent reply	other threads:[~2017-09-20 11:42 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 ` [DLPAR " Rob Herring
2017-09-19 13:34   ` Abdul Haleem
2017-09-20 11:42 ` Michael Ellerman [this message]
2017-09-22  9:57   ` Abdul Haleem
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=878th9lhpe.fsf@concordia.ellerman.id.au \
    --to=mpe@ellerman$(echo .)id.au \
    --cc=abdhalee@linux$(echo .)vnet.ibm.com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=linuxppc-dev@lists$(echo .)ozlabs.org \
    --cc=paulus@samba$(echo .)org \
    --cc=robh@kernel$(echo .)org \
    --cc=sfr@canb$(echo .)auug.org.au \
    /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