From: Greg KH <gregkh@linuxfoundation.org>
To: "Holger Hoffstätte" <holger@applied-asynchrony.com>
Cc: "Dylan E." <dylan.eskew@candelatech.com>,
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: Fri, 2 Jan 2026 13:23:01 +0100 [thread overview]
Message-ID: <2026010252-pushchair-cornmeal-5c82@gregkh> (raw)
In-Reply-To: <39762dfb-d8bd-f1ab-b2f5-a44fa8139911@applied-asynchrony.com>
On Wed, Dec 31, 2025 at 09:59:51PM +0100, Holger Hoffstätte wrote:
> On 2025-12-31 21:00, Dylan E. wrote:
> > Hello,
> >
> > When booting into the v6.18.2 tagged kernel from linux-stable, I get the following
> > stack trace while booting into the system every 1 in 5 boots or so, usually during
> > fsck or early systemd service initialization:
> >
> > ---
> > BUG: kernel NULL pointer dereference, address: 0000000000000051
> > #PF: supervisor read access in kernel mode
> > #PF: error_code(0x0000) - not-present page
> > PGD 0 P4D 0
> > Oops: Oops: 0000 [#1] SMP
> > CPU: 0 UID: 0 PID: 15 Comm: rcu_preempt Not tainted 6.18.2 #2 PREEMPT(full)
> > Hardware name: /SKYBAY, BIOS 5.12 06/27/2017
> > RIP: 0010:pick_task_fair+0x57/0x160
> > Code: 66 90 66 90 48 8b 5d 50 48 85 db 74 10 48 8b 73 70 48 89 ef e8 3a 74 ff ff 85 c0 75 71 be 01 00 00 00 48 89 ef e8 29 a5 ff ff <80> 78 51 00 48 89 c3 0f 85 80 00 00 00 48 85 c0 0f 84 87 00 00 00
> > RSP: 0000:ffffc900000d3cf8 EFLAGS: 00010086
> > RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000800
> > RDX: fffffc02295d3c00 RSI: 0000000000000800 RDI: 0000000002edc4f2
> > RBP: ffff888108f13000 R08: 0000000000000400 R09: 0000000000000002
> > R10: 0000000000000260 R11: ffff888108b74200 R12: ffff888265c2cd00
> > R13: 0000000000000000 R14: ffff888265c2cd80 R15: ffffffff827c6fa0
> > FS: 0000000000000000(0000) GS:ffff8882e2724000(0000) knlGS:0000000000000000
> > CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> > CR2: 0000000000000051 CR3: 00000001110a5003 CR4: 00000000003706f0
> > Call Trace:
> > <TASK>
> > pick_next_task_fair+0x1d/0x3d0
> > __schedule+0x1ee/0x10c0
>
> Welcome to the club :) I already reported it and requested a fix in:
> https://lore.kernel.org/stable/04b82346-c38a-08e2-49d5-d64981eb7dae@applied-asynchrony.com/
>
> You can apply the patch from:
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=127b90315ca07ccad2618db7ba950a63e3b32d22
> which should fix it.
Will be in the next 6.18.y release, thanks.
greg k-h
next prev parent reply other threads:[~2026-01-02 12:23 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 [this message]
2026-01-06 18:56 ` Dylan E.
2026-01-08 9:19 ` Greg KH
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=2026010252-pushchair-cornmeal-5c82@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=dylan.eskew@candelatech.com \
--cc=holger@applied-asynchrony.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.