Fedora Account System
Red Hat Associate
Red Hat Customer
1. Please describe the problem: Running Kerneltest-5.1.iso for Kernel 5.1 test day. Running under VirtualBox Version 6.0.6 r130049 (Qt5.6.1) VM Settings: 2 CPU, 4GB RAM, 128MB VSGA sudo ./runtests.sh Test suite called with default ./default/paxtest PASS ./default/cachedrop PASS ./default/mq-memory-corruption PASS ./default/libhugetlbfs SKIP ./default/timer-overhead FAIL ./default/memfd PASS ./default/sysfs-perms PASS ./default/selinux-dac-controls PASS ./default/posix_timers PASS details from the kernel-tests/logs/kernel-test-1557764647.log.txt emfd: SHARE-FORK memfd: SHARE-DUP (shared file-table) memfd: SHARE-MMAP (shared file-table) memfd: SHARE-OPEN (shared file-table) memfd: SHARE-FORK (shared file-table) memfd: DONE Starting test ./default/sysfs-perms Starting test ./default/selinux-dac-controls Starting test ./default/posix_timers Testing posix timers. False negative may happen on CPU execution based timers if other threads run on the CPU... Check itimer virtual... Diff too high: 2665487..[FAIL] 2. What is the Version-Release number of the kernel: Linux localhost 5.1.1-300.fc30.x86_64 #1 SMP Sat May 11 17:15:05 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux 3. Did it work previously in Fedora? If so, what kernel version did the issue *first* appear? Old kernels are available for download at https://koji.fedoraproject.org/koji/packageinfo?packageID=8 : 4. Can you reproduce this issue? If so, please provide the steps to reproduce the issue below: 5. Does this problem occur with the latest Rawhide kernel? To install the Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by ``sudo dnf update --enablerepo=rawhide kernel``: 6. Are you running any modules that not shipped with directly Fedora's kernel?: 7. Please attach the kernel logs. You can get the complete kernel log for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the issue occurred on a previous boot, use the journalctl ``-b`` flag.
This report has not received an update in over 90 days. If this issue is still relevant to you, please do not hesitate to update this report with any relevant details on recent investigative steps or changes and we will absolutely work to understand how to best move forward. Otherwise, this bug report will need to be closed in 30 days. No worries, however; should you need still assistance after the report is closed, please do not hesitate to create a new bug report referencing this report and with any new details on the matter. NOTE: This is an automated mass update.