[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ec95d575-070f-4c62-8b27-3ce281cb192e@email.android.com>
Date: Sat, 01 Mar 2014 12:26:40 -0800
From: "H. Peter Anvin" <hpa@...or.com>
To: Matthew Garrett <mjg59@...f.ucam.org>
CC: "Li, Aubrey" <aubrey.li@...ux.intel.com>,
"H. Peter Anvin" <hpa@...ux.intel.com>,
"alan@...ux.intel.com" <alan@...ux.intel.com>,
linux-kernel@...r.kernel.org, Len.Brown@...el.com,
Adam Williamson <awilliam@...hat.com>
Subject: Re: [patch] x86: Introduce BOOT_EFI and BOOT_CF9 into the reboot sequence loop
True... trying cf9_cond with low priority probably makes sense.
On March 1, 2014 12:21:39 PM PST, Matthew Garrett <mjg59@...f.ucam.org> wrote:
>On Sat, Mar 01, 2014 at 12:06:39PM -0800, H. Peter Anvin wrote:
>
>> Be careful. This is *exactly* what I tried back in checkin
>> 14d7ca5c575853664d8fe4f225a77b8df1b7de7d. We had to back that out
>quite
>> quickly.
>
>It's the difference between trying it before the keyboard controller
>and
>trying it after the keyboard controller and ACPI. It seems that it
>broke
>some systems where the keyboard controller worked - if we've hit the
>keyboard controller and ACPI twice, and the system is still alive, and
>if we have standard PCI ports, it doesn't seem like poking them is
>likely to make anything actively worse.
--
Sent from my mobile phone. Please pardon brevity and lack of formatting.
--
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/
Powered by blists - more mailing lists