Bios is not setting CPU cores to maximum frequency

Bug #1839166 reported by Brahamaprakash Vardhaman
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

We are hitting below customer issue as explained briefly below.


UCS C220 M5
Firmware 4.0(2f) - standalone
Ubuntu 16.04.5 LTS with 4.15.0-29-generic kernel (HWE)

The customer is looking to force the CPU frequency to stay on max value. Ubuntu detects variable speeds (the CPU cores are going down to 800 MHz):

Bios is not setting all CPU cores to maximum frequency in Ubuntu.
Bios settings are as below.

- Disabled Intel speedstep
- Disabled TurboBoost
- Limited to C0/C1 only with disabled extended states
- Disabled P states, or reduced as much as possible
- Set profiles to max performance
- Control for CPU performance is done via BIOS, not OS
- CPU performance is Enterprise

The issue is also not seen on another C220 M5SX without NVMe drives running 3.1(3i). Same kernel version for Ubuntu.
Downgrading the firmware on one of the affected C220 M5s doesn't resolve the issue.”

All the cores are running on max frequency after applying the below command at the OS level:

tuned-adm profile latency-performance

So please let us know is this BIOS or Ubuntu issue?

I . will attach logs soon.

Tags: bionic
Revision history for this message
Jeff Lane  (bladernr) wrote :

Something tells me this is not filed against the right project, and likely will not get the attention it deserves until it is moved to the correct project.

Changed in bugzilla-traceparser:
status: New → Incomplete
affects: bugzilla-traceparser → umkl
Changed in umkl:
status: Incomplete → New
Revision history for this message
Jeff Lane  (bladernr) wrote :

Moved to correct project

affects: umkl → linux (Ubuntu)
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1839166

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: bionic
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.