Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S936498AbcJUXUv (ORCPT ); Fri, 21 Oct 2016 19:20:51 -0400 Received: from mail-it0-f48.google.com ([209.85.214.48]:37651 "EHLO mail-it0-f48.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S935590AbcJUXUr (ORCPT ); Fri, 21 Oct 2016 19:20:47 -0400 MIME-Version: 1.0 In-Reply-To: <20161021202022.GI27807@codeblueprint.co.uk> References: <20161020122931.GD19876@codeblueprint.co.uk> <20161021154129.GH27807@codeblueprint.co.uk> <20161021202022.GI27807@codeblueprint.co.uk> From: Dan Williams Date: Fri, 21 Oct 2016 16:20:45 -0700 Message-ID: Subject: Re: 4.9-rc1 boot regression, ambiguous bisect result To: Matt Fleming Cc: LKML , linux-efi@vger.kernel.org, Peter Jones , Ard Biesheuvel , Ingo Molnar Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 775 Lines: 17 On Fri, Oct 21, 2016 at 1:20 PM, Matt Fleming wrote: > 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 I can take a look, but it will not be until Monday when I have physical access to the system again.