linux-kernel - Re: 4.9-rc1 boot regression, ambiguous bisect result

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4a73a7d8-599c-eb25-0f78-d921a16bb56f@leemhuis.info>
Date:   Sun, 30 Oct 2016 13:08:44 +0100
From:   Thorsten Leemhuis <regressions@...mhuis.info>
To:     Dan Williams <dan.j.williams@...el.com>,
        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

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@...mhuis.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 <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.
> 
> 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
>