AES-NI CPU Crypto: No
-
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. -
@stephenw10 No, just me posting it here. And there is one.
-
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
-
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 FutureVery low and future really got my hopes up.
-
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 Bootif 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? -
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
-
@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.
-
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> -
Hmm, not sure why you ended up with no logs then. That is the reason for the missing CPU data though.
Steve
-
It's probably this bug: https://redmine.pfsense.org/issues/11428
-
Yes, it's that. As I linked above.
