From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1753487AbdBKJFk (ORCPT <rfc822;w@1wt.eu>);
        Sat, 11 Feb 2017 04:05:40 -0500
Received: from Galois.linutronix.de ([146.0.238.70]:34961 "EHLO
        Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1753216AbdBKJFh (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Sat, 11 Feb 2017 04:05:37 -0500
Date: Sat, 11 Feb 2017 09:26:19 +0100 (CET)
From: Thomas Gleixner <tglx@linutronix.de>
To: Gabriel C <nix.or.die@gmail.com>
cc: Linus Torvalds <torvalds@linux-foundation.org>,
        Greg KH <gregkh@linuxfoundation.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Andrew Morton <akpm@linux-foundation.org>,
        stable <stable@vger.kernel.org>, lwn@lwn.net,
        Jiri Slaby <jslaby@suse.cz>, Ruslan Ruslichenko <rruslich@cisco.com>
Subject: Re: Linux 4.9.6 ( Restore IO-APIC irq_chip retrigger callback ,
 breaks my box )
In-Reply-To: <1e88cc0e-4d34-a314-a44f-8324335b79e3@gmail.com>
Message-ID: <alpine.DEB.2.20.1702110924371.3734@nanos>
References: <20170126074846.GA19870@kroah.com> <ace2220f-3d75-85cb-54bb-e3bdd0c77f6e@gmail.com> <CA+55aFxe6d0T-VyK=WX1DQqrNs+N_OL5QT0zZP==GEwVgU2vJw@mail.gmail.com> <alpine.DEB.2.20.1702072142500.8117@nanos> <alpine.DEB.2.20.1702072224190.8117@nanos>
 <1e88cc0e-4d34-a314-a44f-8324335b79e3@gmail.com>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Sat, 11 Feb 2017, Gabriel C wrote:
> On 07.02.2017 22:25, Thomas Gleixner wrote:
> Hi Thomas ,
> 
> Sorry I was travelling..

Nothing to be sorry about.

> > Btw, how far in the boot process is the machine when this happens?
> 
> Right after :
> 
> Uncompressing Linux.....
> Booting the kernel..
> 
> So early..

You might try with 'earlyprintk' on the command line. That should tell more.

> One thing is strange .. on all one socket boxes I have the kernel seems
> to be fine with that patch while breaks on both dual socket boxes ( well
> both have near same HW )

That's really weird.

Thanks,

	tglx