From: Matt Fleming <matt@codeblueprint.co.uk>
To: Dan Williams <dan.j.williams@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-efi@vger.kernel.org, Peter Jones <pjones@redhat.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: 4.9-rc1 boot regression, ambiguous bisect result
Date: Fri, 21 Oct 2016 21:20:36 +0100 [thread overview]
Message-ID: <20161021202022.GI27807@codeblueprint.co.uk> (raw)
In-Reply-To: <20161021154129.GH27807@codeblueprint.co.uk>
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
next prev parent reply other threads:[~2016-10-21 20:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-20 4:04 4.9-rc1 boot regression, ambiguous bisect result Dan Williams
2016-10-20 6:24 ` Ingo Molnar
2016-10-20 12:29 ` Matt Fleming
2016-10-20 15:22 ` Dan Williams
2016-10-20 19:37 ` Dan Williams
2016-10-21 7:00 ` Ingo Molnar
2016-10-21 18:20 ` Dan Williams
2016-10-21 15:41 ` Matt Fleming
2016-10-21 20:20 ` Matt Fleming [this message]
2016-10-21 23:20 ` Dan Williams
2016-10-30 12:08 ` Thorsten Leemhuis
2016-10-30 15:59 ` Dan Williams
2016-10-31 9:38 ` Matt Fleming
2016-11-03 0:41 ` Neri, Ricardo
2016-11-03 5:18 ` Dan Williams
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161021202022.GI27807@codeblueprint.co.uk \
--to=matt@codeblueprint.co.uk \
--cc=ard.biesheuvel@linaro.org \
--cc=dan.j.williams@intel.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=pjones@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).