Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751873AbdITLmZ (ORCPT ); Wed, 20 Sep 2017 07:42:25 -0400 Received: from ozlabs.org ([103.22.144.67]:55045 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751619AbdITLmY (ORCPT ); Wed, 20 Sep 2017 07:42:24 -0400 From: Michael Ellerman To: Abdul Haleem , linuxppc-dev Cc: linux-kernel , linux-next , Stephen Rothwell , Rob Herring , Paul Mackerras Subject: Re: [linux-next][DLPAR CPU][Oops] Bad kernel stack pointer In-Reply-To: <1505729319.6990.5.camel@abdul.in.ibm.com> References: <1505729319.6990.5.camel@abdul.in.ibm.com> User-Agent: Notmuch/0.21 (https://notmuchmail.org) Date: Wed, 20 Sep 2017 21:42:21 +1000 Message-ID: <878th9lhpe.fsf@concordia.ellerman.id.au> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 567 Lines: 27 Abdul Haleem 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