linux-kernel - Re: [Bisected] Oops witn 5.7.0-rc1

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] [day] [month] [year] [list]

Message-ID: <002b6490-9e4c-27d4-304e-775c07be1b61@skogtun.org>
Date:   Mon, 20 Apr 2020 10:54:59 +0200
From:   Harald Arnesen <harald@...gtun.org>
To:     Giovanni Gherdovich <ggherdovich@...e.cz>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [Bisected] Oops witn 5.7.0-rc1

Giovanni Gherdovich [20.04.2020 10:44]:

> 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!

I just sent a new bug report, since rc2 has the same problem. You may
disregard that one, then.
-- 
Hilsen Harald