[SOLVED] pfSense 2.4.3 halts with calcru messages in console
I'm running pfsense 2.4.3 in a VM on Proxmox VE 5.1.
After a variable amount of time and traffic pfsense stops passing traffic.
I can't get to the gui.
The console from VM shows multiple lines like:
calcru: runtime went backwards from 932 usec to 743 usec for pid 12 (intr)
calcru: runtime went backwards from 966291697 usec to 869561348 usec for pid 11 (idle)
calcru: runtime went backwards from 50754758 usec to 452405913 usec for pid 11 (idle)
calcru: runtime went backwards from 6980 usec to 5566 usec for pid 1 (init)
calcru: runtime went backwards from 123795810 usec to 99437608 usec for pid 0 (kernel)
Can anyone point me in the right direction to solve this?
Is this an error in pfsense 2.4.3 (in combination with proxmox?)
Is this a hardware fault?
Re-installing pfsense in a new vm doesnt solve the problem.
25 years in the IT business and never seen such errors, something new everyday :)
KOM last edited by
Google found these:
Looks like it's a combination of things. Try the suggestions above.
Excellent, i will try those possible solutions. I guess my Google-skills missed those, its all about the search parameters.
Changed the NTP server to a local one and problem seems solved. No crashes in 48 hours. It was on the default pfsense ntp.
john_wick last edited by john_wick
Have the same problem with new 2.4.3 versinon its hangs cli with web UI interface after 30 minutes of work in KVM. When suspend and reply Pfsense VM cli with UI go to unfrozen :(
When cli ang UI hangs a cant uptdate my linux machines under the NAT in local network
EIST or Speedstep disabled
cpu 2cores of xeon x5675 up to 1.6 ghz
Proliant G7 series
hypervisor Proxmox 5.3 or Qemu KVM
How to slowe this problem? IPfire?
Why are you running 2.4.3? Have you tested 2.4.4p1/2?
Locking this. You have you own thread open for it: