From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx0a-001b2d01.pphosted.com (mx0a-001b2d01.pphosted.com [148.163.156.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 3xxP3z52TtzDq8f for ; Tue, 19 Sep 2017 23:34:22 +1000 (AEST) Received: from pps.filterd (m0098409.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.21/8.16.0.21) with SMTP id v8JDYEuG067074 for ; Tue, 19 Sep 2017 09:34:19 -0400 Received: from e13.ny.us.ibm.com (e13.ny.us.ibm.com [129.33.205.203]) by mx0a-001b2d01.pphosted.com with ESMTP id 2d300001bn-1 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NOT) for ; Tue, 19 Sep 2017 09:34:19 -0400 Received: from localhost by e13.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Tue, 19 Sep 2017 09:34:18 -0400 Subject: Re: [linux-next][DLPAR CPU][Oops] Bad kernel stack pointer From: Abdul Haleem To: Rob Herring Cc: Stephen Rothwell , linux-kernel , linux-next , Paul Mackerras , linuxppc-dev Date: Tue, 19 Sep 2017 19:04:09 +0530 In-Reply-To: References: <1505729319.6990.5.camel@abdul.in.ibm.com> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Message-Id: <1505828049.30180.3.camel@abdul.in.ibm.com> List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Mon, 2017-09-18 at 07:44 -0500, Rob Herring wrote: > On Mon, Sep 18, 2017 at 5:08 AM, Abdul Haleem > wrote: > > 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 > > I assume this is not something new to 9/15 -next nor only in -next > because you also reported that 4.13.0 broke. Can you provide some > details on what version worked? 4.12? [linux-next][DLPAR CPU][Oops] Bad kernel stack pointer [mainline][DLPAR][Oops] OF: ERROR: Bad of_node_put() on /cpus The above issues are not reproducible with 4.12.0 (mainline), it is broken with 4.13.0 and next. -- Regard's Abdul Haleem IBM Linux Technology Centre