linux-kernel - [PATCH] x86: UV kdump reboot fix

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <E1PPjXy-0004Cs-5F@eag09.americas.sgi.com>
Date:	Mon, 06 Dec 2010 16:28:38 -0600
From:	Cliff Wickman <cpw@....com>
To:	linux-kernel@...r.kernel.org
Cc:	mingo@...e.hu
Subject: [PATCH] x86: UV kdump reboot fix


After a crash dump on an SGI Altix UV system the crash kernel fails to
cause a reboot.
Only the reboot_type of BOOT_ACPI works.
Other boot types ...BOOT_EFI, _KBD, _TRIPLE... fail.

The system's BIOS has an EFI layer, so it is a bit of a mystery to me
why BOOT_EFI fails.  Can someone explain that?

Diffed against 2.6.37-rc2

Signed-off-by: Cliff Wickman <cpw@....com>

---
 arch/x86/kernel/reboot.c |    6 ++++++
 1 file changed, 6 insertions(+)

Index: linux/arch/x86/kernel/reboot.c
===================================================================
--- linux.orig/arch/x86/kernel/reboot.c
+++ linux/arch/x86/kernel/reboot.c
@@ -10,6 +10,7 @@
 #include <linux/dmi.h>
 #include <linux/sched.h>
 #include <linux/tboot.h>
+#include <linux/crash_dump.h>
 #include <acpi/reboot.h>
 #include <asm/io.h>
 #include <asm/apic.h>
@@ -22,6 +23,7 @@
 #include <asm/pci_x86.h>
 #include <asm/virtext.h>
 #include <asm/cpu.h>
+#include <asm/uv/uv.h>
 
 #ifdef CONFIG_X86_32
 # include <linux/ctype.h>
@@ -675,6 +677,10 @@ static void native_machine_restart(char 
 
 	if (!reboot_force)
 		machine_shutdown();
+
+	if (is_uv_system() && is_kdump_kernel())
+		reboot_type = BOOT_ACPI;
+
 	__machine_emergency_restart(0);
 }
 
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/