[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wjOXE4cqFOdtSymYnMMayZq8Lv7qDy-6BzCs=2=8HcoBA@mail.gmail.com>
Date: Thu, 30 Jan 2020 10:07:40 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Jörg Otte <jrg.otte@...il.com>,
Ingo Molnar <mingo@...nel.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"the arch/x86 maintainers" <x86@...nel.org>
Subject: Re: 5.6-### doesn't boot
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,
Linus
Powered by blists - more mailing lists