From: Greg KH <gregkh@linuxfoundation.org>
To: "Dylan E." <dylan.eskew@candelatech.com>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-wireless@vger.kernel.org, sashal@kernel.org,
jjohnson@kernel.org
Subject: Re: [BUG 6.18.2] Null Pointer Exception in Fair Scheduler
Date: Thu, 8 Jan 2026 10:19:51 +0100 [thread overview]
Message-ID: <2026010836-pony-driveway-65ab@gregkh> (raw)
In-Reply-To: <e5cba37b-2bb5-46fb-b414-5cc6b2e894cf@candelatech.com>
On Tue, Jan 06, 2026 at 10:56:49AM -0800, Dylan E. wrote:
> Hello again,
>
> On 6.18.3, I'm still seeing the scheduler NPE pop-up, though this one
> happened at shutdown. Looks to be an identical location to the previous
> stack trace.
I don't think the fix landed in 6.18.3, can you try 6.18.4?
thanks,
greg k-h
next prev parent reply other threads:[~2026-01-08 9:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-31 20:00 [BUG 6.18.2] Null Pointer Exception in Fair Scheduler Dylan E.
2025-12-31 20:13 ` Salvatore Bonaccorso
2025-12-31 20:59 ` Holger Hoffstätte
2026-01-02 12:23 ` Greg KH
2026-01-06 18:56 ` Dylan E.
2026-01-08 9:19 ` Greg KH [this message]
2026-01-08 16:02 ` Dylan E.
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=2026010836-pony-driveway-65ab@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=dylan.eskew@candelatech.com \
--cc=jjohnson@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=stable@vger.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