Comment 11 for bug 1873083

On Thu, 2020-04-16 at 20:18 +0000, Anton Keks wrote:
> I have traced it to int3403_thermal module.
> If I do rmmod int3403_thermal - the thermal_zone3 goes away an no
> thermal shutdown is happening.
> I can use it as a workaround - but is it dangerous for the HW?
>
> https://github.com/torvalds/linux/blob/master/drivers/thermal/intel/int340x_thermal/int3403_thermal.c
>
> > From what I see in the source, it is probably related to battery or
> charger or both.
>
> So I guess thermald should take this sensor into acccount when
> throttling?
>
> When I quickly modprobe int3403_thermal back, the full output is here
> (it is seen that temp is 79C, which is really close to the critical
> 80C):

Correct. So this will shutdown the system. Is that sensor temperature
always in that range? If it is then sensor may be faulty.

Thanks,
Srinivas

>
> thermal_zone3$ grep . *
> available_policies:power_allocator user_space step_wise bang_bang
> fair_share
> grep: emul_temp: Permission denied
> integral_cutoff:0
> k_d:0
> k_i:0
> k_po:0
> k_pu:0
> offset:0
> policy:user_space
> grep: power: Is a directory
> slope:0
> grep: subsystem: Is a directory
> sustainable_power:0
> temp:79000
> trip_point_0_hyst:2000
> trip_point_0_temp:0
> trip_point_0_type:passive
> trip_point_1_hyst:2000
> trip_point_1_temp:0
> trip_point_1_type:passive
> trip_point_2_hyst:2000
> trip_point_2_temp:80000
> trip_point_2_type:critical
> trip_point_3_hyst:2000
> trip_point_3_temp:75000
> trip_point_3_type:hot
> trip_point_4_hyst:2000
> trip_point_4_temp:65000
> trip_point_4_type:passive
> trip_point_5_hyst:2000
> trip_point_5_temp:60000
> trip_point_5_type:active
> trip_point_6_hyst:2000
> trip_point_6_temp:50000
> trip_point_6_type:active
> trip_point_7_hyst:2000
> trip_point_7_temp:40000
> trip_point_7_type:active
> type:SEN4
>