[Solved] reboot in 25.1 halts at check admtemp0.

[dirkp]

Hi All

I did an upgrade op Opnsense to versio 25.1. This is on a DECISO DEC610 piece of hardware. Before that previous versions worked like a charm.

Now the booting procedure hangs at the following statement in the terminal:
amdtemp0: <AMD CPU On-Die Thermal Sensors> on hostb5

This is a fan-less piece of hw.

Anyone any idea ?

rgds
dirkp

[dirkp]

In the meantime I tried:
- getting to the bootprompt and set amdtemp_load="NO"
no avail
- trying to boot in single user mode
no avail
- trying to boot previous kernel
no avail
- getting to the boot prompt and boot -v
this gave this extra line:
amdtemp0: <AMD CPU On-Die Thermal Sensors> on hostb5
amdtemp0: Found 2 cores and 1 sensors.
further: it hangs...

I am pretty sure I must find a way to prevent to "autostart" or autoload the amdtemp. But I cannot seem to get find out how.

Maybe it gets loaded from the rc.conf or so but I have no proof of that...
tbc

[patient0]

I could find almost no information about a DEC610, is it an AMD GX-210UA SOC based device?

I am pretty sure I must find a way to prevent to "autostart" or autoload the amdtemp

Single user mode should already disable all modules, could it be an console issue?
And did you try setting `set amdtemp_load="NO"`?

Since the system is not working, can you try a) boot of an OPNsense USB stick (lastest and an earlier version) and if that is no success then b) boot from a vanilla FreeBSD 14.2?

[dirkp]

The device is indeed An AMD G series SOC GX-210UA 1.0Ghz dual core.

I contacted Deciso (supplier/manufacturer) and they confirmed it is still supported (the router is about 6y old).

I confirm indeed that I tried amdtemp_load="NO", I corrected my original mail.

I do not think it is a console issue, at least I get no indication otherwise and console is working fine. The trouble starts when /sbin/init is launched so it seems... Maybe try the single user again ? Update/edit: I found this https://forum.opnsense.org/index.php?topic=28602.0 - lucky my German is not that bad :-) I'll check this first, you will never know.

Booting via USB as suggested is going to be a weekend job I am afraid.. but we will continue.



Any other suggestions always welcome.
Dirkp

[patient0]

Update/edit: I found this https://forum.opnsense.org/index.php?topic=28602.0 - lucky my German is not that bad :-) I'll check this first, you will never know.

(I do speak German) It's about setting the disabling legacy UART. Does the device even have a normal BIOS? If yes, of course try it (but it would hint towards an issue with the console).

[dirkp]

Helas, no way to access the bios. Unfortunate!

I have limited time this weekend, testing with booting via USB will be for another time... really disappointed...

Code Select Expand

pci0: driver added
found-> vendor=0x1022, dev=0x780b, revid=0x3a
        domain=0, bus=0, slot=20, func=0
        class=0c-05-00, hdrtype=0x00, mfdev=1
        cmdreg=0x0403, statreg=0x0220, cachelnsz=0 (dwords)
        lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
pci0:0:20:0: reprobing on driver added
ahcich0: AHCI reset...
ahcich0: SATA connect time=100us status=00000133
ahcich0: AHCI reset: device found
ahcich0: AHCI reset: device ready after 1ms
ahcich1: AHCI reset...
ahcich1: SATA connect timeout time=10000us status=00000000
ahcich1: AHCI reset: device not found
pci1: driver added
pci2: driver added
pci3: driver added
Trying to mount root from ufs:/dev/ufs/OPNsense [rw,noatime]...
ada0 at ahcich0 bus 0 scbus0 target 0 lun 0
ada0: <TS128GMSA370 P1225CH1> ACS-2 ATA SATA 3.x device
ada0: Serial Number E901030025
ada0: 600.000MB/s transfers (SATA 3.x, PIO4, PIO 1024bytes)
ada0: Command Queueing enabled
ada0: 122104MB (250069680 512 byte sectors)
GEOM: new disk ada0
pass0 at ahcich0 bus 0 scbus0 target 0 lun 0
pass0: <TS128GMSA370 P1225CH1> ACS-2 ATA SATA 3.x device
pass0: Serial Number E901030025
pass0: 600.000MB/s transfers (SATA 3.x, PIO4, PIO 1024bytes)
pass0: Command Queueing enabled
uhub0: 4 ports with 4 removable, self powered
uhub2: 4 ports with 4 removable, self powered
uhub3: 4 ports with 4 removable, self powered
Root mount waiting for: usbus2 usbus4
uhub1: 4 ports with 4 removable, self powered
uhub4: 4 ports with 4 removable, self powered
WARNING: / was not properly dismounted
WARNING: /: TRIM flag on fs but disk does not support TRIM
atrtc0: providing initial system time
start_init: trying /sbin/init
pci0: driver added
found-> vendor=0x1022, dev=0x780b, revid=0x3a
        domain=0, bus=0, slot=20, func=0
        class=0c-05-00, hdrtype=0x00, mfdev=1
        cmdreg=0x0403, statreg=0x0220, cachelnsz=0 (dwords)
        lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
pci0:0:20:0: reprobing on driver added
intsmb0: <AMD FCH SMBus Controller> at device 20.0 on pci0
pcib0: allocated type 4 (0xcd6-0xcd7) for rid 0 of intsmb0
pcib0: allocated type 4 (0xb00-0xb0f) for rid 0 of intsmb0
smbus0: <System Management Bus> on intsmb0
pci1: driver added
pci2: driver added
pci3: driver added
lo0: link state changed to UP
amdtemp0: <AMD CPU On-Die Thermal Sensors> on hostb5
amdtemp0: Found 2 cores and 1 sensors.


[dirkp]

Oh my god, I have found the bugger.

Your suggestion on the issues with the terminal (and old hw) got me looking further down the road in the opnsense forums. I have found this thread: https://forum.opnsense.org/index.php?topic=47494.15

Not sure what this all means but clearly: there is a "bug" in 25.1 (funny enough it also refers to that uart thing where there is an advice to disable something in the bios) with old hardware and looking at the setting it is clearly uart related. Anyway: long story short

boot
at the boot press esc to get into the boot prompt:

Code Select Expand

set hint.uart.0.at="isa"
boot

and it worked (again) like a charm. Unfortunately I do not know what to do next :-(

[patient0]

hint.uart.0.at="isa"

You add that line to the file /boot/loader.conf.local (without 'set') and it will be applied during boot.

To add it you execute:

Code Select Expand

echo 'hint.uart.0.at="isa"' >> /boot/loader.conf.local

[dirkp]

tx. I the meantime I also upgraded to 25.1.8 and the issue is gone. No need to update loader.conf.local, luckily.

anyway problem solved !
tx

[patient0]

I the meantime I also upgraded to 25.1.8 and the issue is gone.

That's even better, they found the issue too and fixed it.

[dirkp]

Different style of problem, same solution... https://forum.opnsense.org/index.php?topic=47494.15
adding for the cross reference.