From: Peter Zijlstra <peterz@infradead.org>
To: Niklas Cassel <niklas.cassel@linaro.org>
Cc: linux-kernel@vger.kernel.org, bjorn.andersson@linaro.org
Subject: Re: stop_machine() soft lockup
Date: Wed, 5 Sep 2018 15:14:10 +0200 [thread overview]
Message-ID: <20180905131410.GY24082@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20180905114749.GA5345@centauri.lan>
On Wed, Sep 05, 2018 at 01:47:49PM +0200, Niklas Cassel wrote:
> On Wed, Sep 05, 2018 at 10:42:41AM +0200, Peter Zijlstra wrote:
> > On Tue, Sep 04, 2018 at 09:03:22PM +0200, Niklas Cassel wrote:
> > > Hello Peter,
> > >
> > > I'm seeing some lockups when booting linux-next on a db820c arm64 board.
> > > I've tried to analyze, but I'm currently stuck.
> >
> > Please see (should be in your Inbox too):
> >
> > https://lkml.kernel.org/r/20180905084158.GR24124@hirez.programming.kicks-ass.net
>
> I'm sorry if I mislead you by replying to your other mail thread,
> both of them have timekeeping_notify() in the call trace,
> but my problem has this call trace:
>
> [ 128.747853] wait_for_common+0xe0/0x1a0
> [ 128.752023] wait_for_completionx+0x28/0x38
> [ 128.755677] __stop_cpus+0xd4/0xf8
> [ 128.759837] stop_cpus+0x70/0xa8
> [ 128.762958] stop_machine_cpuslocked+0x124/0x130
> [ 128.766345] stop_machine+0x54/0x70
> [ 128.771373] timekeeping_notify+0x44/0x70
> [ 128.774158] __clocksource_select+0xa8/0x1d8
> [ 128.778605] clocksource_done_booting+0x4c/0x64
> [ 128.782931] do_one_initcall+0x94/0x3f8
> [ 128.786921] kernel_init_freeable+0x47c/0x528
> [ 128.790742] kernel_init+0x18/0x110
> [ 128.795673] ret_from_fork+0x10/0x1c
>
>
> while your other mail thread has this call trace:
>
> * stop_machine()
> * timekeeping_notify()
> * __clocksource_select()
> * clocksource_select()
> * clocksource_watchdog_work()
>
>
> So my problem is not related to the watchdog, I tried your revert anyway,
> but unfortunately my problem persists.
Oh, right, missed that distinction. And this is new?
I'll try and have a look. Lockdep doesn't suggest anything?
next prev parent reply other threads:[~2018-09-05 13:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-04 19:03 Niklas Cassel
2018-09-05 8:42 ` Peter Zijlstra
2018-09-05 11:47 ` Niklas Cassel
2018-09-05 13:14 ` Peter Zijlstra [this message]
2018-09-05 13:45 ` Niklas Cassel
2018-09-06 12:56 ` 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=20180905131410.GY24082@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bjorn.andersson@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=niklas.cassel@linaro.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome