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 S1752011AbdKVTKP (ORCPT <rfc822;w@1wt.eu>);
        Wed, 22 Nov 2017 14:10:15 -0500
Received: from usa-sjc-mx-foss1.foss.arm.com ([217.140.101.70]:55156 "EHLO
        foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1751773AbdKVTKO (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Wed, 22 Nov 2017 14:10:14 -0500
Date: Wed, 22 Nov 2017 19:10:14 +0000
From: Will Deacon <will.deacon@arm.com>
To: Sebastian Ott <sebott@linux.vnet.ibm.com>
Cc: Peter Zijlstra <peterz@infradead.org>, Ingo Molnar <mingo@kernel.org>,
        Martin Schwidefsky <schwidefsky@de.ibm.com>,
        Heiko Carstens <heiko.carstens@de.ibm.com>,
        linux-kernel@vger.kernel.org
Subject: Re: [bisected] system hang after boot
Message-ID: <20171122191013.GF22648@arm.com>
References: <alpine.LFD.2.21.1711221832100.1728@schleppi>
 <20171122182659.GA22648@arm.com>
 <alpine.LFD.2.21.1711221946390.1728@schleppi>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.LFD.2.21.1711221946390.1728@schleppi>
User-Agent: Mutt/1.5.23 (2014-03-12)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Hi Sebastian,

On Wed, Nov 22, 2017 at 07:54:54PM +0100, Sebastian Ott wrote:
> On Wed, 22 Nov 2017, Will Deacon wrote:
> > Now, I can't see what the break_lock is doing here other than causing
> > problems. Is there a good reason for it, or can you just try removing it
> > altogether? Patch below.
> 
> With your patch applied the system is able to boot again.
> I did some quick additional tests - seems to be working fine.

That was quick, thanks!

So the million dollar question is: does somebody care about the break_lock
field and, if so, why?

Will