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: Thu, 6 Sep 2018 14:56:37 +0200 [thread overview]
Message-ID: <20180906125637.GJ24082@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20180905134553.GB5345@centauri.lan>
On Wed, Sep 05, 2018 at 03:45:53PM +0200, Niklas Cassel wrote:
> However, I just managed to get this lockdep splat when booting without
> earlycon and ftrace=irqsoff
> I'm not sure that it is related, but I'm planning on looking into it anyway:
That looks like your generic printk is crap splat.
I tend to use this patch-set:
https://lkml.kernel.org/r/20170928121823.430053219@infradead.org
and have (on x86):
earlyprintk=serial,ttyS0,115200 force_early_printk debug ignore_loglevel
That results in a printk that does pure UART bit-banging and works from
any context without issue.
prev parent reply other threads:[~2018-09-06 12:56 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
2018-09-05 13:45 ` Niklas Cassel
2018-09-06 12:56 ` Peter Zijlstra [this message]
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=20180906125637.GJ24082@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