Quote from: NotFuzzyWarm on Today at 07:15:16 PM

If temp is really over 180C then char it - yes. Also a safe be that the chip would be dead by now from semiconductor failures in it.

Historically Canaan has always had temp sensors inside of each chip (hence the per-chip readout) so considering it is otherwise running normally I go with the idea that it is a false positive.

Agreed, my hypothesis is that if that temperature was correct it would have been fried already, or lead to some other failure.

So for posterity, is it possible it's a faulty temperature sensor inside of the chip? I'm not sure how Avalon's CGMiner implementation works against their hardware - I took a look at their github and nothing jumped out at me at first glance, as I thought maybe it was their software misreporting.

This was running for quite an extended period of time at that reported temp, and hashing on that chip is normal and working without issue. I can't say too much for the chip architecture, but the likelihood of one of the ASICs even reaching that high temperature while being in such close proximity to the heat sink (even if the thermal paste wasn't 100%) AND the fans cranking seems VERY unlikely. For example: The unit will be completely shut off, ambient room/device temperature is 55F. I turn the unit on and that ASIC reports 180C immediately.

Apologies for the hypothesizing, I'm just trying to pinpoint the false positive and if it's a hardware or software issue.