Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
References: <20190708162756.GA69120@gmail.com>
In-Reply-To: <20190708162756.GA69120@gmail.com>
From:   Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue, 9 Jul 2019 14:20:47 -0700
Message-ID: <CAHk-=wigbHd6wXcrpH+6jnDe=e+OHFy6-KdVSUP2yU5aip-UAg@mail.gmail.com>
Subject: Re: [GIT PULL] x86/topology changes for v5.3
To:     Ingo Molnar <mingo@kernel.org>
Cc:     Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
        Thomas Gleixner <tglx@linutronix.de>,
        Borislav Petkov <bp@alien8.de>, Len Brown <lenb@kernel.org>,
        Peter Zijlstra <a.p.zijlstra@chello.nl>,
        Andrew Morton <akpm@linux-foundation.org>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

After doing a lot of build testing and merging, I finally got around
to actually boot-testing the result.

Something in this series has broken booting for me. Or rather, things
*boot*, but then it hangs in user space, with

   A start job is running for udev Wait for Complete Device Initialization

it does this on both my desktop and laptop, although the exact hang is
different (on my laptop, it hangs earlier - I don't even get to input
the disk encryption keys).

I'm bisecting, and it will take a while to pinpoint, but I can already
tell that it's from one of these pulls:

    Pull x86 topology updates from Ingo Molnar:
    Pull x86 platform updayes from Ingo Molnar:
    Pull x86 paravirt updates from Ingo Molnar:
    Pull x86 AVX512 status update from Ingo Molnar:
    Pull x86 cleanups from Ingo Molnar:
    Pull x86 cache resource control update from Ingo Molnar:
    Pull x86 build updates from Ingo Molnar:
    Pull x86 asm updates from Ingo Molnar:
    Pull scheduler updates from Ingo Molnar:

Will keep you updated as bisection narrows it down.

              Linus