Public bug reported: ---Problem 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. ---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 --- Mahesh has posted a patch upstream to provide support for nr_cpus in kdump kernel. That should take care of this problem..
https://lists.ozlabs.org/pipermail/linuxppc-dev/2016-February/138619.html --- Heads up Canonical: We'll want this patch included as soon possible/practical. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Taco Screen team (taco-screen-team) Status: New ** Tags: architecture-ppc64le bugnameltc-134503 severity-high targetmilestone-inin--- ** Tags added: architecture-ppc64le bugnameltc-134503 severity-high targetmilestone-inin--- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1546159 Title: ISST-LTE: high cpus number need a high crashkernel value in kdump To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1546159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
