hugemmap05_1 hugemmap10 from hugetlb in ubuntu_ltp_stable failed on B-ibm-gt

Bug #2057898 reported by Po-Hsu Lin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-kernel-tests
New
Undecided
Unassigned

Bug Description

Issue found with B-ibm-gt 4.15.0-1156.169 on node durin and openstack AMD64 instance.

Test failed with hugemmap05_1 and hugemmap10 these 2 test cases:

 startup='Thu Mar 14 01:44:13 2024'
 tst_hugepage.c:84: TINFO: 4 hugepage(s) reserved
 tst_test.c:1741: TINFO: LTP version: 20230929-406-gcbc2d0568
 tst_test.c:1627: TINFO: Timeout per run is 0h 00m 30s
 hugemmap05.c:226: TINFO: original nr_overcommit_hugepages is 0
 hugemmap05.c:233: TINFO: Mounting (null) to /tmp/ltp-2GRCMg39hB/LTP_huglALBlM/hugemmap05 fstyp=hugetlbfs flags=0
 hugemmap05.c:99: TINFO: check /proc/meminfo before allocation.
 hugemmap05.c:275: TINFO: HugePages_Total is 4.
 hugemmap05.c:278: TFAIL: HugePages_Total is not 3 but 4.
 hugemmap05.c:179: TINFO: restore nr_overcommit_hugepages to 0.

 Summary:
 passed 0
 failed 1
 broken 0
 skipped 0
 warnings 0
 tag=hugemmap05_1 stime=1710380653 dur=0 exit=exited stat=1 core=no cu=0 cs=2

 startup='Thu Mar 14 01:44:03 2024'
 tst_hugepage.c:84: TINFO: 5 hugepage(s) reserved
 tst_test.c:1049: TINFO: Mounting none to /tmp/ltp-hmfJwHRq3e/LTP_hugYYlEVD/hugetlbfs fstyp=hugetlbfs flags=0
 tst_test.c:1741: TINFO: LTP version: 20230929-406-gcbc2d0568
 tst_test.c:1627: TINFO: Timeout per run is 0h 00m 30s
 hugemmap10.c:388: TINFO: Base pool size: 0
 hugemmap10.c:315: TINFO: Clean...
 hugemmap10.c:317: TFAIL: While initializing hugepages pool: Bad HugePages_Total: expected 0, actual 2
 hugemmap10.c:317: TFAIL: While initializing hugepages pool: Bad HugePages_Free: expected 0, actual 2
 hugemmap10.c:317: TFAIL: While initializing hugepages pool: Bad HugePages_Surp: expected 0, actual 2

 Summary:
 passed 0
 failed 3
 broken 0
 skipped 0
 warnings 0
 tag=hugemmap10 stime=1710380643 dur=0 exit=exited stat=1 core=no cu=0 cs=3

This is not a regression, from our hint database it looks this can be traced all the way back to -1148

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.