7682 2015-04-30 15:16:39 +0000 acpitz-virtual-0 thermal device always returns 26.8 deg C 2017-06-13 18:08:08 +0000 1 1 12 Hardware Platforms MinnowBoard MAX Firmware minnowmax-edk2 unspecified MinnowBoard Max x86_64 RESOLVED MOVED Medium normal Production Release 1 dvhart unassigned david.wei dvhart gerard.b shifeix.a.lu sjolley.yp.pm --- --- Don't know oldest_to_newest 50664 0 dvhart 2015-04-30 15:16:39 +0000 On Linux 3.19.2 (yocto), a user on MinnowBoard is reporting the acpitz-virtual-0 device, accessed via /sys/class/thermal/thermal_zone0/temp, is always returning 26800 (26.8 deg C), regardless of core temp. Another Debian user reported the following using the lm-sensors package: sensors acpitz-virtual-0 Adapter: Virtual device temp1: +26.8°C (crit = +90.0°C) coretemp-isa-0000 Adapter: ISA adapter Core 0: +50.0°C (high = +110.0°C, crit = +110.0°C) Core 2: +51.0°C (high = +110.0°C, crit = +110.0°C) The core* temps using the coretemp driver are what I use, I'm not sure what the acpitz-virtual-0 device is or what it reports. Since it's an ACPI device, I'm filing under firmware for an initial review of this device and it's ACPI implementation. Should this device be reported? I have asked on list for the firmware version. The original reported is Cc'd here. Gerard, if you can report your firmware version, that would be helpful. 50668 1 dvhart 2015-04-30 15:38:13 +0000 Scanning through the edk2 sources, I see the following defaults for VLV2 devices, which explicitly returns this value (26.8 deg C) if "both EC and DTS are unavailable". If this always returns the same value, should we be removing this from the table? Or at least disabling it via _STA? // _TMP (Temperature) // // Return the highest of the CPU temperatures to the OS. // // Arguments: (0) // None // Return Value: // An Integer containing the current temperature of the thermal zone (in tenths of degrees Kelvin) // Method(_TMP,0,Serialized) { If(DTSE) { If(LGreater(DTS2, DTS1)) { Store(DTS2,Local0) } else { Store(DTS1,Local0) } Return(Add(2732,Multiply(Local0,10))) // // Else return a static value if both EC and DTS are unavailable. // } Else { Return(3000) // (3000-2732)/10 = 26.8 degree C } } 50674 2 gerard.b 2015-04-30 16:58:24 +0000 Problem reported when using firmware: MNW2MAX1.X64.0079.R01.1504081555 - Gerard Bucas (gerard.b@tekmagic.net) 50950 3 david.wei 2015-05-13 06:18:05 +0000 We are trying to enable Digital Thermal Sensor to detect the temperature. 51217 4 david.wei 2015-05-22 06:08:44 +0000 Firware team is optimizing Digital Thermal Sensor driver to make it able to detect smaller changes of processor temperature. 51277 5 david.wei 2015-05-26 23:23:38 +0000 Shifei has finished adding back Digital Thermal Sensor and tested its function. V0.81 release will include this feature. 52062 6 david.wei 2015-06-30 23:34:50 +0000 This issue has been fixed by V0.81 release. Please review it. 52088 7 gerard.b 2015-07-02 05:47:09 +0000 Ok - tested it on a minnowboard MAX with latest 0.81 firmware. It now behaves differently and after Linux starts in root shell it returns 60000 (= 60.0C). At that point the sensors command returns around 65C However, then I run some heavy CPU/GPU content and the value returned by temp only rises to 70000 (70.0C) and then stats there, even though 'sensors' now reports 92C. So the 'virtual device' seems to get stuck at a max of 70000, even though CPU (die) temp has gone up to 92C (stabilises around 92C with the content I am running). So my conclusion is that the behavior has changed (no longer returns a fixed/constant value like before) but it still does not report correct temp and always returns a value between 60000 and 70000. A good 'check' is to compare the results of the Linux 'sensors' command - which I did. Hope this helps. Regards Gerard Bucas Gerard.b@tekmagic.net 52328 8 david.wei 2015-07-14 06:14:29 +0000 Assign to Shifei to check the ACPI thermal zone. 52822 9 shifeix.a.lu 2015-08-05 07:13:10 +0000 Please double check with V0.82 Firmware Binary.Thanks a lot! 52957 10 gerard.b 2015-08-10 16:50:29 +0000 OK - I checked it out with 0.82 firmware and linux 3.19 kernel (ubuntu & yocto) running on a minnowboard MAX. Seems to work and reports similar results now to "sensors" command. Thanks for fixing this - much appreciated. - Gerard 53006 11 david.wei 2015-08-11 23:25:48 +0000 Hi Dareen, Gerard has confirmed this fix. Could you help change this bug status to "resolved"? 74107 12 sjolley.yp.pm 2017-06-13 18:08:08 +0000 We are no longer tracking in Yocto Project Bugzilla MinnowBoard and MinnowBoard-MAX HW and firmware bugs.