From: Pavel Machek <pavel@denx.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Pavel Machek <pavel@denx.de>,
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 20:54:32 +0100 [thread overview]
Message-ID: <20200320195432.GA12666@duo.ucw.cz> (raw)
In-Reply-To: <20200319204859.5011a488@gandalf.local.home>
[-- Attachment #1: Type: text/plain, Size: 2467 bytes --]
Hi!
> > > > I'm pleased to announce the 4.19.106-rt44 stable release.
> > > >
> > > >
> > > > This release is just an update to the new stable 4.19.106 version
> > > > and no RT specific changes have been made.
> > > >
> > > >
> > > > You can get this release via the git tree at:
> > > >
> > > > git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git
> > > >
> > > > branch: v4.19-rt
> > > > Head SHA1: 0f2960c75dd68d339f0aff2935f51652b5625fbf
> > >
> > > This brought some problems for me. de0-nano board now fails to boot in
> > > cca 50% of cases if I move these patches on top of -cip tree.
> > >
> > > This is example of failed job:
> > >
> > > https://lava.ciplatform.org/scheduler/job/13037
> > >
> > > de0-nano is 32-bit arm, should be based on Altera SoCFPGA if I understand
> > > things correctly.
> > >
> > > "fc9f4631a290 irqwork: push most work into softirq context" touches
> > > area of the panic above. I tried to revert it on top of the full
> > > series, and tests passed twice so far...
> >
> > Test passed 7 times now. So yes, reverting this fixes de0-nano
> > boot. Any ideas what might be wrong?
> >
> > I'll be running it few more times.
> >
> > https://gitlab.com/cip-project/cip-kernel/linux-cip/pipelines/127953471
> >
>
> Looks like you are running this without PREEMPT_RT enabled.
Yes. We still need to set up proper realtime testing.
> 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
Best regards,
Pavel
> diff --git a/kernel/irq_work.c b/kernel/irq_work.c
> index 2940622da5b3..0ca75c77536b 100644
> --- a/kernel/irq_work.c
> +++ b/kernel/irq_work.c
> @@ -146,8 +146,9 @@ bool irq_work_needs_cpu(void)
> raised = this_cpu_ptr(&raised_list);
> lazy = this_cpu_ptr(&lazy_list);
>
> - if (llist_empty(raised) && llist_empty(lazy))
> - return false;
> + if (llist_empty(raised) || arch_irq_work_has_interrupt())
> + if (llist_empty(lazy))
> + return false;
>
> /* All work should have been flushed before going offline */
> WARN_ON_ONCE(cpu_is_offline(smp_processor_id()));
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2020-03-20 19:54 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 [this message]
2020-03-20 20:05 ` Steven Rostedt
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=20200320195432.GA12666@duo.ucw.cz \
--to=pavel@denx.de \
--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=rostedt@goodmis.org \
--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;
as well as URLs for NNTP newsgroup(s).