public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: "Chen, Yu C" <yu.c.chen@intel.com>
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: Mon, 27 Oct 2025 14:55:16 +0100	[thread overview]
Message-ID: <20251027135516.GA3419281@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <3b30e40b-f1fb-4145-b4d9-a9279b9602d8@intel.com>

On Mon, Oct 27, 2025 at 09:14:11PM +0800, Chen, Yu C wrote:
> On 10/27/2025 8:54 PM, Peter Zijlstra wrote:
> > On Tue, Oct 21, 2025 at 01:04:49PM +0200, Peter Zijlstra wrote:
> > > On Tue, Oct 21, 2025 at 01:14:36PM +0800, kernel test robot wrote:
> > > > 
> > > > 
> > > > Hello,
> > > > 
> > > > kernel test robot noticed "BUG:kernel_NULL_pointer_dereference,address" on:
> > > > 
> > > > commit: 79104becf42baeeb4a3f2b106f954b9fc7c10a3c ("sched/fair: Forfeit vruntime on yield")
> > > > https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git sched/core
> > > > 
> > > > [test failed on linux-next/master 606da5bb165594c052ee11de79bf05bc38bc1aa6]
> > > > 
> > > > in testcase: trinity
> > > > version:
> > > > with following parameters:
> > > > 
> > > > 	runtime: 300s
> > > > 	group: group-04
> > > > 	nr_groups: 5
> > > > 
> > > > 
> > > > 
> > > > config: x86_64-randconfig-121-20251020
> > > > compiler: gcc-13
> > > > test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G
> > > > 
> > > 
> > > > The kernel config and materials to reproduce are available at:
> > > > https://download.01.org/0day-ci/archive/20251021/202510211205.1e0f5223-lkp@intel.com
> > > 
> > > 
> > > I'm failing at running the kernel as described in:
> > > 
> > >    https://download.01.org/0day-ci/archive/20251021/202510211205.1e0f5223-lkp@intel.com/reproduce
> > > 
> > > 
> > > I then start the test as:
> > > 
> > > root@spr:/usr/local/src/lkp-tests# bin/lkp qemu -k /usr/src/linux-2.6/tmp-build/arch/x86/boot/bzImage -m /usr/src/linux-2.6/tmp-build/modules.cgz /usr/src/linux-2.6/tmp-build/job-script
> > > result_root: /root/.lkp//result/trinity/group-04-5-300s/vm-snb/quantal-i386-core-20190426.cgz/x86_64-randconfig-121-20251020/gcc-13/79104becf42baeeb4a3f2b106f954b9fc7c10a3c/4
> > > downloading initrds ...
> > > use local modules: /root/.lkp/cache/modules.cgz
> > > skip downloading /root/.lkp/cache/osimage/quantal/quantal-i386-core-20190426.cgz
> > > 153636 blocks
> > > skip downloading /root/.lkp/cache/osimage/pkg/quantal-i386-core.cgz/trinity-static-i386-x86_64-f93256fb_2019-08-28.cgz
> > > 48101 blocks
> > > exec command: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -fsdev local,id=test_dev,path=/root/.lkp//result/trinity/group-04-5-300s/vm-snb/quantal-i386-core-20190426.cgz/x86_64-randconfig-121-20251020/gcc-13/79104becf42baeeb4a3f2b106f954b9fc7c10a3c/4,security_model=none -device virtio-9p-pci,fsdev=test_dev,mount_tag=9p/virtfs_mount -kernel /usr/src/linux-2.6/tmp-build/arch/x86/boot/bzImage -append root=/dev/ram0 RESULT_ROOT=/result/trinity/group-04-5-300s/vm-snb/quantal-i386-core-20190426.cgz/x86_64-randconfig-121-20251020/gcc-13/79104becf42baeeb4a3f2b106f954b9fc7c10a3c/1 BOOT_IMAGE=/pkg/linux/x86_64-randconfig-121-20251020/gcc-13/79104becf42baeeb4a3f2b106f954b9fc7c10a3c/vmlinuz-6.18.0-rc1-00001-g79104becf42b branch=linux-devel/devel-hourly-20251019-154855 job=/lkp/jobs/scheduled/vm-meta-291/trinity-group-04-5-300s-quantal-i386-core-20190426.cgz-x86_64-randconfig-121-20251020-79104becf42b-20251020-124904-8548hu-1.yaml user=lkp ARCH=x86_64 kconfig=x86_64-randconfig-121-20251020 commit=79104becf42baeeb4a3f2b106f954b9fc7c10a3c intremap=posted_msi vmalloc=256M initramfs_async=0 page_owner=on carrier_timeout=60 rcupdate.rcu_self_test=0 max_uptime=7200 LKP_LOCAL_RUN=1 selinux=0 debug apic=debug sysrq_always_enabled rcupdate.rcu_cpu_stall_timeout=100 net.ifnames=0 printk.devkmsg=on panic=-1 softlockup_panic=1 nmi_watchdog=panic oops=panic load_ramdisk=2 prompt_ramdisk=0 drbd.minor_count=8 systemd.log_level=err ignore_loglevel console=tty0 earlyprintk=ttyS0,115200 console=ttyS0,115200 vga=normal rw  ip=dhcp result_service=9p/virtfs_mount -initrd /root/.lkp/cache/final_initrd -smp 2 -m 16384M -no-reboot -device i6300esb -rtc base=localtime -device e1000,netdev=net0 -netdev user,id=net0 -display none -monitor null -serial stdio
> > 
> > > [    5.650807][    T1] Starting init: /bin/sh exists but couldn't execute it (error -8)
> 
> 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
> CONFIG_COMPAT_32=y
> CONFIG_COMPAT=y
> 
> It is suspected that the filesystem provided by lkp is 32bits, might
> need Oliver's confirm.

It was certainly meant to be that config -- let be double check that.

  reply	other threads:[~2025-10-27 13:55 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 [this message]
2025-10-27 14:07         ` Peter Zijlstra
2025-10-27 14:09           ` Peter Zijlstra
2025-10-28  2:30             ` Chen, Yu C
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=20251027135516.GA3419281@noisy.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --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=sieberf@amazon.com \
    --cc=x86@kernel.org \
    --cc=yu.c.chen@intel.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