From: Steven Rostedt <rostedt@goodmis.org>
To: Pavel Machek <pavel@denx.de>
Cc: ben.hutchings@codethink.co.uk, Chris.Paterson2@renesas.com,
bigeasy@linutronix.de, LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Carsten Emde <C.Emde@osadl.org>, John Kacur <jkacur@redhat.com>,
Julia Cartwright <julia@ni.com>, Daniel Wagner <wagi@monom.org>,
Tom Zanussi <zanussi@kernel.org>,
"Srivatsa S. Bhat" <srivatsa@csail.mit.edu>
Subject: Re: 4.19.106-rt44 -- boot problems with irqwork: push most work into softirq context
Date: Fri, 20 Mar 2020 16:05:45 -0400 [thread overview]
Message-ID: <20200320160545.26a65de3@gandalf.local.home> (raw)
In-Reply-To: <20200320195432.GA12666@duo.ucw.cz>
On Fri, 20 Mar 2020 20:54:32 +0100
Pavel Machek <pavel@denx.de> wrote:
> > Does this patch help?
>
> I don't think so. It also failed, and the failure seems to be
> identical to me.
>
> https://gitlab.com/cip-project/cip-kernel/linux-cip/tree/ci/pavel/linux-cip
> https://lava.ciplatform.org/scheduler/job/13110
>
Can you send me a patch that shows the difference between the revert that
you say works, and the upstream v4.19-rt tree (let me know which version
of v4.19-rt you are basing it on).
Thanks!
-- Steve
next prev parent reply other threads:[~2020-03-20 20:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 22:08 [ANNOUNCE] 4.19.106-rt44 Steven Rostedt
2020-03-19 21:48 ` Pavel Machek
2020-03-19 23:22 ` 4.19.106-rt44 -- boot problems with irqwork: push most work into softirq context Pavel Machek
2020-03-20 0:48 ` Steven Rostedt
2020-03-20 19:54 ` Pavel Machek
2020-03-20 20:05 ` Steven Rostedt [this message]
2020-03-21 22:43 ` Pavel Machek
2020-03-21 23:00 ` Pavel Machek
2020-03-29 10:09 ` 4.4-rt ... seems to have same ireqwork problem was " Pavel Machek
2020-03-30 20:15 ` Steven Rostedt
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=20200320160545.26a65de3@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=C.Emde@osadl.org \
--cc=Chris.Paterson2@renesas.com \
--cc=ben.hutchings@codethink.co.uk \
--cc=bigeasy@linutronix.de \
--cc=jkacur@redhat.com \
--cc=julia@ni.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=pavel@denx.de \
--cc=srivatsa@csail.mit.edu \
--cc=tglx@linutronix.de \
--cc=wagi@monom.org \
--cc=zanussi@kernel.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
all inboxes | Powered by JetHome®