-We always get "crashkernel reservation failed -memory is in use" with crashkernel=64M@16M or crashkernel=128M@16M on all of our x86 test hardware. Here 256M@128M seems to be the best fit based on empirical data.
Signed-off-by: Sweekar Pinto <[email protected]> --- testcases/kdump/lib/setup.sh | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/testcases/kdump/lib/setup.sh b/testcases/kdump/lib/setup.sh index 5bc54bb..3e53f1a 100755 --- a/testcases/kdump/lib/setup.sh +++ b/testcases/kdump/lib/setup.sh @@ -86,11 +86,11 @@ echo "Modify Boot Loader." if [ "${arch}" = "ppc64" ]; then args="crashkernel=256M@32M xmon=off" elif [ "${arch}" = "i686" ]; then - args="crashkernel=128M@16M nmi_watchdog=1" + args="crashkernel=256M@128M nmi_watchdog=1" elif [ "${arch}" = "ia64" ]; then args="crashkernel=512M@256M" else - args="crashkernel=128M@16M" + args="crashkernel=256M@128M" fi if [ -x "/sbin/grubby" ]; then -- 1.7.1 ------------------------------------------------------------------------------ Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk _______________________________________________ Ltp-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ltp-list
