Subject: Re: 4.14.9 doesn't boot (regression)
To: Alexander Tsoy <alexander@tsoy.me>, stable@vger.kernel.org
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
References: <b8b49443-e43b-7253-78c9-23a0b1632a3b@gmx.de>
 <1514562525.28262.5.camel@tsoy.me>
From: =?UTF-8?Q?Toralf_F=c3=b6rster?= <toralf.foerster@gmx.de>
Message-ID: <0faed1af-d10a-fcb4-1f94-e3968e141d85@gmx.de>
Date: Fri, 29 Dec 2017 16:52:59 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.5.0
MIME-Version: 1.0
In-Reply-To: <1514562525.28262.5.camel@tsoy.me>
Content-Type: text/plain; charset=utf-8
Content-Language: en-GB
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 856
Lines: 23

On 12/29/2017 04:48 PM, Alexander Tsoy wrote:
> В Пт, 29/12/2017 в 12:14 +0100, Toralf Förster пишет:
>> I can confirm now, that that kernel breaks both a desktop (an
>> ThinkPad T440s i5) and a headless server (i3930) setup. For the
>> server the attached .config works fine but switching from
>> CONFIG_GENERIC_CPU to CONFIG_MCORE2 legt them hang at boot w/op any
>> messages. Similar picture at the desktop.
> 
> You most likely have the same problem as me:
> https://lkml.org/lkml/2017/12/29/279
> 

Indeed, I got a similar message at my ThinkPad too when I tried to bisect it:

>[   21.776011] INFO: rcu_preempt detected stalls on CPUs/tasks:
>[   21.w77008]  0-...!: (0 ticks this GP) idle=c56/140000000000000/0
>softirq=73/73 fqs=0 
>[   21.777008]  (detected by 1, t=21002 jiffies, g=-255, c=-256, q=4)


-- 
Toralf
PGP C4EACDDE 0076E94E