Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S936362AbcJUUUl (ORCPT ); Fri, 21 Oct 2016 16:20:41 -0400 Received: from mail-wm0-f50.google.com ([74.125.82.50]:37603 "EHLO mail-wm0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S936286AbcJUUUj (ORCPT ); Fri, 21 Oct 2016 16:20:39 -0400 Date: Fri, 21 Oct 2016 21:20:36 +0100 From: Matt Fleming To: Dan Williams Cc: LKML , linux-efi@vger.kernel.org, Peter Jones , Ard Biesheuvel , Ingo Molnar Subject: Re: 4.9-rc1 boot regression, ambiguous bisect result Message-ID: <20161021202022.GI27807@codeblueprint.co.uk> References: <20161020122931.GD19876@codeblueprint.co.uk> <20161021154129.GH27807@codeblueprint.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20161021154129.GH27807@codeblueprint.co.uk> User-Agent: Mutt/1.5.24+41 (02bc14ed1569) (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 576 Lines: 13 On Fri, 21 Oct, at 04:41:29PM, Matt Fleming wrote: > > FYI, I've been able to reproduce some crash when using your EFI memory > map layout under Qemu and forcing the ESRT driver to reserve the space. Nope, that was a bug in my hack. I can't get Qemu to crash while using your memory map layout. Any chance you can insert "while(1)" loops into the EFI boot paths for a kernel that is known to reboot or trigger a triple fault in kernels that hang, so that we can narrow in on the issue. See, http://www.codeblueprint.co.uk/2015/04/early-x86-linux-boot-debug-tricks.html