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
error:
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>
note<https://lists.ubuntu.com/archives/kernel-team/2014-July/045006.html,
LP#1655986>
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
kernels.
@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
changes.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1928394
Title:
CONFIG_LATENCYTOP should be disabled
Status in linux package in Ubuntu:
Incomplete
Bug description:
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
error:
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>
note<https://lists.ubuntu.com/archives/kernel-team/2014-July/045006.html,
LP#1655986>
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
kernels.
@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
changes.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928394/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
