canonical-ubuntu-qa team mailing list archive
-
canonical-ubuntu-qa team
-
Mailing list archive
-
Message #00898
[Bug 2026543] [NEW] hugefork02 in ubuntu_ltp_stable/hugetlb will timeout with J-6.2 ARM64k
Public bug reported:
This issue can be found on J-6.2 generic / lowlatency ARM64k with node
wright-kernel.
It feels likes a hw-specific issue, test passed with L-generic ARM64k
starmie-kernel (for L-lowlatency ARM64k scobee-kernel, test was unable
to start due to a hang in dio test)
When this happens, it will cause failures to these tests as well:
hugemmap05 hugemmap05_1 hugemmap10 hugeshmctl02
Test log:
startup='Fri Jul 7 08:47:20 2023'
tst_hugepage.c:83: TINFO: 5 hugepage(s) reserved
tst_test.c:1558: TINFO: Timeout per run is 0h 00m 30s
Test timeouted, sending SIGKILL!
tst_test.c:1606: TINFO: Killed the leftover descendant processes
tst_test.c:1612: TINFO: If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1
tst_test.c:1614: TBROK: Test killed! (timeout?)
Summary:
passed 0
failed 0
broken 1
skipped 0
warnings 0
tag=hugefork02 stime=1688719640 dur=31 exit=exited stat=2 core=no cu=0 cs=20
And lead to ENOMEM to other tests:
startup='Fri Jul 7 08:48:04 2023'
tst_hugepage.c:83: TINFO: 7 hugepage(s) reserved
tst_test.c:1558: TINFO: Timeout per run is 0h 00m 30s
hugemmap05.c:225: TINFO: original nr_overcommit_hugepages is 0
hugemmap05.c:83: TBROK: mmap((nil),1610612736,3,1,8,0) failed: ENOMEM (12)
hugemmap05.c:178: TINFO: restore nr_overcommit_hugepages to 0.
Summary:
passed 0
failed 0
broken 1
skipped 0
warnings 0
tag=hugemmap05 stime=1688719684 dur=0 exit=exited stat=2 core=no cu=0 cs=10
startup='Fri Jul 7 08:49:00 2023'
tst_hugepage.c:83: TINFO: 7 hugepage(s) reserved
tst_test.c:1558: TINFO: Timeout per run is 0h 00m 30s
hugemmap05.c:225: TINFO: original nr_overcommit_hugepages is 0
hugemmap05.c:79: TBROK: shmget(219611296, 1610612736, b80) failed: ENOMEM (12)
hugemmap05.c:178: TINFO: restore nr_overcommit_hugepages to 0.
Summary:
passed 0
failed 0
broken 1
skipped 0
warnings 0
tag=hugemmap05_1 stime=1688719740 dur=0 exit=exited stat=2 core=no cu=0 cs=10
startup='Fri Jul 7 08:48:13 2023'
tst_hugepage.c:83: TINFO: 8 hugepage(s) reserved
tst_test.c:1558: 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 5
hugemmap10.c:317: TFAIL: While initializing hugepages pool: Bad HugePages_Surp: expected 0, actual 5
Summary:
passed 0
failed 2
broken 0
skipped 0
warnings 0
tag=hugemmap10 stime=1688719693 dur=1 exit=exited stat=1 core=no cu=0 cs=26
startup='Fri Jul 7 08:49:26 2023'
tst_hugepage.c:83: TINFO: 128 hugepage(s) reserved
tst_test.c:1558: TINFO: Timeout per run is 0h 00m 30s
hugeshmctl02.c:93: TBROK: shmget #2: ENOMEM (12)
Summary:
passed 0
failed 0
broken 1
skipped 0
warnings 0
tag=hugeshmctl02 stime=1688719766 dur=4 exit=exited stat=2 core=no cu=0 cs=399
** Affects: ubuntu-kernel-tests
Importance: Undecided
Assignee: Po-Hsu Lin (cypressyew)
Status: In Progress
** Tags: 6.2 arm64 jammy sru-20230612 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/2026543
Title:
hugefork02 in ubuntu_ltp_stable/hugetlb will timeout with J-6.2 ARM64k
Status in ubuntu-kernel-tests:
In Progress
Bug description:
This issue can be found on J-6.2 generic / lowlatency ARM64k with node
wright-kernel.
It feels likes a hw-specific issue, test passed with L-generic ARM64k
starmie-kernel (for L-lowlatency ARM64k scobee-kernel, test was unable
to start due to a hang in dio test)
When this happens, it will cause failures to these tests as well:
hugemmap05 hugemmap05_1 hugemmap10 hugeshmctl02
Test log:
startup='Fri Jul 7 08:47:20 2023'
tst_hugepage.c:83: TINFO: 5 hugepage(s) reserved
tst_test.c:1558: TINFO: Timeout per run is 0h 00m 30s
Test timeouted, sending SIGKILL!
tst_test.c:1606: TINFO: Killed the leftover descendant processes
tst_test.c:1612: TINFO: If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1
tst_test.c:1614: TBROK: Test killed! (timeout?)
Summary:
passed 0
failed 0
broken 1
skipped 0
warnings 0
tag=hugefork02 stime=1688719640 dur=31 exit=exited stat=2 core=no cu=0 cs=20
And lead to ENOMEM to other tests:
startup='Fri Jul 7 08:48:04 2023'
tst_hugepage.c:83: TINFO: 7 hugepage(s) reserved
tst_test.c:1558: TINFO: Timeout per run is 0h 00m 30s
hugemmap05.c:225: TINFO: original nr_overcommit_hugepages is 0
hugemmap05.c:83: TBROK: mmap((nil),1610612736,3,1,8,0) failed: ENOMEM (12)
hugemmap05.c:178: TINFO: restore nr_overcommit_hugepages to 0.
Summary:
passed 0
failed 0
broken 1
skipped 0
warnings 0
tag=hugemmap05 stime=1688719684 dur=0 exit=exited stat=2 core=no cu=0 cs=10
startup='Fri Jul 7 08:49:00 2023'
tst_hugepage.c:83: TINFO: 7 hugepage(s) reserved
tst_test.c:1558: TINFO: Timeout per run is 0h 00m 30s
hugemmap05.c:225: TINFO: original nr_overcommit_hugepages is 0
hugemmap05.c:79: TBROK: shmget(219611296, 1610612736, b80) failed: ENOMEM (12)
hugemmap05.c:178: TINFO: restore nr_overcommit_hugepages to 0.
Summary:
passed 0
failed 0
broken 1
skipped 0
warnings 0
tag=hugemmap05_1 stime=1688719740 dur=0 exit=exited stat=2 core=no cu=0 cs=10
startup='Fri Jul 7 08:48:13 2023'
tst_hugepage.c:83: TINFO: 8 hugepage(s) reserved
tst_test.c:1558: 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 5
hugemmap10.c:317: TFAIL: While initializing hugepages pool: Bad HugePages_Surp: expected 0, actual 5
Summary:
passed 0
failed 2
broken 0
skipped 0
warnings 0
tag=hugemmap10 stime=1688719693 dur=1 exit=exited stat=1 core=no cu=0 cs=26
startup='Fri Jul 7 08:49:26 2023'
tst_hugepage.c:83: TINFO: 128 hugepage(s) reserved
tst_test.c:1558: TINFO: Timeout per run is 0h 00m 30s
hugeshmctl02.c:93: TBROK: shmget #2: ENOMEM (12)
Summary:
passed 0
failed 0
broken 1
skipped 0
warnings 0
tag=hugeshmctl02 stime=1688719766 dur=4 exit=exited stat=2 core=no cu=0 cs=399
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2026543/+subscriptions
Follow ups