Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1734904
| From | Abdul Haleem <abdhalee@linux.vnet.ibm.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [linux-next][DLPAR CPU][Oops] Bad kernel stack pointer |
| Date | 2017-09-19 15:40 +0200 |
| Message-ID | <urqUN-62D-1@gated-at.bofh.it> (permalink) |
| References | <ur1a1-4VA-15@gated-at.bofh.it> <ur3ES-6mo-13@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Mon, 2017-09-18 at 07:44 -0500, Rob Herring wrote: > On Mon, Sep 18, 2017 at 5:08 AM, Abdul Haleem > <abdhalee@linux.vnet.ibm.com> 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
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
Re: [linux-next][DLPAR CPU][Oops] Bad kernel stack pointer Rob Herring <robh@kernel.org> - 2017-09-18 14:50 +0200 Re: [linux-next][DLPAR CPU][Oops] Bad kernel stack pointer Abdul Haleem <abdhalee@linux.vnet.ibm.com> - 2017-09-19 15:40 +0200
csiph-web