Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From:   Andy Lutomirski <luto@amacapital.net>
Mime-Version: 1.0 (1.0)
Subject: Re: 5.6-### doesn't boot
Date:   Thu, 30 Jan 2020 10:22:51 -0800
Message-Id: <8E4D91A4-8A35-481D-B5F6-4779FBDE3876@amacapital.net>
References: <CAHk-=wjOXE4cqFOdtSymYnMMayZq8Lv7qDy-6BzCs=2=8HcoBA@mail.gmail.com>
Cc:     =?utf-8?Q?J=C3=B6rg_Otte?= <jrg.otte@gmail.com>,
        Ingo Molnar <mingo@kernel.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        the arch/x86 maintainers <x86@kernel.org>
In-Reply-To: <CAHk-=wjOXE4cqFOdtSymYnMMayZq8Lv7qDy-6BzCs=2=8HcoBA@mail.gmail.com>
To:     Linus Torvalds <torvalds@linux-foundation.org>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk


> On Jan 30, 2020, at 10:08 AM, Linus Torvalds <torvalds@linux-foundation.or=
g> wrote:
>=20
> =EF=BB=BFOn Thu, Jan 30, 2020 at 9:32 AM J=C3=B6rg Otte <jrg.otte@gmail.co=
m> wrote:
>>=20
>> 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.
>>=20
>> last known good kernel is : vmlinuz-5.5.0-00849-gb0be0eff1a5a
>> first known bad kernel is : vmlinuz-5.5.0-01154-gc677124e631d
>=20
> It would be lovely if you can bisect a bit. But my merges in that
> range are all from Ingo:
>=20
> Ingo Molnar (7):
>    header cleanup
>    objtool updates
>    RCU updates
>    EFI updates
>    locking updates
>    perf updates
>    scheduler updates
>=20
> but not having any messages at all makes it hard to guess where it would b=
e.
>=20
> A few bisect runs would narrow it down a fair amount. Bisecting all
> the way would be even better, of course,
>=20
>=20

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 3=
2-bit EFI?)=