log_check / kernel_tainted test from ubuntu_boot failed on ARM64 node starmie-kernel with 5.8 generic-64k kernel (failed with flag 512)
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| ubuntu-kernel-tests |
New
|
Undecided
|
Unassigned | ||
Bug Description
Found on Focal/hwe-5.8 5.8.0-45.51~20.04.1 generic-64k, host: starmie-kernel
Though it's instead "ERROR: kernel tainted flag != 0: 512"
03/11 04:40:30 INFO |ubuntu_boo:0042| Checking kernel tainted flags in /proc/sys/
03/11 04:40:30 INFO |ubuntu_boo:0046| ERROR: kernel tainted flag != 0: 512
03/11 04:40:30 INFO |ubuntu_boo:0046|
03/11 04:40:30 ERROR| test:0414| Exception escaping from test:
Traceback (most recent call last):
File "/home/
_call_test_
File "/home/
return func(*args, **dargs)
File "/home/
postprocess_
File "/home/
self.run_
File "/home/
raise error.TestFail()
TestFail
This flag was caused by a WARNING in the boot dmesg:
WARNING: CPU: 0 PID: 1 at arch/arm64/
Which is causing failure in the log_check test.
| tags: | added: 5.8 focal sru-20210222 |
| tags: | added: groovy |
| description: | updated |
| summary: |
log_check / kernel_tainted test from ubuntu_boot failed on ARM64 node - starmie-kernel (failed with flag 512) + starmie-kernel with 5.8 generic-64k kernel (failed with flag 512) |
| tags: | added: ubuntu-boot |
| tags: | added: hwe-5.8 |
| Po-Hsu Lin (cypressyew) wrote | #2 |
| tags: | added: 4.4 xenial |
| tags: | added: sru-20210315 |
| tags: | added: hwe |
| tags: | added: riscv |
| tags: | added: sru-20210412 |
This can be found on Groovy 5.8 generic-64k kernel on starmie-kernel as well. And it can be reproduced with the generic-64k kernel in -updates (5.8.0-
Interesting part is that this issue does not exist in 5.8 generic-arm64 kernel, just in this generic-64k kernel on this specific node.
This is triggered by the following code in efi.c:
if (WARN_ONCE(