← Back to team overview

canonical-ubuntu-qa team mailing list archive

[Bug 2116171] [NEW] hugemmap05 from hugetlb in ubuntu_ltp_stable failed with 5.15 on AWS a1.xlarge

 

Public bug reported:

Issue found after updating our LTP fork to upstream head SHA1 c9e5b1e508

So far I can only see this issue with AWS a1.xlarge instance with 5.15
64k kernel.

The test failed with:
  TBROK: mmap((nil),1610612736,PROT_READ | PROT_WRITE(3),1,8,0) failed: ENOMEM (12)

Test output:
 startup='Mon Jul  7 03:10:27 2025'
 tst_hugepage.c:84: TINFO: 2 hugepage(s) reserved
 tst_tmpdir.c:316: TINFO: Using /tmp/ltp-EsAJcZdEfd/LTP_hugsU4n2Z as tmpdir (ext2/ext3/ext4 filesystem)
 tst_test.c:1952: TINFO: LTP version: 20230929-1381-g3d4c171fb
 tst_test.c:1955: TINFO: Tested kernel: 5.15.0-1088-aws-64k #95-Ubuntu SMP Mon Jun 30 17:07:33 UTC 2025 aarch64
 tst_kconfig.c:88: TINFO: Parsing kernel config '/lib/modules/5.15.0-1088-aws-64k/build/.config'
 tst_test.c:1773: TINFO: Overall timeout per run is 0h 00m 30s
 hugemmap05.c:224: TINFO: original nr_overcommit_hugepages is 0
 hugemmap05.c:232: TINFO: Mounting (null) to /tmp/ltp-EsAJcZdEfd/LTP_hugsU4n2Z/hugemmap05 fstyp=hugetlbfs flags=0
 hugemmap05.c:82: TBROK: mmap((nil),1610612736,PROT_READ | PROT_WRITE(3),1,8,0) failed: ENOMEM (12)
 hugemmap05.c:177: TINFO: restore nr_overcommit_hugepages to 0.
 
 Summary:
 passed   0
 failed   0
 broken   1
 skipped  0
 warnings 0
 tag=hugemmap05 stime=1751857827 dur=0 exit=exited stat=2 core=no cu=0 cs=9

And this seems to be flaky, I was unable to 100% reproduce it with
multiple manual test attempts.

** Affects: ubuntu-kernel-tests
     Importance: Undecided
         Status: New


** Tags: 5.15 aws jammy ubuntu-ltp-stable

-- 
You received this bug notification because you are a member of Canonical
Platform QA Team, which is subscribed to ubuntu-kernel-tests.
https://bugs.launchpad.net/bugs/2116171

Title:
  hugemmap05 from hugetlb in ubuntu_ltp_stable failed with 5.15 on AWS
  a1.xlarge

Status in ubuntu-kernel-tests:
  New

Bug description:
  Issue found after updating our LTP fork to upstream head SHA1
  c9e5b1e508

  So far I can only see this issue with AWS a1.xlarge instance with 5.15
  64k kernel.

  The test failed with:
    TBROK: mmap((nil),1610612736,PROT_READ | PROT_WRITE(3),1,8,0) failed: ENOMEM (12)

  Test output:
   startup='Mon Jul  7 03:10:27 2025'
   tst_hugepage.c:84: TINFO: 2 hugepage(s) reserved
   tst_tmpdir.c:316: TINFO: Using /tmp/ltp-EsAJcZdEfd/LTP_hugsU4n2Z as tmpdir (ext2/ext3/ext4 filesystem)
   tst_test.c:1952: TINFO: LTP version: 20230929-1381-g3d4c171fb
   tst_test.c:1955: TINFO: Tested kernel: 5.15.0-1088-aws-64k #95-Ubuntu SMP Mon Jun 30 17:07:33 UTC 2025 aarch64
   tst_kconfig.c:88: TINFO: Parsing kernel config '/lib/modules/5.15.0-1088-aws-64k/build/.config'
   tst_test.c:1773: TINFO: Overall timeout per run is 0h 00m 30s
   hugemmap05.c:224: TINFO: original nr_overcommit_hugepages is 0
   hugemmap05.c:232: TINFO: Mounting (null) to /tmp/ltp-EsAJcZdEfd/LTP_hugsU4n2Z/hugemmap05 fstyp=hugetlbfs flags=0
   hugemmap05.c:82: TBROK: mmap((nil),1610612736,PROT_READ | PROT_WRITE(3),1,8,0) failed: ENOMEM (12)
   hugemmap05.c:177: TINFO: restore nr_overcommit_hugepages to 0.
   
   Summary:
   passed   0
   failed   0
   broken   1
   skipped  0
   warnings 0
   tag=hugemmap05 stime=1751857827 dur=0 exit=exited stat=2 core=no cu=0 cs=9

  And this seems to be flaky, I was unable to 100% reproduce it with
  multiple manual test attempts.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2116171/+subscriptions