[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CA+G9fYuhDU=5b0my6yMy+ni=K_SFCRxncWJFvj0DVuLftTWYUA@mail.gmail.com>
Date: Sat, 6 Sep 2025 14:14:00 +0530
From: Naresh Kamboju <naresh.kamboju@...aro.org>
To: John Stultz <jstultz@...gle.com>
Cc: open list <linux-kernel@...r.kernel.org>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>, Cgroups <cgroups@...r.kernel.org>,
lkft-triage@...ts.linaro.org, Linux Regressions <regressions@...ts.linux.dev>,
Thomas Gleixner <tglx@...utronix.de>, Peter Zijlstra <peterz@...radead.org>,
Steven Rostedt <rostedt@...dmis.org>, Ingo Molnar <mingo@...nel.org>,
Ben Copeland <benjamin.copeland@...aro.org>, Anders Roxell <anders.roxell@...aro.org>,
Arnd Bergmann <arnd@...db.de>, Dan Carpenter <dan.carpenter@...aro.org>,
Catalin Marinas <catalin.marinas@....com>, Will Deacon <will@...nel.org>, Tejun Heo <tj@...nel.org>,
Johannes Weiner <hannes@...xchg.org>
Subject: Re: arm64/juno-r2: Kernel panic in cgroup_fj_stress.sh on next-20250904
On Sat, 6 Sept 2025 at 02:50, John Stultz <jstultz@...gle.com> wrote:
>
> On Fri, Sep 5, 2025 at 10:50 AM John Stultz <jstultz@...gle.com> wrote:
> >
> > On Fri, Sep 5, 2025 at 6:21 AM Naresh Kamboju <naresh.kamboju@...aro.org> wrote:
> > >
> > > Kernel warnings and a panic were observed on Juno-r2 while running
> > > LTP controllers (cgroup_fj_stress.sh) on the Linux next-20250904 with
> > > SCHED_PROXY_EXEC=y enabled build.
> > >
> > > Regression Analysis:
> > > - New regression? yes
> > > - Reproducibility? yes
> > >
> > > First seen on next-20250904
> > > Bad: next-20250904
> > > Good: next-20250822
> > >
> > > Test regression: next-20250904 juno-r2 cgroup_fj_stress.sh kernel panic
> > >
> > > Reported-by: Linux Kernel Functional Testing <lkft@...aro.org>
> >
> > Thank you for the testing and the report here!
> >
> > > Juno-r2:
> > > * LTP controllers
> > > * cgroup_fj_stress.sh
> > >
> > > Test crash:
> > > cgroup_fj_stress_net_cls_1_200_one:
> > > [ 365.917504] /usr/local/bin/kirk[402]: cgroup_fj_stress_net_cls_1_200_one:
> > > start (command: cgroup_fj_stress.sh net_cls 1 200 one)
> > > [ 374.230110] ------------[ cut here ]------------
> > > [ 374.230132] WARNING: lib/timerqueue.c:55 at
> > > timerqueue_del+0x68/0x70, CPU#5: swapper/5/0
> >
> > This looks like we are removing a timer that was already removed from the queue.
> >
> > I don't see anything obvious right away in the delta that would clue
> > me into what's going on, but I'll try to reproduce this.
>
> So far I've not been able to reproduce this in my environment. If you
> are able to reproduce this easily, could you try enabling
> CONFIG_DEBUG_OBJECTS_TIMERS to see if it shows anything?
I have been running in CI loop for these tests to reproduce and did not
find this again.
I will add this extra Kconfig CONFIG_DEBUG_OBJECTS_TIMERS
and re-run to reproduce this reported regression.
- Naresh
>
> thanks
> -john
Powered by blists - more mailing lists