[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPcyv4jkVcBwecxwt1P+p-fMSuen9B9xHEVf0BjM5uJZ4_jAdw@mail.gmail.com>
Date: Fri, 21 Oct 2016 16:20:45 -0700
From: Dan Williams <dan.j.williams@...el.com>
To: Matt Fleming <matt@...eblueprint.co.uk>
Cc: LKML <linux-kernel@...r.kernel.org>, linux-efi@...r.kernel.org,
Peter Jones <pjones@...hat.com>,
Ard Biesheuvel <ard.biesheuvel@...aro.org>,
Ingo Molnar <mingo@...nel.org>
Subject: Re: 4.9-rc1 boot regression, ambiguous bisect result
On Fri, Oct 21, 2016 at 1:20 PM, Matt Fleming <matt@...eblueprint.co.uk> 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.
Powered by blists - more mailing lists