vma05 in mm from ubuntu_ltp failed on 5.3 / 5.4 kernel
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-kernel-tests |
Fix Released
|
Undecided
|
Po-Hsu Lin | ||
linux (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
linux-oracle (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Test failed with:
tag=vma05 stime=1568998082 dur=0 exit=exited stat=1 core=no cu=23 cs=4
Need to check if it has something to do with AppArmor
startup='Fri Sep 20 16:48:02 2019'
vma05 1 TINFO: timeout per run is 0h 5m 0s
vma05 1 TFAIL: [vsyscall] reporting wrong
vma05 1 TPASS: [vdso] backtrace complete
vma05 2 TINFO: AppArmor enabled, this may affect test results
vma05 2 TINFO: it can be disabled with TST_DISABLE_
vma05 2 TINFO: loaded AppArmor profiles: none
Summary:
passed 1
failed 1
skipped 0
warnings 0
tag=vma05 stime=1568998082 dur=0 exit=exited stat=1 core=no cu=23 cs=4
startup='Fri Sep 20 16:48:02 2019'
vma05 1 TINFO: timeout per run is 0h 5m 0s
vma05 1 TFAIL: [vsyscall] reporting wrong
vma05 1 TPASS: [vdso] backtrace complete
vma05 2 TINFO: AppArmor enabled, this may affect test results
vma05 2 TINFO: it can be disabled with TST_DISABLE_
vma05 2 TINFO: loaded AppArmor profiles: none
Summary:
passed 1
failed 1
skipped 0
warnings 0
tags: | added: 5.3 amd64 bionic sru-20190902 ubuntu-ltp |
tags: | added: oracle |
tags: | added: sru-20191021 |
Changed in ubuntu-kernel-tests: | |
status: | New → Triaged |
tags: | added: eoan |
tags: | added: sru-20191111 |
tags: | added: aws azure |
tags: | added: sru |
tags: | removed: sru |
summary: |
- vma05 in mm from ubuntu_ltp failed on B-hwe-edge 5.3 + vma05 in mm from ubuntu_ltp failed on 5.3 kernel |
tags: | added: sru-20191202 |
tags: | added: sru-20200316 |
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1845863
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.