Public bug reported:

There were some recent changes on the main kernels to fix some syntax
issues with the annotations files (Propagate "Update annotations and fix
errors" to all derivatives), after I replicated the changes from
bionic/linux to bionic/linux-raspi2 I started getting this enforcement

check-config: FAIL (y != n): CONFIG_LATENCYTOP policy<{'amd64-generic': 'n', 
'amd64-lowlatency': 'y', 'arm64': 'n', 'armhf': 'n', 'i386': 'n', 'ppc64el': 
'n', 's390x': 'n'}> mark<ENFORCED> 
It seems we were supposed to have the same enforcement as the main kernel (= n) 
but the raspi2 config has it actually enabled.

Looking at the url and the bug reference on the enforcement notes, it
seems it doesn't make much sense to keep it enabled for non-lowlatency

@juerghaefliger confirmed we should disable this option:

Yes, it should be disabled. I did the same for hirsute earlier this year after 
Seth fixed the master config annotations:
~ubuntu-kernel/ubuntu/+source/linux-raspi/+git/hirsute - [no description]

If I remember correctly I made some other config changes due to Seth's

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: Incomplete

You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

  CONFIG_LATENCYTOP should be disabled

To manage notifications about this bug go to:

ubuntu-bugs mailing list

Reply via email to