Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1735735
| From | Michael Ellerman <mpe@ellerman.id.au> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [linux-next][DLPAR CPU][Oops] Bad kernel stack pointer |
| Date | 2017-09-20 13:50 +0200 |
| Message-ID | <urLFU-2u1-19@gated-at.bofh.it> (permalink) |
| References | <ur1a1-4VA-15@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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
Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread
Re: [linux-next][DLPAR CPU][Oops] Bad kernel stack pointer Michael Ellerman <mpe@ellerman.id.au> - 2017-09-20 13:50 +0200
Re: [linux-next][DLPAR CPU][Oops] Bad kernel stack pointer Abdul Haleem <abdhalee@linux.vnet.ibm.com> - 2017-09-22 12:00 +0200
Re: [linux-next][DLPAR CPU][Oops] Bad kernel stack pointer Michael Ellerman <mpe@ellerman.id.au> - 2017-09-22 14:30 +0200
Re: [linux-next][DLPAR CPU][Oops] Bad kernel stack pointer Abdul Haleem <abdhalee@linux.vnet.ibm.com> - 2017-09-22 14:40 +0200
csiph-web