From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753659AbdBTOFo (ORCPT ); Mon, 20 Feb 2017 09:05:44 -0500 Received: from mail-wm0-f42.google.com ([74.125.82.42]:37361 "EHLO mail-wm0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752726AbdBTOFm (ORCPT ); Mon, 20 Feb 2017 09:05:42 -0500 Date: Mon, 20 Feb 2017 15:05:38 +0100 From: Frederic Weisbecker To: Pavel Machek Cc: Thomas Gleixner , wanpeng.li@hotmail.com, Peter Zijlstra , Rik van Riel , Linux Kernel Mailing List Subject: Re: next_tick hang was Re: v4.10-rc8 (-rc6) boot regression on Intel desktop, does not boot after cold boots, boots after reboot Message-ID: <20170220140526.GA2771@lerouge> References: <20170216183421.GC4357@lerouge> <20170217140449.GA4521@lerouge> <20170217170508.GA20884@amd> <20170217184327.GD4521@lerouge> <20170218093917.GA4722@amd> <20170218145029.GA4336@lerouge> <20170218180520.GA9377@amd> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170218180520.GA9377@amd> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Feb 18, 2017 at 07:05:20PM +0100, Pavel Machek wrote: > Hi! > > > > I guess I can. But I'll only have one 80x25 screen to look at... > > > > > > .config is attached. > > > > Ah this is x86-32, interesting! I'm going to try to boot that, we never know. > > > > Thanks a lot! > > Happens on x86-64, too; I'm running that normally, but for testing, > 32-bit kernel is easier. Ah! And you've seen that on only one machine? What kind machine is it? Ideally I would need a dump of all pending timer list timers (no sysrq key for that though, but I can do a quick patch) and a stacktrace of all tasks. But I guess you have no access to any serial port, right? > > thinkpad x60 works fine for me, so it is unlikely that .config is all > it takes... Yeah I booted the .config and it reached the root filesystem mounting without problem. So I think it's specific to some hardware.