linux-kernel - Re: 5.6-### doesn't boot

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: <8E4D91A4-8A35-481D-B5F6-4779FBDE3876@amacapital.net>
Date:   Thu, 30 Jan 2020 10:22:51 -0800
From:   Andy Lutomirski <luto@...capital.net>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     Jörg Otte <jrg.otte@...il.com>,
        Ingo Molnar <mingo@...nel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        the arch/x86 maintainers <x86@...nel.org>
Subject: Re: 5.6-### doesn't boot



> On Jan 30, 2020, at 10:08 AM, Linus Torvalds <torvalds@...ux-foundation.org> wrote:
> 
> On Thu, Jan 30, 2020 at 9:32 AM Jörg Otte <jrg.otte@...il.com> wrote:
>> 
>> my notebook doesn't boot with current kernel. Booting stops right after
>> displaying "loading initial ramdisk..". No further displays.
>> Also nothing is wriiten to the logs.
>> 
>> last known good kernel is : vmlinuz-5.5.0-00849-gb0be0eff1a5a
>> first known bad kernel is : vmlinuz-5.5.0-01154-gc677124e631d
> 
> It would be lovely if you can bisect a bit. But my merges in that
> range are all from Ingo:
> 
> Ingo Molnar (7):
>    header cleanup
>    objtool updates
>    RCU updates
>    EFI updates
>    locking updates
>    perf updates
>    scheduler updates
> 
> but not having any messages at all makes it hard to guess where it would be.
> 
> A few bisect runs would narrow it down a fair amount. Bisecting all
> the way would be even better, of course,
> 
> 

It would also be nice to know: are you EFI-booting or BIOS-booting?  And are you using EFI mixed mode?  (That is, are you booting a 64-bit kernel using 32-bit EFI?)