File kdump-kernel-cmdline-filter-notsc.patch of Package kdump

Overview Repositories Revisions Requests Users Attributes Meta

File kdump-kernel-cmdline-filter-notsc.patch of Package kdump (Revision b506a210e4023d5b2e55f9119b1eb136)

Currently displaying revision b506a210e4023d5b2e55f9119b1eb136 , Show latest

From: Jiri Bohac <jbohac@suse.com>
Subject: Remove 'notsc' from the kdump kernel command line
References: bsc#973213
Patch-mainline: v0.8.16
Git-commit: 558eb61b05a7c9557359575b91a78eebfa1b90a9

The kdump kernel boots on the crashed CPU, which may not be the BSP.
Boot may then fail, because the early code switches to legacy interrupt
delivery, which may fail on AP for many reasons. See also
http://thread.gmane.org/gmane.linux.kernel/607252

I don't see any reason to disable TSC in the kdump kernel. People may
want to disable TSC because in some cases it can cause time to be
unreliable. This should be really rare with a single CPU boot and more
importantly, we don't care in the kdump environment.

Signed-off-by: Jiri Bohac <jbohac@suse.com>
Acked-by: Petr Tesarik <ptesarik@suse.com>

---
 init/load.sh |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- a/init/load.sh
+++ b/init/load.sh
@@ -80,7 +80,7 @@ function build_kdump_commandline()
             test -n "$boot_apicid" && \
 		commandline="$commandline disable_cpu_apicid=$boot_apicid"
             commandline=$(echo "$commandline" |
-                remove_from_commandline 'unknown_nmi_panic')
+                remove_from_commandline 'unknown_nmi_panic|notsc')
             ;;
 	s390*)
 	    commandline="$commandline zfcp.allow_lun_scan=0"

Places

File kdump-kernel-cmdline-filter-notsc.patch of Package kdump (Revision b506a210e4023d5b2e55f9119b1eb136)

Places