From: Mike Galbraith <efault@gmx.de>
To: Vishal Chourasia <vishalc@linux.ibm.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Juri Lelli <juri.lelli@redhat.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Valentin Schneider <vschneid@redhat.com>,
luis.machado@arm.com
Subject: Re: sched/fair: Kernel panics in pick_next_entity
Date: Wed, 02 Oct 2024 08:40:44 +0200 [thread overview]
Message-ID: <12242825054bb861578de6405504875e4d1bb6c2.camel@gmx.de> (raw)
In-Reply-To: <09e16088690e6577b60de489e6e52a3e5769f96f.camel@gmx.de>
On Tue, 2024-10-01 at 18:41 +0200, Mike Galbraith wrote:
>
> When I hit $subject, LTPs cfs_bandwidth01 was running, but there was no
> warning prelude, box went straight to panic. Trying to reproduce using
> that testcase plus hackbench as efficacy booster produced lots of dying
> box noise, but zero sneaky $subject instances before or after quash.
Hohum, this morning I did hit..
1. WARNING: CPU: 5 PID: 931 at kernel/sched/fair.c:6062 unthrottle_cfs_rq+0x4c3/0x4d0
2. WARNING: CPU: 0 PID: 786 at kernel/sched/fair.c:704 update_entity_lag+0x79/0x90
3. NULL dereference in pick_next_entity()
..instead of brick, workqueue stall etc. Twice. Not that it matters.
I was only mucking about with it because I was curious whether telling
LB to stop moving sched_delayed tasks about would matter. (nope)
-Mike
next prev parent reply other threads:[~2024-10-02 6:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-26 12:42 Vishal Chourasia
2024-09-26 14:31 ` Luis Machado
2024-09-30 14:41 ` Peter Zijlstra
2024-09-30 19:05 ` Vishal Chourasia
2024-09-30 19:15 ` Vishal Chourasia
2024-10-01 8:30 ` Mike Galbraith
2024-10-01 14:08 ` Vishal Chourasia
2024-10-01 16:41 ` Mike Galbraith
2024-10-02 6:40 ` Mike Galbraith [this message]
2024-10-02 8:49 ` Peter Zijlstra
2024-10-02 18:22 ` Vishal Chourasia
2024-10-02 22:31 ` Benjamin Segall
2024-10-03 4:41 ` Mike Galbraith
2024-10-03 9:31 ` Mike Galbraith
2024-10-04 7:17 ` Vishal Chourasia
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=12242825054bb861578de6405504875e4d1bb6c2.camel@gmx.de \
--to=efault@gmx.de \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luis.machado@arm.com \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
--cc=vishalc@linux.ibm.com \
--cc=vschneid@redhat.com \
/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®