Date: Mon, 15 Jan 2018 17:22:51 +0200 (EET)
From: Meelis Roos <mroos@linux.ee>
To: Thomas Gleixner <tglx@linutronix.de>
cc: Ingo Molnar <mingo@redhat.com>,
        Linux Kernel list <linux-kernel@vger.kernel.org>,
        x86@kernel.org
Subject: Re: lapic-related boot crash in 4.15-rc1
In-Reply-To: <alpine.DEB.2.20.1801101609470.1919@nanos>
Message-ID: <alpine.LRH.2.21.1801102050200.18455@math.ut.ee>
References: <alpine.LRH.2.21.1801101303350.11024@math.ut.ee> <alpine.DEB.2.20.1801101251590.1919@nanos> <alpine.LRH.2.21.1801101703470.11024@math.ut.ee> <alpine.DEB.2.20.1801101609470.1919@nanos>
User-Agent: Alpine 2.21 (LRH 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org

On Wed, 10 Jan 2018, Thomas Gleixner wrote:

> On Wed, 10 Jan 2018, Meelis Roos wrote:
> 
> > > > On 3 of my test computers, boot hangs with 4.15 git kernels. So far I 
> > > > have traced it down to 4.14.0 being good and 4.15-rc1 being bad (bisect 
> > > > is slow because the computers are somwehat remote). Also because of 
> > > > trying to find when it started, I have not tries newer than rc5 
> > > > kernels.
> > > 
> > > Please do so. We have fixes post rc5 in that area.
> > 
> > P4 was the quickest to rebuild the kernel and it is still hanging like 
> > before with todays 4.15-rc7-00102-gcf1fb158230e.

So far I have bisected it to 4f45ed9f848f good, ae41a2a40ed4 bad. Will 
continue tomorrow.

1be2172e96e3 bad
2cd83ba5bede bad
449fcf3ab0ba bad
43ff2f4db9d0 good
313144c1bcd6 good
b18d62891aaf bad
b24591e2fcf8 good
0696d059f23c bad
023a611748fd bad
ae41a2a40ed4 bad
4f45ed9f848f good

-- 
Meelis Roos (mroos@linux.ee)