Issue with 25.1 upgrade - Lobby Temp Sensor panel temp issues.

Started by pasha-19, February 02, 2025, 08:42:22 PM

Previous topic - Next topic
February 02, 2025, 08:42:22 PM Last Edit: March 07, 2025, 05:35:23 PM by pasha-19 Reason: Added 3/7/2025 update
I cannot say I tested the 25.1 upgrade completely because the Lobby Temperature sensor pannel indicated some potentially significant problems.  I have a feeling the sensor display was in error and I had probably had no hot running components.  It took about 4 hours to re-establish the 24.7.12-4 router.  Attached are two images of the temperature sensors.  The better looking one was from the restored 24.7.12.4 version the one with 100C readings was from 25.1.  The base machine that generated this output is an Qotom Q838GE.  I hope this helps.    I would like to know how to setup a ZFS rollback before attempting the 25.1 upgrade again.  Is someone provides additional information I could extract log files or other information to assist in debugging the problem.

My processor is an I3-8130U.

Update 3/7/2025  using a ZFS snspshot I attempted this update again.  The results were the same as before.  I attempted to follow the advice below for the patch. 

The patch indicated below was attempted.  It reported as successful and the restart appeared to have worked.

# opnsense-patch https://github.com/opnsense/core/commit/695772d2017
# service configd restart

  The results were the same as before.  I successfully restored the 24.7.12.4 using my ZFS snapshots.  I can provide additional information from the 25.1 snapshot that still exists.

Any Ideas?


Same here on 3 different Systems with Intel CPU ( i5-8250U / i5-6200U / i7-7500U)
seems to be a Bug


Thanks for the attempt -- this patch did not seem to work in my case.   

All of this was fixed in 25.1.1 and made even better in 25.1.2. Do NOT patch historic patches.


Cheers,
Franco

Sorry I tried updating in the middle of the night so as not to affect others.  I failed to notice the first update only got me to 25.1 and NOT 25.1.2.  I just performed both updates and you are correct the problem was resolved.  The first time I tried to patch I only updated to 25.1 because I did not update a second time.  No patch was needed or attempted this time.

Thanks