| Fedora Test Day | |
|---|---|
| |
| Kernel 5.6 | |
| Date | 2020-04-13 to 2020-04-20 |
| Time | all week |
| Website | QA/Test Days |
| IRC | #fedora-test-day (webirc) |
| Mailing list | test |
If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at Bugzilla, and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule and see if a similar but more recent Test Day is planned or has already happened.
What to test?
Today's installment of Fedora Test Day will focus on Kernel 5.6.
Who's available?
The following cast of characters will be available for testing, workarounds, bug fixes, and general discussion ...
- Development - jforbes (jforbes)
- Quality Assurance - Sumantro Mukherjee (sumantrom), Adam Williamson (adamw), Geoff (coremodule), Lukáš Růžička (lruzicka)
Prerequisites for Test Day
- A fully updated test day image or Fedora 30 or 31 Workstation/Server installation, either on bare metal or VM (please make sure you have no important data on that installation, things might go wrong -- don't do this on your production machine!)
- The 5.6 kernel for an existing installation from F31 koji or kernel-stabilization copr if not using the test day image. (koji is recommended for secure boot users). This kernel should install fine on F30 systems.
- As this is the Fedora 32 shipping kernel, you can also test with any of the Fedora 32 nightlies
- Fedora Silverblue users can test using the koji kernel above as well. Download the kernel locally and install it with rpm-ostree override replace <path to package>
- Enough free space on HDD
How to test?
Run the tests
- Follow the instructions in this test case. For users running the test day image, the tests are pre-installed in
/home/liveuser/kernel-tests/. - Visit the result page and enter your result in the 'Regression' column by clicking Enter result.
- If there are any other result columns, click on the column title links to see the tests that need to be run: most column titles are links to a specific test case. Follow the instructions there, then enter your results by clicking the Enter result button for the test.
- While the results from the regression tests are interesting, we are also interested in your overall experience with the new kernels.
Reporting bugs
If you have problems with any of the tests, have a look in the results page. Please include the vulnerability output at the end of the test suite in the comments.
If you don't see it, please file a new bug to Bugzilla, probably against kernel component. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC #fedora-test-day or #fedora-qa and we will help you.
Test Results
Regression Test
| User | Profile | Regression | References |
|---|---|---|---|
| sumantrom | KVM on T460s |  |
|
| udb28 | liveusb on T430s |  Default test suite. Vulnerability status: /sys/devices/system/cpu/vulnerabilities/itlb_multihit:KVM: Vulnerable /sys/devices/system/cpu/vulnerabilities/l1tf:Mitigation: PTE Inversion /sys/devices/system/cpu/vulnerabilities/mds:Mitigation: Clear CPU buffers; SMT vulnerable /sys/devices/system/cpu/vulnerabilities/meltdown:Mitigation: PTI /sys/devices/system/cpu/vulnerabilities/spec_store_bypass:Mitigation: Speculative Store Bypass disabled via prctl and seccomp /sys/devices/system/cpu/vulnerabilities/spectre_v1:Mitigation: usercopy/swapgs barriers and __user pointer sanitization /sys/devices/system/cpu/vulnerabilities/spectre_v2:Mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB filling /sys/devices/system/cpu/vulnerabilities/tsx_async_abort:Not affected |
- ↑ this is just an example