| 2022-11-03 12:57:01 |
koba |
bug |
|
|
added bug |
| 2022-11-03 12:57:27 |
koba |
description |
[Justification]
The purpose of this bug is that prevent the regression in the future.
The automatic test scripts are better for the future SRU and is still on the planning.
Currently, just use a stressing tools and monitor status manually(e.g. s-tui).
Use stress-ng to stress the machine and observe the temperature/frequency/power.
The whole test cases are the followings,
1. check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly.
2. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly.
3. Run unit tests, the scripts are under test folder, using emul_temp to simulate the High temperatue and check thermald would throttle CPU through the related cooling device.
a. rapl.sh
b. intel_pstate.sh
c. powerclamp.sh
d. processor.sh
4. check if the power/frequency would be throttled once the temperature reach the trip-points of thermal zone.
5. check if system would be throttled even the temperature is under the thrip-poits.
/dev/acpi_thermal_rel |
[Justification]
The purpose of this bug is that prevent the regression in the future.
The automatic test scripts are better for the future SRU and is still on the planning.
Currently, just use a stressing tools and monitor status manually(e.g. s-tui).
Use stress-ng to stress the machine and observe the temperature/frequency/power.
The whole test cases are the followings,
1. check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly.
2. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly.
3. Run unit tests, the scripts are under test folder, using emul_temp to simulate the High temperatue and check thermald would throttle CPU through the related cooling device.
a. rapl.sh
b. intel_pstate.sh
c. powerclamp.sh
d. processor.sh
4. check if the power/frequency would be throttled once the temperature reach the trip-points of thermal zone.
5. check if system would be throttled even the temperature is under the thrip-poits. |
|
| 2022-11-03 13:07:28 |
koba |
description |
[Justification]
The purpose of this bug is that prevent the regression in the future.
The automatic test scripts are better for the future SRU and is still on the planning.
Currently, just use a stressing tools and monitor status manually(e.g. s-tui).
Use stress-ng to stress the machine and observe the temperature/frequency/power.
The whole test cases are the followings,
1. check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly.
2. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly.
3. Run unit tests, the scripts are under test folder, using emul_temp to simulate the High temperatue and check thermald would throttle CPU through the related cooling device.
a. rapl.sh
b. intel_pstate.sh
c. powerclamp.sh
d. processor.sh
4. check if the power/frequency would be throttled once the temperature reach the trip-points of thermal zone.
5. check if system would be throttled even the temperature is under the thrip-poits. |
[Justification]
The purpose of this bug is that prevent the regression in the future.
The automatic test scripts are better for the future SRU and is still on the planning.
Currently, just use a stressing tools and monitor status manually(e.g. s-tui).
Use stress-ng to stress the machine and observe the temperature/frequency/power.
The whole test cases are the followings and run on the platforms, RPL/ADL/TGL/CML/CFL/KBL.
1. check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly.
2. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly.
3. Run unit tests, the scripts are under test folder, using emul_temp to simulate the High temperatue and check thermald would throttle CPU through the related cooling device.
a. rapl.sh
b. intel_pstate.sh
c. powerclamp.sh
d. processor.sh
4. check if the power/frequency would be throttled once the temperature reach the trip-points of thermal zone.
5. check if system would be throttled even the temperature is under the thrip-poits. |
|
| 2022-11-03 13:08:07 |
koba |
thermald (Ubuntu): assignee |
|
koba (kobako) |
|
| 2022-11-03 13:08:12 |
koba |
thermald (Ubuntu): status |
New |
In Progress |
|
| 2022-11-03 13:22:38 |
koba |
description |
[Justification]
The purpose of this bug is that prevent the regression in the future.
The automatic test scripts are better for the future SRU and is still on the planning.
Currently, just use a stressing tools and monitor status manually(e.g. s-tui).
Use stress-ng to stress the machine and observe the temperature/frequency/power.
The whole test cases are the followings and run on the platforms, RPL/ADL/TGL/CML/CFL/KBL.
1. check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly.
2. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly.
3. Run unit tests, the scripts are under test folder, using emul_temp to simulate the High temperatue and check thermald would throttle CPU through the related cooling device.
a. rapl.sh
b. intel_pstate.sh
c. powerclamp.sh
d. processor.sh
4. check if the power/frequency would be throttled once the temperature reach the trip-points of thermal zone.
5. check if system would be throttled even the temperature is under the thrip-poits. |
[Justification]
The purpose of this bug is that prevent the regression in the future.
The automatic test scripts are better for the future SRU and is still on the planning.
Currently, just use stress-ng and observe the temperature/frequency/power manually(e.g. s-tui).
The whole test cases are the followings and run on the platforms, RPL/ADL/TGL/CML/CFL/KBL.
1. check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly.
2. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly.
3. Run unit tests, the scripts are under test folder, using emul_temp to simulate the High temperatue and check thermald would throttle CPU through the related cooling device.
a. rapl.sh
b. intel_pstate.sh
c. powerclamp.sh
d. processor.sh
4. check if the power/frequency would be throttled once the temperature reach the trip-points of thermal zone.
5. check if system would be throttled even the temperature is under the thrip-poits. |
|
| 2022-11-04 08:53:03 |
Chris Halse Rogers |
description |
[Justification]
The purpose of this bug is that prevent the regression in the future.
The automatic test scripts are better for the future SRU and is still on the planning.
Currently, just use stress-ng and observe the temperature/frequency/power manually(e.g. s-tui).
The whole test cases are the followings and run on the platforms, RPL/ADL/TGL/CML/CFL/KBL.
1. check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly.
2. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly.
3. Run unit tests, the scripts are under test folder, using emul_temp to simulate the High temperatue and check thermald would throttle CPU through the related cooling device.
a. rapl.sh
b. intel_pstate.sh
c. powerclamp.sh
d. processor.sh
4. check if the power/frequency would be throttled once the temperature reach the trip-points of thermal zone.
5. check if system would be throttled even the temperature is under the thrip-poits. |
[Justification]
The purpose of this bug is that prevent the regression in the future.
The automatic test scripts are better for the future SRU and is still on the planning.
[Test case]
For each supported CPU series (RPL/ADL/TGL/CML/CFL/KBL) the following tests will be run on machines in the CI lab:
* Run stress-ng, and observe the temperature/frequency/power with s-tui
- Temperatures should stay just below trip values
- Power/performance profiles should stay roughly the same between old thermald and new thermald (unless specifically expected eg: to fix premature/insufficient throttling)
* check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly.
- (TODO: What are the concrete steps to check this?)
* check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly.
- (TODO: How do we check this)
* Run unit tests, the scripts are under test folder, using emul_temp to simulate the High temperatue and check thermald would throttle CPU through the related cooling device.
- rapl.sh
- intel_pstate.sh
- powerclamp.sh
- processor.sh
* check if the power/frequency would be throttled once the temperature reach the trip-points of thermal zone.
* check if system would be throttled even the temperature is under the thrip-poits. |
|
| 2022-11-04 09:12:42 |
koba |
description |
[Justification]
The purpose of this bug is that prevent the regression in the future.
The automatic test scripts are better for the future SRU and is still on the planning.
[Test case]
For each supported CPU series (RPL/ADL/TGL/CML/CFL/KBL) the following tests will be run on machines in the CI lab:
* Run stress-ng, and observe the temperature/frequency/power with s-tui
- Temperatures should stay just below trip values
- Power/performance profiles should stay roughly the same between old thermald and new thermald (unless specifically expected eg: to fix premature/insufficient throttling)
* check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly.
- (TODO: What are the concrete steps to check this?)
* check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly.
- (TODO: How do we check this)
* Run unit tests, the scripts are under test folder, using emul_temp to simulate the High temperatue and check thermald would throttle CPU through the related cooling device.
- rapl.sh
- intel_pstate.sh
- powerclamp.sh
- processor.sh
* check if the power/frequency would be throttled once the temperature reach the trip-points of thermal zone.
* check if system would be throttled even the temperature is under the thrip-poits. |
[Justification]
The purpose of this bug is that prevent the regression in the future.
The automatic test scripts are better for the future SRU and is still on the planning.
[Test case]
For each supported CPU series (RPL/ADL/TGL/CML/CFL/KBL) the following tests will be run on machines in the CI lab:
* Run stress-ng, and observe the temperature/frequency/power with s-tui
- Temperatures should stay just below trip values
- Power/performance profiles should stay roughly the same between old thermald and new thermald (unless specifically expected eg: to fix premature/insufficient throttling)
* check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly.
- this depends on if acpi_thermal_rel exist.
- if the machine suppots acpi_thermal_rel, the "thermal-conf.xml.auto"
could be landed in etc/thermald/.
- run thermald with --loglevel=debug, and compare the log with xml.auto file.
check if the configuration could be parsed correctly.
* check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly.
- run thermald with --loglevel=debug, and compare the log with xml files.
- if parsed correctly, the configurations from XML files would appear in the log.
* Run unit tests, the scripts are under test folder, using emul_temp to simulate the High temperatue and check thermald would throttle CPU through the related cooling device.
- rapl.sh
- intel_pstate.sh
- powerclamp.sh
- processor.sh
* check if the power/frequency would be throttled once the temperature reach the trip-points of thermal zone.
* check if system would be throttled even the temperature is under the thrip-poits. |
|
| 2022-11-04 09:15:09 |
koba |
description |
[Justification]
The purpose of this bug is that prevent the regression in the future.
The automatic test scripts are better for the future SRU and is still on the planning.
[Test case]
For each supported CPU series (RPL/ADL/TGL/CML/CFL/KBL) the following tests will be run on machines in the CI lab:
* Run stress-ng, and observe the temperature/frequency/power with s-tui
- Temperatures should stay just below trip values
- Power/performance profiles should stay roughly the same between old thermald and new thermald (unless specifically expected eg: to fix premature/insufficient throttling)
* check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly.
- this depends on if acpi_thermal_rel exist.
- if the machine suppots acpi_thermal_rel, the "thermal-conf.xml.auto"
could be landed in etc/thermald/.
- run thermald with --loglevel=debug, and compare the log with xml.auto file.
check if the configuration could be parsed correctly.
* check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly.
- run thermald with --loglevel=debug, and compare the log with xml files.
- if parsed correctly, the configurations from XML files would appear in the log.
* Run unit tests, the scripts are under test folder, using emul_temp to simulate the High temperatue and check thermald would throttle CPU through the related cooling device.
- rapl.sh
- intel_pstate.sh
- powerclamp.sh
- processor.sh
* check if the power/frequency would be throttled once the temperature reach the trip-points of thermal zone.
* check if system would be throttled even the temperature is under the thrip-poits. |
[Justification]
The purpose of this bug is that prevent the regression in the future.
The automatic test scripts are better for the future SRU and is still on the planning.
[Test case]
For each supported CPU series (RPL/ADL/TGL/CML/CFL/KBL) the following tests will be run on machines in the CI lab:
1. Run stress-ng, and observe the temperature/frequency/power with s-tui
- Temperatures should stay just below trip values
- Power/performance profiles should stay roughly the same between old thermald and new thermald (unless specifically expected eg: to fix premature/insufficient throttling)
2. check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly.
- this depends on if acpi_thermal_rel exist.
- if the machine suppots acpi_thermal_rel, the "thermal-conf.xml.auto"
could be landed in etc/thermald/.
- if not, the user-defined xml could be created, then jump to (3).
- run thermald with --loglevel=debug, and compare the log with xml.auto file.
check if the configuration could be parsed correctly.
3. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly.
- run thermald with --loglevel=debug, and compare the log with xml files.
- if parsed correctly, the configurations from XML files would appear in the log.
4. Run unit tests, the scripts are under test folder, using emul_temp to simulate the High temperatue and check thermald would throttle CPU through the related cooling device.
- rapl.sh
- intel_pstate.sh
- powerclamp.sh
- processor.sh
5. check if the power/frequency would be throttled once the temperature reach the trip-points of thermal zone.
6. check if system would be throttled even the temperature is under the thrip-poits. |
|
| 2022-11-04 09:17:31 |
koba |
description |
[Justification]
The purpose of this bug is that prevent the regression in the future.
The automatic test scripts are better for the future SRU and is still on the planning.
[Test case]
For each supported CPU series (RPL/ADL/TGL/CML/CFL/KBL) the following tests will be run on machines in the CI lab:
1. Run stress-ng, and observe the temperature/frequency/power with s-tui
- Temperatures should stay just below trip values
- Power/performance profiles should stay roughly the same between old thermald and new thermald (unless specifically expected eg: to fix premature/insufficient throttling)
2. check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly.
- this depends on if acpi_thermal_rel exist.
- if the machine suppots acpi_thermal_rel, the "thermal-conf.xml.auto"
could be landed in etc/thermald/.
- if not, the user-defined xml could be created, then jump to (3).
- run thermald with --loglevel=debug, and compare the log with xml.auto file.
check if the configuration could be parsed correctly.
3. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly.
- run thermald with --loglevel=debug, and compare the log with xml files.
- if parsed correctly, the configurations from XML files would appear in the log.
4. Run unit tests, the scripts are under test folder, using emul_temp to simulate the High temperatue and check thermald would throttle CPU through the related cooling device.
- rapl.sh
- intel_pstate.sh
- powerclamp.sh
- processor.sh
5. check if the power/frequency would be throttled once the temperature reach the trip-points of thermal zone.
6. check if system would be throttled even the temperature is under the thrip-poits. |
[Justification]
The purpose of this bug is that prevent the regression in the future.
The automatic test scripts are better for the future SRU and is still on the planning.
[Test case]
For each supported CPU series (RPL/ADL/TGL/CML/CFL/KBL) the following tests will be run on machines in the CI lab:
1. Run stress-ng, and observe the temperature/frequency/power with s-tui
- Temperatures should stay just below trip values
- Power/performance profiles should stay roughly the same between old thermald and new thermald (unless specifically expected eg: to fix premature/insufficient throttling)
2. check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly.
- this depends on if acpi_thermal_rel exist.
- if the machine suppots acpi_thermal_rel, the "thermal-conf.xml.auto"
could be landed in etc/thermald/.
- if not, the user-defined xml could be created, then jump to (3).
- run thermald with --loglevel=debug, and compare the log with xml.auto file. check if the configuration could be parsed correctly.
3. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly.
- run thermald with --loglevel=debug, and compare the log with xml files.
- if parsed correctly, the configurations from XML files would appear in the log.
4. Run unit tests, the scripts are under test folder, using emul_temp to simulate the High temperatue and check thermald would throttle CPU through the related cooling device.
- rapl.sh
- intel_pstate.sh
- powerclamp.sh
- processor.sh
5. check if the power/frequency would be throttled once the temperature reach the trip-points of thermal zone.
6. check if system would be throttled even the temperature is under the thrip-poits. |
|
| 2022-11-04 10:58:51 |
Timo Aaltonen |
nominated for series |
|
Ubuntu Jammy |
|
| 2022-11-04 10:58:51 |
Timo Aaltonen |
bug task added |
|
thermald (Ubuntu Jammy) |
|
| 2022-11-04 10:58:59 |
Timo Aaltonen |
thermald (Ubuntu): status |
In Progress |
Fix Released |
|
| 2022-11-04 10:59:04 |
Timo Aaltonen |
thermald (Ubuntu Jammy): status |
New |
In Progress |
|
| 2022-11-04 11:13:34 |
koba |
description |
[Justification]
The purpose of this bug is that prevent the regression in the future.
The automatic test scripts are better for the future SRU and is still on the planning.
[Test case]
For each supported CPU series (RPL/ADL/TGL/CML/CFL/KBL) the following tests will be run on machines in the CI lab:
1. Run stress-ng, and observe the temperature/frequency/power with s-tui
- Temperatures should stay just below trip values
- Power/performance profiles should stay roughly the same between old thermald and new thermald (unless specifically expected eg: to fix premature/insufficient throttling)
2. check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly.
- this depends on if acpi_thermal_rel exist.
- if the machine suppots acpi_thermal_rel, the "thermal-conf.xml.auto"
could be landed in etc/thermald/.
- if not, the user-defined xml could be created, then jump to (3).
- run thermald with --loglevel=debug, and compare the log with xml.auto file. check if the configuration could be parsed correctly.
3. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly.
- run thermald with --loglevel=debug, and compare the log with xml files.
- if parsed correctly, the configurations from XML files would appear in the log.
4. Run unit tests, the scripts are under test folder, using emul_temp to simulate the High temperatue and check thermald would throttle CPU through the related cooling device.
- rapl.sh
- intel_pstate.sh
- powerclamp.sh
- processor.sh
5. check if the power/frequency would be throttled once the temperature reach the trip-points of thermal zone.
6. check if system would be throttled even the temperature is under the thrip-poits. |
[Justification]
The purpose of this bug is that prevent the regression in the future.
The automatic test scripts are better for the future SRU and is still on the planning.
[Test case]
For each supported CPU series (RPL/ADL/TGL/CML/CFL/KBL) the following tests will be run on machines in the CI lab:
1. Run stress-ng, and observe the temperature/frequency/power with s-tui
- Temperatures should stay just below trip values
- Power/performance profiles should stay roughly the same between old thermald and new thermald (unless specifically expected eg: to fix premature/insufficient throttling)
2. check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly.
- this depends on if acpi_thermal_rel exist.
- if the machine suppots acpi_thermal_rel, the "thermal-conf.xml.auto"
could be landed in etc/thermald/.
- if not, the user-defined xml could be created, then jump to (3).
- run thermald with --loglevel=debug, and compare the log with xml.auto file. check if the configuration could be parsed correctly.
3. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly.
- run thermald with --loglevel=debug, and compare the log with xml files.
- if parsed correctly, the configurations from XML files would appear in the log.
4. Run unit tests, the scripts are under test folder, using emul_temp to simulate the High temperatue and check thermald would throttle CPU through the related cooling device.
- rapl.sh
- intel_pstate.sh
- powerclamp.sh
- processor.sh
5. check if the power/frequency would be throttled once the temperature reach the trip-points of thermal zone.
6. check if system would be throttled even the temperature is under the trip-points.
[ Where problems could occur ] |
|
| 2022-11-06 14:16:05 |
Robie Basak |
thermald (Ubuntu Jammy): status |
In Progress |
Incomplete |
|
| 2022-11-07 01:35:25 |
koba |
description |
[Justification]
The purpose of this bug is that prevent the regression in the future.
The automatic test scripts are better for the future SRU and is still on the planning.
[Test case]
For each supported CPU series (RPL/ADL/TGL/CML/CFL/KBL) the following tests will be run on machines in the CI lab:
1. Run stress-ng, and observe the temperature/frequency/power with s-tui
- Temperatures should stay just below trip values
- Power/performance profiles should stay roughly the same between old thermald and new thermald (unless specifically expected eg: to fix premature/insufficient throttling)
2. check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly.
- this depends on if acpi_thermal_rel exist.
- if the machine suppots acpi_thermal_rel, the "thermal-conf.xml.auto"
could be landed in etc/thermald/.
- if not, the user-defined xml could be created, then jump to (3).
- run thermald with --loglevel=debug, and compare the log with xml.auto file. check if the configuration could be parsed correctly.
3. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly.
- run thermald with --loglevel=debug, and compare the log with xml files.
- if parsed correctly, the configurations from XML files would appear in the log.
4. Run unit tests, the scripts are under test folder, using emul_temp to simulate the High temperatue and check thermald would throttle CPU through the related cooling device.
- rapl.sh
- intel_pstate.sh
- powerclamp.sh
- processor.sh
5. check if the power/frequency would be throttled once the temperature reach the trip-points of thermal zone.
6. check if system would be throttled even the temperature is under the trip-points.
[ Where problems could occur ] |
[Justification]
The purpose of this bug is that prevent the regression in the future.
The automatic test scripts are better for the future SRU and is still on the planning.
[Test case]
For each supported CPU series (RPL/ADL/TGL/CML/CFL/KBL) the following tests will be run on machines in the CI lab:
1. Run stress-ng, and observe the temperature/frequency/power with s-tui
- Temperatures should stay just below trip values
- Power/performance profiles should stay roughly the same between old thermald and new thermald (unless specifically expected eg: to fix premature/insufficient throttling)
2. check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly.
- this depends on if acpi_thermal_rel exist.
- if the machine suppots acpi_thermal_rel, the "thermal-conf.xml.auto"
could be landed in etc/thermald/.
- if not, the user-defined xml could be created, then jump to (3).
- run thermald with --loglevel=debug, and compare the log with xml.auto file. check if the configuration could be parsed correctly.
3. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly.
- run thermald with --loglevel=debug, and compare the log with xml files.
- if parsed correctly, the configurations from XML files would appear in the log.
4. Run unit tests, the scripts are under test folder, using emul_temp to simulate the High temperatue and check thermald would throttle CPU through the related cooling device.
- rapl.sh
- intel_pstate.sh
- powerclamp.sh
- processor.sh
5. check if the power/frequency would be throttled once the temperature reach the trip-points of thermal zone.
6. check if system would be throttled even the temperature is under the trip-points.
[ Where problems could occur ]
since the PL1 min/max is introduced, we may face the edge case in the future. |
|
| 2022-11-09 13:40:08 |
koba |
bug |
|
|
added subscriber Srinivas Pandruvada |
| 2022-11-10 15:00:33 |
koba |
description |
[Justification]
The purpose of this bug is that prevent the regression in the future.
The automatic test scripts are better for the future SRU and is still on the planning.
[Test case]
For each supported CPU series (RPL/ADL/TGL/CML/CFL/KBL) the following tests will be run on machines in the CI lab:
1. Run stress-ng, and observe the temperature/frequency/power with s-tui
- Temperatures should stay just below trip values
- Power/performance profiles should stay roughly the same between old thermald and new thermald (unless specifically expected eg: to fix premature/insufficient throttling)
2. check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly.
- this depends on if acpi_thermal_rel exist.
- if the machine suppots acpi_thermal_rel, the "thermal-conf.xml.auto"
could be landed in etc/thermald/.
- if not, the user-defined xml could be created, then jump to (3).
- run thermald with --loglevel=debug, and compare the log with xml.auto file. check if the configuration could be parsed correctly.
3. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly.
- run thermald with --loglevel=debug, and compare the log with xml files.
- if parsed correctly, the configurations from XML files would appear in the log.
4. Run unit tests, the scripts are under test folder, using emul_temp to simulate the High temperatue and check thermald would throttle CPU through the related cooling device.
- rapl.sh
- intel_pstate.sh
- powerclamp.sh
- processor.sh
5. check if the power/frequency would be throttled once the temperature reach the trip-points of thermal zone.
6. check if system would be throttled even the temperature is under the trip-points.
[ Where problems could occur ]
since the PL1 min/max is introduced, we may face the edge case in the future. |
[Justification]
The purpose of this bug is that prevent the regression in the future.
The automatic test scripts are better for the future SRU and is still on the planning.
[Test case]
For these CPU series, RPL/ADL/TGL/CML/CFL/KBL, the following tests will be run on machines in the CI lab:
1. Run stress-ng, and observe the temperature/frequency/power with s-tui
- Temperatures should stay just below trip values
- Power/performance profiles should stay roughly the same between old thermald and new thermald (unless specifically expected eg: to fix premature/insufficient throttling)
2. check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly.
- this depends on if acpi_thermal_rel exist.
- if the machine suppots acpi_thermal_rel, the "thermal-conf.xml.auto"
could be landed in etc/thermald/.
- if not, the user-defined xml could be created, then jump to (3).
- run thermald with --loglevel=debug, and compare the log with xml.auto file. check if the configuration could be parsed correctly.
3. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly.
- run thermald with --loglevel=debug, and compare the log with xml files.
- if parsed correctly, the configurations from XML files would appear in the log.
4. Run unit tests, the scripts are under test folder, using emul_temp to simulate the High temperatue and check thermald would throttle CPU through the related cooling device.
- rapl.sh
- intel_pstate.sh
- powerclamp.sh
- processor.sh
5. check if the power/frequency would be throttled once the temperature reach the trip-points of thermal zone.
6. check if system would be throttled even the temperature is under the trip-points.
[ Where problems could occur ]
since the PL1 min/max is introduced, there may have some cases that don't check the minimum of PL1 then make PL1 to smaller and smaller and throttle the CPU.
this may cause machines run like the old behavior that doesn't have PL1 min/max. |
|
| 2022-12-05 16:03:00 |
Rex Tsai |
bug task added |
|
oem-priority |
|
| 2022-12-05 16:03:08 |
Rex Tsai |
oem-priority: importance |
Undecided |
High |
|
| 2022-12-05 16:04:17 |
Rex Tsai |
tags |
|
hwe-thermal |
|
| 2022-12-05 16:04:56 |
Yuan-Chen Cheng |
tags |
hwe-thermal |
hwe-thermal oem-priority |
|
| 2022-12-05 16:07:13 |
Rex Tsai |
thermald (Ubuntu): status |
Fix Released |
New |
|
| 2022-12-05 16:07:27 |
Rex Tsai |
summary |
Upgrade thermald to 2.5.1 |
Upgrade thermald to 2.5.1 for Jammy (22.04) |
|
| 2022-12-05 16:07:36 |
Rex Tsai |
bug |
|
|
added subscriber Rex Tsai |
| 2022-12-07 10:35:14 |
Louis Magand |
bug |
|
|
added subscriber Louis Magand |
| 2023-04-04 07:58:18 |
OEM Taipei Bot |
bug |
|
|
added subscriber OEM Solutions Group: Engineers |
| 2023-04-04 07:58:21 |
OEM Taipei Bot |
tags |
hwe-thermal oem-priority |
hwe-thermal oem-priority originate-from-2015192 sutton |
|
| 2023-04-04 08:02:46 |
OEM Taipei Bot |
tags |
hwe-thermal oem-priority originate-from-2015192 sutton |
hwe-thermal oem-priority originate-from-2015192 originate-from-2015208 sutton |
|
| 2023-04-19 14:23:57 |
koba |
attachment added |
|
thermald_Jammy_2.4.9-1ubuntu0.3.debdiff https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1995606/+attachment/5665259/+files/thermald_Jammy_2.4.9-1ubuntu0.3.debdiff |
|
| 2023-04-19 16:12:27 |
Ubuntu Foundations Team Bug Bot |
tags |
hwe-thermal oem-priority originate-from-2015192 originate-from-2015208 sutton |
hwe-thermal oem-priority originate-from-2015192 originate-from-2015208 patch sutton |
|
| 2023-04-19 16:12:30 |
Ubuntu Foundations Team Bug Bot |
bug |
|
|
added subscriber Ubuntu Sponsors Team |
| 2023-04-27 07:53:21 |
koba |
thermald (Ubuntu Jammy): assignee |
|
koba (kobako) |
|
| 2023-06-21 07:42:37 |
koba |
attachment added |
|
thermald_jammy_2.4.9-1ubuntu0.3.debdiff https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1995606/+attachment/5681109/+files/thermald_jammy_2.4.9-1ubuntu0.3.debdiff |
|
| 2023-06-26 09:02:53 |
Louis Magand |
removed subscriber Louis Magand |
|
|
|
| 2023-06-27 14:49:34 |
koba |
attachment added |
|
thermald_jammy_2.4.9-1ubuntu0.3.v2.debdiff https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1995606/+attachment/5682352/+files/thermald_jammy_2.4.9-1ubuntu0.3.v2.debdiff |
|
| 2023-06-29 14:14:59 |
Julian Andres Klode |
thermald (Ubuntu Jammy): status |
Incomplete |
New |
|
| 2023-06-29 14:56:23 |
koba |
thermald (Ubuntu Jammy): status |
New |
In Progress |
|
| 2023-07-05 06:58:49 |
koba |
attachment added |
|
thermald_jammy_2.4.9-1ubuntu0.3.v3.debdiff https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1995606/+attachment/5683967/+files/thermald_jammy_2.4.9-1ubuntu0.3.v3.debdiff |
|
| 2023-07-05 11:41:52 |
Benjamin Drung |
removed subscriber Ubuntu Sponsors |
|
|
|
| 2023-07-05 11:41:58 |
Benjamin Drung |
bug |
|
|
added subscriber Benjamin Drung |
| 2023-07-06 01:39:35 |
Chris Halse Rogers |
thermald (Ubuntu Jammy): status |
In Progress |
Fix Committed |
|
| 2023-07-06 01:39:37 |
Chris Halse Rogers |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2023-07-06 01:39:41 |
Chris Halse Rogers |
bug |
|
|
added subscriber SRU Verification |
| 2023-07-06 01:39:46 |
Chris Halse Rogers |
tags |
hwe-thermal oem-priority originate-from-2015192 originate-from-2015208 patch sutton |
hwe-thermal oem-priority originate-from-2015192 originate-from-2015208 patch sutton verification-needed verification-needed-jammy |
|
| 2023-07-14 05:09:51 |
Kai-Chuan Hsieh |
tags |
hwe-thermal oem-priority originate-from-2015192 originate-from-2015208 patch sutton verification-needed verification-needed-jammy |
hwe-thermal oem-priority originate-from-2012475 originate-from-2015192 originate-from-2015208 patch somerville sutton verification-needed verification-needed-jammy |
|
| 2023-07-14 05:22:16 |
koba |
tags |
hwe-thermal oem-priority originate-from-2012475 originate-from-2015192 originate-from-2015208 patch somerville sutton verification-needed verification-needed-jammy |
hwe-thermal oem-priority originate-from-2012475 originate-from-2015192 originate-from-2015208 patch somerville sutton verification-done verification-done-jammy |
|
| 2023-07-31 09:04:30 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2023-07-31 09:05:14 |
Launchpad Janitor |
thermald (Ubuntu Jammy): status |
Fix Committed |
Fix Released |
|
| 2023-08-01 14:45:14 |
Anthony Wong |
thermald (Ubuntu): status |
New |
Fix Released |
|
| 2023-11-23 16:48:15 |
Timo Aaltonen |
oem-priority: status |
New |
Fix Released |
|
