Pfsense 2.4 stopped at vga_bitblt_text*0x14a: movi (%rax, %rcx,4), %r15d
-
Hi,
I am running pfsense 2.3 as a gateway on a vmware 6.5 ESXi server.
i give the vm 4 cores and 4gb ram.After update to 2.4 its random crashed with vga_bitblt_text*0x14a: movi (%rax, %rcx,4), %r15d
Right now i revert to the snapshot so no wurrys but is it a coming issue or should i debug?
Regards,
Tim
-
I have the same issue running pfsense on ESXi 6.5. Same stop error/code/instruction.
upgraded from 2.3 to 2.4. Initially, the upgrade was successful.
On reboot a few days after the upgrade, the Stop error occurred.
reverted back to 2.3
-
-
https://doc.pfsense.org/index.php/2.4_New_Features_and_Changes#Known_Issues reading helps.
jep thats true. But i thought pfsense was a bit more professional and test there products before making a STABLE 2.4. But as i can read on the internet 2.4 is like a alpha release (thats what i read).
I'm glad with snapshots with this sort of releases.
I wait for a stable release ;).
Tim
-
The fact that that is a Known Issue means it was tested, and discovered, and a work-around was offered.
-
Have you tried 2.4.1, it specifically addresses an issue with vSphere 6.5.0
https://www.reddit.com/r/PFSENSE/comments/78hms8/pfsense_241release_now_available/
-
It always helps to read the release notes.
But, release notes are for things that the software cannot handle or very specific unavoidable situations.
In this case, running under VMWARE is extremely common and instead of assuming the user will catch the issue,
why not simply make the installer add the needed change to the boot loader??The fact that a patch to correct this, was made, says that it should have been caught in the previous release…
It is still great work and it is appreciated, but like I said before, if it is meant to be Enterprise, Production ready, these 'silly' things will drive customers away as well as: "I have never, ever had any upgrade issues with Untangle".
https://doc.pfsense.org/index.php/2.4_New_Features_and_Changes#Known_Issues reading helps.
