Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754456Ab0LFW23 (ORCPT ); Mon, 6 Dec 2010 17:28:29 -0500 Received: from relay1.sgi.com ([192.48.179.29]:46795 "EHLO relay.sgi.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753796Ab0LFW22 (ORCPT ); Mon, 6 Dec 2010 17:28:28 -0500 To: linux-kernel@vger.kernel.org Subject: [PATCH] x86: UV kdump reboot fix Cc: mingo@elte.hu Message-Id: From: Cliff Wickman Date: Mon, 06 Dec 2010 16:28:38 -0600 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1460 Lines: 53 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 --- 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 #include #include +#include #include #include #include @@ -22,6 +23,7 @@ #include #include #include +#include #ifdef CONFIG_X86_32 # include @@ -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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/