The coolest PC in the entire universe!

fmc000 said:
Code: 
[19:21][fmc000@tu45b-freebsd][~]
 ╰─$ sysctl -a hw.acpi.thermal.tz0.temperature
hw.acpi.thermal.tz0.temperature: -273.1C
[19:21][fmc000@tu45b-freebsd][~]
 ╰─$

How cool is that?
Click to expand...
Bro, nice quantum computer. One question tho, how did you got absolute 0 temperature in your rig? Water cooling?
 
On a more serious tone, any idea on how to debug the issue? Coretemp values are definitely OK but there are apps that report the CPU temp using this value (sysutils/btop is one example but there are others).
 
Hmm, it is either a faulty temperature sensor, or the FreeBSD driver is getting confused (I understand that many of these things are very ad-hoc and each vendor does them slightly differently).

Some random questions that might help with diagnosis:
  • What is the machine? Googling around do others run into the issue?
  • Does the temperature still change? Possibly just non-calibrated?
  • Does it come up with the same range using i.e a Linux LiveCD or even on Windows. Is it FreeBSD specific?
In some ways you are lucky that it is cold. I had one (faulty) on an old HP Z420 that would read hotter than my soldering iron. Unfortunately that meant the fans were on full blast and most operating systems would just immediately shut down.
 
First of all, thank you for your answer. I'll try to do my best to anwser:
  • my laptop is this one: HandyStation PRO;
  • the temperature never changes, it's always fixed to -273.1 (I suppose that it would read -273.16 if the driver would print 2 digits after the decimal point);
  • I will try an Archlinux image and report back (I never booted Windows on this machine even if it came with it preinstalled).
For your last sentence, actually I thought about that and I came to the conclusion that the firmware can read values correctly as the (very loud) fan spins like crazy when I compile things but it's usually off during normal activities. There are no fan drivers / sensors available in both Archlinux and FreeBSD.

BTW, apart from this nitpick and from the fingerprint reader not detected (not even in Linux: FTE3600) this notebook is very well supported by 14.1, everything works (OK, to be picky USB3 is still unfortunately very slow when compared to Archlinux).
 
My old home server with Intel Atom D525 show that temperature in htop. Now is summer and show a more higher temperature but I also installed cpu microcode, so I do not know if it is changed for the season or the microcode.

forum.jpg
 
It looks like it's showing coretemp values, which are OK also in my notebook. It's the ACPI temp which is wrong.
 
Too cold for liquid nitrogene.
You need liquid helium cooling to get into this range.
While superconducting did you considered overclocking > 7GHz?
Tell us your build world time on that! ?

Seriously:
Temperatures are commonly measured with a Negative Temperature Coefficient Thermistor.
That's a resistor which resistance becomes lower the hotter it gets.
Showing ~ absolute zero in this case could mean unfinite resistance, no-load, an interrupted conduction,
or in short clear english:
a broken wire.

As I said, it could.
I hope for you it's a software problem, or just a lose connector/jumper somewhere on the board.
 
It's definitely a software problem because in Linux it works. Please see the picture I just took while booting a (not really recent) Archiso.

IMG_4334.jpg


As you can see it shows four thermal zones, INT3400 (I suppose it's the chipset; 20°C) - CPU (34°C) - Wi-Fi chip (34°C) and x86_pkg_temp (???; 32°C). Allo look pretty reasonable to me for a freshly booted system.

FreeBSD sees only one thermal zone and the coretemp driver:

Code: 
 ╰─$ sysctl -a|grep temperature
hw.acpi.thermal.tz0.temperature: -273.1C
dev.cpu.7.temperature: 35.0C
dev.cpu.5.temperature: 40.0C
dev.cpu.3.temperature: 37.0C
dev.cpu.1.temperature: 41.0C
dev.cpu.6.temperature: 36.0C
dev.cpu.4.temperature: 38.0C
dev.cpu.2.temperature: 36.0C
dev.cpu.0.temperature: 40.0C
[17:58][fmc000@tu45b-freebsd][~]
 ╰─$ sysctl -a|grep thermal
hw.acpi.thermal.tz0._TSP: -1
hw.acpi.thermal.tz0._TC2: -1
hw.acpi.thermal.tz0._TC1: -1
hw.acpi.thermal.tz0._ACx: 71.1C 55.1C 50.1C 45.1C 40.1C -1 -1 -1 -1 -1
hw.acpi.thermal.tz0._CRT: 119.1C
hw.acpi.thermal.tz0._HOT: -1
hw.acpi.thermal.tz0._CR3: -1
hw.acpi.thermal.tz0._PSV: -1
hw.acpi.thermal.tz0.thermal_flags: 0
hw.acpi.thermal.tz0.passive_cooling: 0
hw.acpi.thermal.tz0.active: -2
hw.acpi.thermal.tz0.temperature: -273.1C
hw.acpi.thermal.user_override: 0
hw.acpi.thermal.polling_rate: 10
hw.acpi.thermal.min_runtime: 0
sys.class.drm.card0.gt.gt0.throttle_reason_vr_thermalert: 0
sys.class.drm.card0.gt.gt0.throttle_reason_thermal: 0
[17:58][fmc000@tu45b-freebsd][~]
 ╰─$

Values in the ACx field look reasonable, I wish I knew what they do refer to.

EDIT: these values are fixed, they haven't changed since I booted the laptop.
 
Does your FreeBSD dmesg mention anything about invalid ACPI entries?
My X1 Carbon (on OpenBSD) complains about out of range temperature sensors (and subsequently ignores them).

Perhaps Linux has some quirk applied to correct a slightly buggy ACPI entry, I don't suppose there are any BIOS updates for your machine? It sounds like a cop-out, but sometimes (rarely) these things do actually help.
 
Yes, the BIOS in this machine is basically garbage and I actually filter out this error lines to have readable and meaningful logs. However, I believe you're right as I checked those lines and they are definitely different from what I got in Linux:

Code: 
[20:37][fmc000@tu45b-freebsd][~]
 ╰─$ grep '20221020.ps' /var/run/dmesg.boot |wc -l
     372
[20:42][fmc000@tu45b-freebsd][~]
 ╰─$ grep '20221020.ps' /var/run/dmesg.boot |sort |uniq
ACPI Error: Aborting method \134_SB.PC00.LPCB.H_EC.BAT0._STA due to previous error (AE_NOT_EXIST) (20221020/psparse-689)
ACPI Error: Aborting method \134_TZ.TZ00._TMP due to previous error (AE_NOT_FOUND) (20221020/psparse-689)
Firmware Error (ACPI): Could not resolve symbol [\134_SB.PC00.LPCB.HEC.PLMX], AE_NOT_FOUND (20221020/psargs-503)
[20:42][fmc000@tu45b-freebsd][~]
 ╰─$

I'll try booting again on archiso and report back but I believe that the ACPI-20221020 shipped in 14.1 is pretty old.
 
fmc000 said:
ACPI Error: Aborting method \134_TZ.TZ00._TMP due to previous error (AE_NOT_FOUND) (20221020/psparse-689)
Click to expand...
Right, this is the likely culprit.

Have a check in here for disabling quirks (just in case something weird is applied).

But then you are possibly into the realms of dumping and patching the ACPI tables which is beyond my knowledge. Perhaps someone else here has done this before?

Perhaps it is a known flaw with some BIOSes if Linux does indeed have a quirk that handles it?
 
Archiso:

IMG_4347.JPG


Different messages but TZ.TZ00._TMP definitely present in Linux also. As i said before, the ACPI package in FreeBSD is pretty old.

I'm not confident in playing with ACPI parameters, I don't want to risk to damage anything or having an unbootable laptop. Unless someone has a real idea of what's going on I think I'm done with this problem, it was more a curiosity than anything else.
 
It's seems to do absolute measuring in Kelvin. Can you get it any hotter or is the temperature polling line dead?
 
fmc000 said:
I don't want to risk to damage anything or having an unbootable laptop. Unless someone has a real idea of what's going on I think I'm done with this problem, it was more a curiosity than anything else.
Click to expand...
Thats fair. One last ditch effort is to alternate between UEFI <-> BIOS mode and see if perhaps some of the emulation is dodgy. But other than that I have no real suggestions.
 
My new server instead, seams to show a correct temperatrure (more or less).

forum.jpg


It's an Intel N100. I have the same ACPI messages as fmc000. I muted the messages on console they come out continuously. From /var/log/messages

Code: 
ug 17 09:22:54 ambaxtos kernel: ACPI Error: Aborting method \_TZ.TZ00._TMP due to previous error (AE_NOT_FOUND) (20221020/psparse-689)
Aug 17 09:23:04 ambaxtos kernel: Firmware Error (ACPI): Could not resolve symbol [\_SB.PC00.LPCB.ITE8.GETT], AE_NOT_FOUND (20221020/psargs-503)
Aug 17 09:23:04 ambaxtos kernel: ACPI Error: Aborting method \_TZ.TZ00._TMP due to previous error (AE_NOT_FOUND) (20221020/psparse-689)
Aug 17 09:23:14 ambaxtos kernel: Firmware Error (ACPI): Could not resolve symbol [\_SB.PC00.LPCB.ITE8.GETT], AE_NOT_FOUND (20221020/psargs-503)
Aug 17 09:23:14 ambaxtos kernel: ACPI Error: Aborting method \_TZ.TZ00._TMP due to previous error (AE_NOT_FOUND) (20221020/psparse-689)
Aug 17 09:23:24 ambaxtos kernel: Firmware Error (ACPI): Could not resolve symbol [\_SB.PC00.LPCB.ITE8.GETT], AE_NOT_FOUND (20221020/psargs-503)
Aug 17 09:23:24 ambaxtos kernel: ACPI Error: Aborting method \_TZ.TZ00._TMP due to previous error (AE_NOT_FOUND) (20221020/psparse-689)
Aug 17 09:23:34 ambaxtos kernel: Firmware Error (ACPI): Could not resolve symbol [\_SB.PC00.LPCB.ITE8.GETT], AE_NOT_FOUND (20221020/psargs-503)
Aug 17 09:23:34 ambaxtos kernel: ACPI Error: Aborting method \_TZ.TZ00._TMP due to previous error (AE_NOT_FOUND) (20221020/psparse-689)
Aug 17 09:23:44 ambaxtos kernel: Firmware Error (ACPI): Could not resolve symbol [\_SB.PC00.LPCB.ITE8.GETT], AE_NOT_FOUND (20221020/psargs-503)
Aug 17 09:23:44 ambaxtos kernel: ACPI Error: Aborting method \_TZ.TZ00._TMP due to previous error (AE_NOT_FOUND) (20221020/psparse-689)
Aug 17 09:23:54 ambaxtos kernel: Firmware Error (ACPI): Could not resolve symbol [\_SB.PC00.LPCB.ITE8.GETT], AE_NOT_FOUND (20221020/psargs-503)
Aug 17 09:23:54 ambaxtos kernel: ACPI Error: Aborting method \_TZ.TZ00._TMP due to previous error (AE_NOT_FOUND) (20221020/psparse-689)
Aug 17 09:24:04 ambaxtos kernel: Firmware Error (ACPI): Could not resolve symbol [\_SB.PC00.LPCB.ITE8.GETT], AE_NOT_FOUND (20221020/psargs-503)
Aug 17 09:24:04 ambaxtos kernel: ACPI Error: Aborting method \_TZ.TZ00._TMP due to previous error (AE_NOT_FOUND) (20221020/psparse-689)

I don't changed anything in BIOS, I no more understand most of the options, that is: I don't know what I do.
 
freethread said:
My new server instead, seams to show a correct temperatrure (more or less).

View attachment 20059

It's an Intel N100. I have the same ACPI messages as fmc000. I muted the messages on console they come out continuously. From /var/log/messages

Code: 
ug 17 09:22:54 ambaxtos kernel: ACPI Error: Aborting method \_TZ.TZ00._TMP due to previous error (AE_NOT_FOUND) (20221020/psparse-689)
Aug 17 09:23:04 ambaxtos kernel: Firmware Error (ACPI): Could not resolve symbol [\_SB.PC00.LPCB.ITE8.GETT], AE_NOT_FOUND (20221020/psargs-503)
Aug 17 09:23:04 ambaxtos kernel: ACPI Error: Aborting method \_TZ.TZ00._TMP due to previous error (AE_NOT_FOUND) (20221020/psparse-689)
Aug 17 09:23:14 ambaxtos kernel: Firmware Error (ACPI): Could not resolve symbol [\_SB.PC00.LPCB.ITE8.GETT], AE_NOT_FOUND (20221020/psargs-503)
Aug 17 09:23:14 ambaxtos kernel: ACPI Error: Aborting method \_TZ.TZ00._TMP due to previous error (AE_NOT_FOUND) (20221020/psparse-689)
Aug 17 09:23:24 ambaxtos kernel: Firmware Error (ACPI): Could not resolve symbol [\_SB.PC00.LPCB.ITE8.GETT], AE_NOT_FOUND (20221020/psargs-503)
Aug 17 09:23:24 ambaxtos kernel: ACPI Error: Aborting method \_TZ.TZ00._TMP due to previous error (AE_NOT_FOUND) (20221020/psparse-689)
Aug 17 09:23:34 ambaxtos kernel: Firmware Error (ACPI): Could not resolve symbol [\_SB.PC00.LPCB.ITE8.GETT], AE_NOT_FOUND (20221020/psargs-503)
Aug 17 09:23:34 ambaxtos kernel: ACPI Error: Aborting method \_TZ.TZ00._TMP due to previous error (AE_NOT_FOUND) (20221020/psparse-689)
Aug 17 09:23:44 ambaxtos kernel: Firmware Error (ACPI): Could not resolve symbol [\_SB.PC00.LPCB.ITE8.GETT], AE_NOT_FOUND (20221020/psargs-503)
Aug 17 09:23:44 ambaxtos kernel: ACPI Error: Aborting method \_TZ.TZ00._TMP due to previous error (AE_NOT_FOUND) (20221020/psparse-689)
Aug 17 09:23:54 ambaxtos kernel: Firmware Error (ACPI): Could not resolve symbol [\_SB.PC00.LPCB.ITE8.GETT], AE_NOT_FOUND (20221020/psargs-503)
Aug 17 09:23:54 ambaxtos kernel: ACPI Error: Aborting method \_TZ.TZ00._TMP due to previous error (AE_NOT_FOUND) (20221020/psparse-689)
Aug 17 09:24:04 ambaxtos kernel: Firmware Error (ACPI): Could not resolve symbol [\_SB.PC00.LPCB.ITE8.GETT], AE_NOT_FOUND (20221020/psargs-503)
Aug 17 09:24:04 ambaxtos kernel: ACPI Error: Aborting method \_TZ.TZ00._TMP due to previous error (AE_NOT_FOUND) (20221020/psparse-689)

I don't changed anything in BIOS, I no more understand most of the options, that is: I don't know what I do.
Click to expand...
I already answered to you before:
It looks like it's showing coretemp values, which are OK also in my notebook. It's the ACPI temp which is wrong.
Click to expand...
Try this:
Code: 
sysctl hw.acpi.thermal.tz0.temperature
 
You must log in or register to reply here.
Back
Top