Thanks Heiko, I just looked the patch(commit-ID up in the ubuntu master-
next git trees of the Ubuntu releases that are in service.
In Eoan this patch is already addressed by:
LP 1851550: Eoan update: 5.3.9 upstream stable release
Hence, adapting the status from LP 1851550 (currently Fix Committed) to the
Eoan entry here.
In Disco this patch is already addressed by:
LP 1853067: Disco update: upstream stable patchset 2019-11-18
Hence, adapting the status from LP 1853067 (currently Fix Committed) to the
Disco entry here.
In Bionic this patch is already addressed by:
LP 1852492: Bionic update: upstream stable patchset 2019-11-13
Hence, adapting the status from LP 1852492 (currently Fix Committed) to the
Bionic entry here.
In addition, the target kernel for Focus is 5.4; and the patch here got
upstream accepted with 5.4, hence changing the Focal entry here to
Confirmed.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu Bionic)
Status: New => Fix Committed
** Changed in: linux (Ubuntu Disco)
Status: New => Fix Committed
** Changed in: linux (Ubuntu Eoan)
Status: New => Fix Committed
** Changed in: ubuntu-z-systems
Status: Incomplete => Fix Committed
--
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/1854059
Title:
[UBUNTU] kernel: cpu idle time calculation
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Disco:
Fix Committed
Status in linux source package in Eoan:
Fix Committed
Bug description:
Description: kernel: cpu idle time calculation
Symptom: The cpu idle time reported within /proc/stat as well as in
/sys/devices/system/cpu/cpuX/idle_time_us sometimes may
show incorrect values.
Problem: The kernel tries to figure out when a cpu entered idle
by accessing its per-cpu data structure. There is an
ordering problem: if a remote cpu has an idle_enter
value which is not zero, and an idle_exit value which
is zero, it is assumed it is idle since "now". The
"now" timestamp however is taken before the idle_enter
value is read.
This in turn means that "now" can be smaller than
idle_enter of the remote cpu. Unconditionally
subtracting idle_enter from "now" can thus lead to a
negative value (aka large unsigned value).
Solution: Move the get_tod_clock() invocation.
Upstream-ID:
https://github.com/torvalds/linux/commit/3d7efa4edd07be5c5c3ffa95ba63e97e070e1f3f
Patch tagged as "stable".
Tracking the integration of this patch in the relevant distros..
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1854059/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
