Tmon test case failed - max_state is 0 - common issue for all platforms
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
intel |
Fix Committed
|
Undecided
|
Unassigned | ||
Ubuntu |
New
|
Undecided
|
Unassigned |
Bug Description
Description:
Platform:ADLN02
BIOS:5.25
Processor:Genuine Intel(R) 0000
Kernel:Linux 6.2.0+
OS:UBUNTU2304-
Tmon max_state show 0 and can't change with user guide.
This is a regression.
> Starting from commit c408b3d1d9bb(
> cur_state_store()") and commit a365105c685c(
> cdev->max_state"), the cdev->get_
> during cooling device registration.
>
> This is done to fix the below Smatch static checker warning:
> drivers/
> thermal_
> warn: potential integer overflow from user 'stats->state *
> stats->max_states + new_state'
> reported here https:/
>
> But this actually breaks cooling devices which could have dynamic max
> cooling state, like ACPI processor cooling device.
>
> acpi_processor_
> driver_
> acpi_processor_
> acpi_processor_
> thermal_
> processor_
> acpi_processor_
> The driver doesn't count cpufreq as cooling state until
> acpi_processor_
>
> As a result, without the commits above,
> /sys/class/
> /sys/class/
> /sys/class/
> after the commits above,
> /sys/class/
> /sys/class/
> /sys/class/
Reproduce steps:
1.tmon
2.max_state is 0
3. press tab to set max_state
no work
[HW/SW Information]
Target Kernel: 6.3
Target Release: 23.10
Commit ids: 22c52fa5155a2f4
Platform Independent
[Business Justification]
Bug Fix
Changed in intel: | |
status: | New → Fix Committed |