From: Giovanni Gherdovich <ggherdovich@suse.cz>
To: Rui Salvaterra <rsalvaterra@gmail.com>, x86@kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BISECTED] bug/regression, x86-64: completely unbootable machine
Date: Fri, 24 Apr 2020 10:10:59 +0200 [thread overview]
Message-ID: <1587715859.28179.17.camel@suse.cz> (raw)
In-Reply-To: <CALjTZvaiCzPQT6Jrx4pFW6KuZj2WLSQQpCbU-sg1jEgscQAKFQ@mail.gmail.com>
On Fri, 2020-04-24 at 09:00 +0100, Rui Salvaterra wrote:
> Hi, everyone,
>
> Starting with Linux 5.7-rc1, my Arrandale (Core i3-380M) laptop is
> completely unbootable (the last messages on screen are GRUB's loading
> kernel/initramfs). I was hoping someone would have noticed it before
> 5.7-rc2 had been tagged, but alas. Anyway, I bisected it down to
> commit 1567c3e3467cddeb019a7b53ec632f834b6a9239 (x86, sched: Add
> support for frequency invariance). After reverting it, the machine
> boots again, obviously.
>
> Let me know if you need any further info in order to fix this issue.
>
> Complete bisection log follows.
> [...]
Hello Rui,
thanks for the report.
The problem you encountered is due to a bug where the code doesn't work on
machines with less than 4 physical CPU cores. It is fixed by this patch
series:
https://lore.kernel.org/lkml/20200416054745.740-1-ggherdovich@suse.cz/
The series has been merged in the branch sched/urgent of the "tip" tree
(https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git), the commit
fixing the bug you observed is 23ccee22e834 (x86, sched: Account for CPUs
with less than 4 cores in freq. invariance), and will be merged in Linus'
tree at some point.
Thanks,
Giovanni Gherdovich
next prev parent reply other threads:[~2020-04-24 8:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 8:00 Rui Salvaterra
2020-04-24 8:10 ` Giovanni Gherdovich [this message]
2020-04-24 8:21 ` Rui Salvaterra
2020-04-24 17:39 ` Rui Salvaterra
2020-04-25 16:01 ` Giovanni Gherdovich
2020-04-28 7:27 ` Rui Salvaterra
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=1587715859.28179.17.camel@suse.cz \
--to=ggherdovich@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=rsalvaterra@gmail.com \
--cc=x86@kernel.org \
/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
all inboxes | Powered by JetHome®