From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752696Ab2LWVAG (ORCPT ); Sun, 23 Dec 2012 16:00:06 -0500 Received: from mail-da0-f44.google.com ([209.85.210.44]:53221 "EHLO mail-da0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752628Ab2LWVAD (ORCPT ); Sun, 23 Dec 2012 16:00:03 -0500 Date: Sun, 23 Dec 2012 12:59:50 -0800 From: Jonathan Nieder To: stable@vger.kernel.org Cc: Matthew Garrett , x86@kernel.org, hpa@zytor.com, linux-kernel@vger.kernel.org, Keith Ward , Ben Hutchings Subject: [2.6.32.y, 2.6.34.y] Re: [PATCH] x86: Don't use the EFI reboot method by default Message-ID: <20121223205950.GA16511@elie.Belkin> References: <1309985557-15350-1-git-send-email-mjg@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1309985557-15350-1-git-send-email-mjg@redhat.com> User-Agent: Mutt/1.5.21+51 (9e756d1adb76) (2011-07-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Willy et al, Please consider f70e957cda22 x86: Don't use the EFI reboot method by default, 2011-07-06 for application to the 2.6.32.y and 2.6.34.y trees. The patch was applied upstream late in the 3.0 cycle, so newer kernels don't need it. In 2011, Keith Ward wrote[1]: > When attempting to reboot my my UEFI enabled system, the system hangs when > calling reboot requiring me to manually reset the system via the reset switch. > > Screenshot: http://twitgoo.com/29bq1c Ben Hutchings writes[1]: > Version: 3.0.0-1 > > I also had this problem on my own system, but it is fixed now. > I bisected the fix to: > > commit f70e957cda22d309c769805cbb932407a5232219 > Author: Matthew Garrett > Date: Wed Jul 6 16:52:37 2011 -0400 > > x86: Don't use the EFI reboot method by default > > which is basically equivalent to the workaround! > > I'll also apply this fix to squeeze as it's so simple. Keith Ward also wrote[1]: > It seems as if this has recently been reported at Ubuntu's Launchpad as well: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/721576 There are a variety of reports of the same panic at that bug on 2.6.32.y-, 2.6.38.y-, and 2.6.39-based kernels. Passing "reboot=a,w" on the kernel command line avoids trouble for reporters. Regards, Jonathan [1] http://bugs.debian.org/626022