AES-NI CPU Crypto: No

maverickws

Sorry guys but my dmesg.boot is empty.

[2.5.0-RELEASE][admin@pfSense.domain.io]/var/log: pwd
/var/log
[2.5.0-RELEASE][admin@pfSense.domain.io]/var/log: ls -la dmesg.boot
-rw-r--r--  1 root  wheel  0 Feb 19 16:54 dmesg.boot
[2.5.0-RELEASE][admin@pfSense.domain.io]/var/log: cat /var/log/dmesg.boot 
[2.5.0-RELEASE][admin@pfSense.domain.io]/var/log:

I'll have to take a look after next reboot. unless you can point some other way to get that info

stephenw10

Hmmm, weird.

It might still be in dmesg in the buffer if you rebooted recently.

Or in the system logs from the last boot.

Steve

Bob.Dig

If you delete logs it will clear that too and will report AES:No.
That behavior was "fixed" in 2.4.5p1, but came back with 2.5.

stephenw10

Ah. Hmm

Was there a bug for that? Not seeing one...

maverickws

The uptime is since the 2.5.0 update so 14 days uptime.

With grep looking for the CPU model (3865U) I don't get anything so I'd say its not on the system log.
I have to wait a few hours until I can reboot.

Bob.Dig

@stephenw10 No, just me posting it here. And there is one.

stephenw10

There is a current bug for it though: https://redmine.pfsense.org/issues/11428

Looks like that's what you're seeing. It's a gui bug, you would still be able to load the module and use the instructions.

Steve

maverickws

man looking at that bug and reading this:

Updated by Jim Pingle 15 days ago

Subject changed from CPU Type, some information disappear on 2.5.0 RC to CPU core details disappear after resetting log files
Priority changed from Normal to Very Low
Target version changed from 2.6.0 to Future

Very low and future really got my hopes up.

maverickws

By the way I'm sorry if this remark may seem stupid but,

what is the point of adding an OS Boot tab under
Status > System Logs > System > OS Boot

if the log is emptied??
I didn't manually reset any log files so I assume this is automatic. So its like a new tab to be empty?

stephenw10

It should not be emptied. That should only be manual.

This is the first report of this I've seen because most people never reset the logs.

Steve

maverickws

@stephenw10 I never reset the logs either.

Anyway this is my home office pfsense. I have a couple more virtualized on Xen, they have 3 days uptime. I'll keep an eye on them and let know if the same happens.

maverickws

Hello again,
As promised I rebooted our router late last night and now dmesg.boot is correctly populated, and the System Information correctly displays AES-NI CPU Crypto: Yes (Active):

Features2=0x4ffaebbf<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,RDRAND>

stephenw10

Hmm, not sure why you ended up with no logs then. That is the reason for the missing CPU data though.

Steve

MoonKnight

It's probably this bug: https://redmine.pfsense.org/issues/11428

stephenw10

Yes, it's that. As I linked above.