ISST-LTE: pVM:high cpus number need a high crashkernel value in kdump
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
High
|
Tim Gardner | ||
Xenial |
Fix Released
|
High
|
Tim Gardner |
Bug Description
The kdump kernel will be booted with "maxcpus=1", so no matter how many cpus this system has, only one cpu will be brought up during kdump I think. But on LPAR thymelp2, if we allocate 40 cpus on it, then kdump works just fine with 512M as crashkernel value. But if we allocate 200 cpus on it, kdump fails by trggering OOM. It has been proved that in latter situation we need 1.5G RAM reserved for kdump to let it works.
Contact Information = Ping Tian <email address hidden> Carrie <email address hidden>
---uname output---
Linux thymelp2 4.2.0-23-generic #28~14.04.1-Ubuntu SMP Thu Dec 31 13:41:19 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux
Machine Type = 8247-22L, LPAR
---Debugger---
A debugger was configured, however the system did not enter into the debugger
---Steps to Reproduce---
1. configure kdump with crashkernel=512M on thymelp2
2. allcoate 40 cpus on thymelp2 and trigger kdump
3. allocate 200 cpus on thymelp2 then do kdump again
*Additional Instructions for Ping Tian <email address hidden> Carrie <email address hidden>:
-Post a private note with access information to the machine that the bug is occuring on.
== Comment: #1 - Nadia N. Fry <email address hidden> - 2016-02-19 13:53:02 ==
Any update?
== Comment: #2 - Hari Krishna Bathini <email address hidden> - 2016-02-22 03:40:05 ==
Mahesh posted a patch upstream which should take care of this problem
http://
Thanks
Hari
tags: | added: architecture-ppc64le bugnameltc-137281 severity-high targetmilestone-inin--- |
Changed in ubuntu: | |
assignee: | nobody → Taco Screen team (taco-screen-team) |
affects: | ubuntu → linux (Ubuntu) |
Changed in linux (Ubuntu): | |
assignee: | Taco Screen team (taco-screen-team) → Canonical Kernel Team (canonical-kernel-team) |
importance: | Undecided → High |
status: | New → Triaged |
Changed in linux (Ubuntu Xenial): | |
assignee: | Canonical Kernel Team (canonical-kernel-team) → Tim Gardner (timg-tpi) |
status: | Triaged → Fix Committed |
tags: |
added: targetmilestone-inin16041 removed: targetmilestone-inin--- |
tags: | added: cscc |
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.
To change the source package that this bug is filed about visit https:/ /bugs.launchpad .net/ubuntu/ +bug/1560552/ +editstatus and add the package name in the text box next to the word Package.
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]