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
Date: Wed, 22 Nov 2017 19:10:14 +0000 [thread overview]
Message-ID: <20171122191013.GF22648@arm.com> (raw)
In-Reply-To: <alpine.LFD.2.21.1711221946390.1728@schleppi>
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
next prev parent reply other threads:[~2017-11-22 19:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-22 17:46 [bisected] system hang after boot Sebastian Ott
2017-11-22 18:26 ` Will Deacon
2017-11-22 18:54 ` Sebastian Ott
2017-11-22 19:10 ` Will Deacon [this message]
2017-11-22 20:22 ` Peter Zijlstra
2017-11-27 11:49 ` Will Deacon
2017-11-27 12:45 ` Will Deacon
2017-11-27 13:05 ` Sebastian Ott
2017-11-27 12:49 ` Martin Schwidefsky
2017-11-27 12:54 ` Will Deacon
2017-11-27 13:00 ` Martin Schwidefsky
2017-11-27 13:10 ` Will Deacon
2017-11-27 13:13 ` Peter Zijlstra
2017-11-27 13:12 ` Peter Zijlstra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171122191013.GF22648@arm.com \
--to=will.deacon@arm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=schwidefsky@de.ibm.com \
--cc=sebott@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.