From: "Chen, Yu C" <yu.c.chen@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: kernel test robot <oliver.sang@intel.com>,
Fernand Sieber <sieberf@amazon.com>, <oe-lkp@lists.linux.dev>,
<lkp@intel.com>, <linux-kernel@vger.kernel.org>, <x86@kernel.org>,
<aubrey.li@linux.intel.com>
Subject: Re: [tip:sched/core] [sched/fair] 79104becf4: BUG:kernel_NULL_pointer_dereference,address
Date: Tue, 28 Oct 2025 10:30:08 +0800 [thread overview]
Message-ID: <e9f705f3-3a8f-4952-b5d5-e36f4fa1515d@intel.com> (raw)
In-Reply-To: <20251027140959.GU1386988@noisy.programming.kicks-ass.net>
On 10/27/2025 10:09 PM, Peter Zijlstra wrote:
> On Mon, Oct 27, 2025 at 03:07:18PM +0100, Peter Zijlstra wrote:
>> On Mon, Oct 27, 2025 at 02:55:16PM +0100, Peter Zijlstra wrote:
>>
>>>> May I know if you are using the kernel config 0day attached?
>>>> I found that the config 0day attached
>>>> (https://download.01.org/0day-ci/archive/20251021/202510211205.1e0f5223-lkp@intel.com/config-6.18.0-rc1-00001-g79104becf42b)
>>>> has
>>>> CONFIG_IA32_EMULATION=y
>>>> CONFIG_IA32_EMULATION_DEFAULT_DISABLED=y
>>
>> Yep, deleting that entry makes it all work.
>
> 'work' might be over stating, it boots and starts trinity, which then
> promptly (as in a handful of seconds) triggers OOM and dies. Not
> actually reproducing the NULL deref I was looking for.
Change the following line in job-script
export memory='16G'
to
export memory='64G'
?
I had a try and can reproduce the NULL except at first run:
[ 137.151416][ T321] BUG: kernel NULL pointer dereference, address:
0000000000000051
[ 137.152128][ T321] #PF: supervisor read access in kernel mode
[ 137.152661][ T321] #PF: error_code(0x0000) - not-present page
[ 137.153155][ T321] PGD 100b76067 P4D 100b76067 PUD 115fd6067 PMD 0
[ 137.153834][ T321] Oops: Oops: 0000 [#1]
[ 137.154256][ T321] CPU: 0 UID: 65534 PID: 321 Comm: trinity-c1 Not
tainted 6.18.0-rc1-g30682ad76ee6 #4 PREEMPT
[ 137.155384][ T321] Hardware name: QEMU Ubuntu 24.04 PC (i440FX +
PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
[ 137.156509][ T321] RIP: 0010:pick_task_fair+0x69/0x9d
thanks,
Chenyu
next prev parent reply other threads:[~2025-10-28 2:30 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-21 5:14 [tip:sched/core] [sched/fair] 79104becf4: BUG:kernel_NULL_pointer_dereference,address kernel test robot
2025-10-21 6:39 ` Chen, Yu C
2025-10-21 11:04 ` Peter Zijlstra
2025-10-27 12:54 ` Peter Zijlstra
2025-10-27 13:14 ` Chen, Yu C
2025-10-27 13:55 ` Peter Zijlstra
2025-10-27 14:07 ` Peter Zijlstra
2025-10-27 14:09 ` Peter Zijlstra
2025-10-28 2:30 ` Chen, Yu C [this message]
2025-11-05 11:00 ` Peter Zijlstra
2025-11-05 12:06 ` Philip Li
2025-11-07 10:16 ` Philip Li
2025-11-07 10:53 ` Peter Zijlstra
2025-11-04 21:04 ` Fernand Sieber
2025-11-05 8:43 ` Fernand Sieber
2025-11-05 11:03 ` Peter Zijlstra
2025-11-05 12:28 ` Peter Zijlstra
2025-11-06 10:54 ` Fernand Sieber
2025-11-06 23:57 ` John Stultz
2025-11-07 8:18 ` Fernand Sieber
-- strict thread matches above, loose matches on Subject: below --
2025-11-06 10:40 [PATCH] sched: Proxy yields to donor tasks Fernand Sieber
2025-11-06 10:57 ` Peter Zijlstra
2025-11-07 6:54 ` kernel test robot
2025-11-07 8:12 ` Fernand Sieber
2025-11-07 8:25 ` Peter Zijlstra
2025-11-11 11:37 ` [tip: sched/core] sched/proxy: Yield the donor task tip-bot2 for Fernand Sieber
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=e9f705f3-3a8f-4952-b5d5-e36f4fa1515d@intel.com \
--to=yu.c.chen@intel.com \
--cc=aubrey.li@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=peterz@infradead.org \
--cc=sieberf@amazon.com \
--cc=x86@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