Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756068AbcJ3MIx (ORCPT ); Sun, 30 Oct 2016 08:08:53 -0400 Received: from basicbox7.server-home.net ([195.137.212.29]:48254 "EHLO basicbox7.server-home.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753454AbcJ3MIt (ORCPT ); Sun, 30 Oct 2016 08:08:49 -0400 Subject: Re: 4.9-rc1 boot regression, ambiguous bisect result To: Dan Williams , Matt Fleming References: <20161020122931.GD19876@codeblueprint.co.uk> <20161021154129.GH27807@codeblueprint.co.uk> <20161021202022.GI27807@codeblueprint.co.uk> Cc: LKML , linux-efi@vger.kernel.org, Peter Jones , Ard Biesheuvel , Ingo Molnar From: Thorsten Leemhuis Message-ID: <4a73a7d8-599c-eb25-0f78-d921a16bb56f@leemhuis.info> Date: Sun, 30 Oct 2016 13:08:44 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1499 Lines: 33 JFYI: I added this report to the list of regressions for Linux 4.9. I'll watch this thread for further updates on this issue to document progress in my weekly reports. Please let me know via regressions@leemhuis.info in case the discussion moves to a different place (bugzilla or another mail thread for example). tia! Current status (afaics) in my report: This looks stuck. Or was is discussed (or even fixed) somewhere else? Ciao, Thorsten On 22.10.2016 01:20, Dan Williams wrote: > 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. > > http://news.gmane.org/find-root.php?message_id=CAPcyv4jkVcBwecxwt1P+p-fMSuen9B9xHEVf0BjM5uJZ4_jAdw%40mail.gmail.com > http://mid.gmane.org/CAPcyv4jkVcBwecxwt1P+p-fMSuen9B9xHEVf0BjM5uJZ4_jAdw%40mail.gmail.com >