diff options
| author | Sweekar Pinto <sweekar.pinto@oracle.com> | 2014-02-20 19:05:53 -0500 |
|---|---|---|
| committer | Cyril Hrubis <chrubis@suse.cz> | 2014-02-25 17:03:32 +0100 |
| commit | 4ce95c6aaa87a678822cfda27946e151bc87f73b (patch) | |
| tree | 7be5af1a32234af3e1419028293aaadd7f36cec2 /testcases/kdump | |
| parent | 9f5316b6329b3f671a8650721daa0659660a57c0 (diff) | |
Change crashkernel param to 256M@128M
-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 <sweekar.pinto@oracle.com>
Diffstat (limited to 'testcases/kdump')
| -rwxr-xr-x | 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 5bc54bb6d..3e53f1aec 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 |