From: Harry Yoo <harry.yoo@oracle.com>
To: kernel test robot <oliver.sang@intel.com>
Cc: Uladzislau Rezki <urezki@gmail.com>,
oe-lkp@lists.linux.dev, lkp@intel.com,
Andrew Morton <akpm@linux-foundation.org>,
Baoquan He <bhe@redhat.com>, Adrian Huang <ahuang12@lenovo.com>,
Christop Hellwig <hch@infradead.org>,
Mateusz Guzik <mjguzik@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [linux-next:master] [lib/test_vmalloc.c] 7fc85b92db: Mem-Info
Date: Sat, 21 Jun 2025 05:08:37 +0900 [thread overview]
Message-ID: <aFW_xQdFhjeFTeq5@hyeyoo> (raw)
In-Reply-To: <202505071555.e757f1e0-lkp@intel.com>
On Wed, May 07, 2025 at 04:24:24PM +0800, kernel test robot wrote:
>
>
> Hello,
>
>
> by this commit, we notice the config diff:
>
> --- /pkg/linux/i386-randconfig-053-20250503/gcc-12/ceec7f2554e7af6f6a11acee3dcba414b9ecdccd/.config 2025-05-07 06:57:33.691929038 +0800
> +++ /pkg/linux/i386-randconfig-053-20250503/gcc-12/7fc85b92db96fd88f86f8e977e7e142c233680b4/.config 2025-05-07 01:22:43.415543806 +0800
> @@ -6760,7 +6760,7 @@ CONFIG_TEST_IDA=m
> CONFIG_TEST_MISC_MINOR=m
> # CONFIG_TEST_LKM is not set
> CONFIG_TEST_BITOPS=m
> -CONFIG_TEST_VMALLOC=m
> +CONFIG_TEST_VMALLOC=y
> # CONFIG_TEST_BPF is not set
> CONFIG_FIND_BIT_BENCHMARK=m
> CONFIG_TEST_FIRMWARE=m
>
>
> then we find a i386 config boot test always fail as "kernel_hang_in_boot_stage"
> in one of tests, we captured some information about Mem-Info.
Hi Oliver,
This is simply the vmalloc test module simply taking too long time to
finish. I've observed it taking up to ~5000 seconds.
This is not a bug, it's just too slow and the timed out.
When I used my qemu command that I use everyday, it took up to 1400 seconds.
When using the job-script provided to run it, it took much longer.
I don't know the exact reason ;)
In any case, I’m not sure the vmalloc test module should be part of
your i386 boot test as it takes too long to complete.
On x86_64 this was not an issue because the vmalloc test module
completes testing much faster.
> =========================================================================================
> tbox_group/testcase/rootfs/kconfig/compiler/sleep:
> vm-snb-i386/boot/debian-11.1-i386-20220923.cgz/i386-randconfig-053-20250503/gcc-12/1
>
> ceec7f2554e7af6f 7fc85b92db96fd88f86f8e977e7
> ---------------- ---------------------------
> fail:runs %reproduction fail:runs
> | | |
> :6 100% 6:6 last_state.booting
> :6 100% 6:6 last_state.is_incomplete_run
> :6 100% 6:6 dmesg.BUG:kernel_hang_in_boot_stage
> :6 17% 1:6 dmesg.Mem-Info
>
> BTW, seems x86_64 config tests are ok.
>
> below details just FYI.
>
>
> kernel test robot noticed "Mem-Info" on:
>
> commit: 7fc85b92db96fd88f86f8e977e7e142c233680b4 ("lib/test_vmalloc.c: allow built-in execution")
> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
>
> [test failed on linux-next/master 0a00723f4c2d0b273edd0737f236f103164a08eb]
>
> in testcase: boot
>
> config: i386-randconfig-053-20250503
> compiler: gcc-12
> test machine: qemu-system-i386 -enable-kvm -cpu SandyBridge -smp 2 -m 4G
>
> (please refer to attached dmesg/kmsg for entire log/backtrace)
>
>
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <oliver.sang@intel.com>
> | Closes: https://lore.kernel.org/oe-lkp/202505071555.e757f1e0-lkp@intel.com
>
>
>
> [ 568.859422][ T77] ? kthread_is_per_cpu (kbuild/obj/consumer/i386-randconfig-053-20250503/kernel/kthread.c:413)
> [ 568.859422][ T77] ret_from_fork (kbuild/obj/consumer/i386-randconfig-053-20250503/arch/x86/kernel/process.c:159)
> [ 568.859422][ T77] ? kthread_is_per_cpu (kbuild/obj/consumer/i386-randconfig-053-20250503/kernel/kthread.c:413)
> [ 568.859422][ T77] ret_from_fork_asm (kbuild/obj/consumer/i386-randconfig-053-20250503/arch/x86/entry/entry_32.S:737)
> [ 568.859422][ T77] entry_INT80_32 (kbuild/obj/consumer/i386-randconfig-053-20250503/arch/x86/entry/entry_32.S:942)
> [ 568.892507][ T77] Mem-Info:
> [ 568.893062][ T77] active_anon:0 inactive_anon:0 isolated_anon:0
> [ 568.893062][ T77] active_file:0 inactive_file:0 isolated_file:0
> [ 568.893062][ T77] unevictable:81237 dirty:0 writeback:0
> [ 568.893062][ T77] slab_reclaimable:4892 slab_unreclaimable:990
> [ 568.893062][ T77] mapped:0 shmem:0 pagetables:37
> [ 568.893062][ T77] sec_pagetables:0 bounce:0
> [ 568.893062][ T77] kernel_misc_reclaimable:0
> [ 568.893062][ T77] free:642768 free_pcp:7866 free_cma:0
> [ 568.907502][ T77] Node 0 active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:324948kB isolated(anon):0kB isolated(file):0kB mapped:0kB dirty:0kB writeback:0kB shmem:0kB writeback_tmp:0kB kernel_stack:344kB pagetables:148kB sec_pagetables:0kB all_unreclaimable? no Balloon:0kB
> [ 568.913478][ T77] DMA free:15360kB boost:0kB min:76kB low:92kB high:108kB reserved_highatomic:0KB free_highatomic:0KB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB writepending:0kB present:15992kB managed:15360kB mlocked:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB
> [ 568.919639][ T77] lowmem_reserve[]: 0 664 2988 2988
> [ 568.922660][ T77] Normal free:562624kB boost:0kB min:3016kB low:3768kB high:4520kB reserved_highatomic:0KB free_highatomic:0KB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:7336kB writepending:0kB present:749560kB managed:680084kB mlocked:0kB bounce:0kB free_pcp:31472kB local_pcp:31472kB free_cma:0kB
> [ 568.928669][ T77] lowmem_reserve[]: 0 0 18591 18591
> [ 568.930481][ T77] DMA: 0*4kB 0*8kB 0*16kB 0*32kB 0*64kB 0*128kB 0*256kB 0*512kB 1*1024kB (U) 1*2048kB (U) 3*4096kB (M) = 15360kB
> [ 568.935634][ T77] Normal: 2*4kB (ME) 1*8kB (M) 3*16kB (UME) 4*32kB (UME) 2*64kB (ME) 1*128kB (M) 28*256kB (UME) 52*512kB (UM) 2*1024kB (M) 1*2048kB (U) 128*4096kB (M) = 562624kB
> [ 568.942674][ T77] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=4096kB
> [ 568.944646][ T77] 81256 total pagecache pages
> [ 568.945136][ T77] 0 pages in swap cache
> [ 568.947632][ T77] Free swap = 0kB
> [ 568.948086][ T77] Total swap = 0kB
> [ 568.949615][ T77] 786302 pages RAM
> [ 568.950027][ T77] 594914 pages HighMem/MovableOnly
> [ 568.952655][ T77] 17527 pages reserved
> [ 568.953101][ T77] 0 pages cma reserved
> BUG: kernel hang in boot stage
>
>
> The kernel config and materials to reproduce are available at:
> https://download.01.org/0day-ci/archive/20250507/202505071555.e757f1e0-lkp@intel.com
>
>
>
> --
> 0-DAY CI Kernel Test Service
> https://github.com/intel/lkp-tests/wiki
>
--
Cheers,
Harry / Hyeonggon
prev parent reply other threads:[~2025-06-20 20:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-07 8:24 [linux-next:master] [lib/test_vmalloc.c] 7fc85b92db: Mem-Info kernel test robot
2025-06-20 20:08 ` Harry Yoo [this message]
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=aFW_xQdFhjeFTeq5@hyeyoo \
--to=harry.yoo@oracle.com \
--cc=ahuang12@lenovo.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mjguzik@gmail.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=urezki@gmail.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