This is fixed in 2.23-0ubuntu11
** Changed in: glibc (Ubuntu)
Status: New => Fix Released
** Changed in: intel
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: glibc (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783043
Title:
GLIBC High Power License Fix
** Changed in: intel
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783043
Title:
GLIBC High Power License Fix for Ubuntu 16.04.4
To manage
** Changed in: intel
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783043
Title:
GLIBC High Power License Fix for Ubuntu 16.04.4
To manage notifications
hi, Joe
The issue is broader than this particular use case. Without H.J.'s fix,
most of the workloads will probably run at an unnecessary high power
license level, preventing the CPU to scale up to the maximum frequency.
I suggest Ubuntu take this patch into 16.04.4 to provide strong support
for
