Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Message-ID: <1587372294.26844.24.camel@suse.cz>
Subject: Re: [Bisected] Oops witn 5.7.0-rc1
From:   Giovanni Gherdovich <ggherdovich@suse.cz>
To:     Harald Arnesen <harald@skogtun.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Date:   Mon, 20 Apr 2020 10:44:54 +0200
In-Reply-To: <41ae3b90-8e14-9db5-a804-5fdb2eebac03@skogtun.org>
References: <41ae3b90-8e14-9db5-a804-5fdb2eebac03@skogtun.org>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Sat, 2020-04-18 at 18:15 +0200, Harald Arnesen wrote:
> Kernel 5.7.0-rc1 and later won't boot on my ThinkPad T510i.
> 
> The attached jpeg is all I can capture of the oops. Bisected to commit
> 1567c3e3467cddeb019a7b53ec632f834b6a9239, but I cannot revert that to check.
> 
> A strange thing: The same commit is in 5.6.5, and that kernel boots
> fine. 5.7.0-rc1 also boots fine on my desktop.
> 
> Screenshot and config attached. Please request any further info.

Hello Harald,

thanks for the report.

The problem you encountered is likely 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 acknowledged by the subsystem maintainers but not yet
merged in any tree (it is expected to land in the "tip" tree and then be pulled
by Linus).


Thanks,
Giovanni Gherdovich