Navigation

    Netgate Discussion Forum
    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search

    Pfsense 2.4 stopped at vga_bitblt_text*0x14a: movi (%rax, %rcx,4), %r15d

    Installation and Upgrades
    6
    7
    933
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • T
      Timmeke last edited by

      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

      1 Reply Last reply Reply Quote 0
      • B
        balbert last edited by

        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

        1 Reply Last reply Reply Quote 0
        • Grimson
          Grimson Banned last edited by

          https://doc.pfsense.org/index.php/2.4_New_Features_and_Changes#Known_Issues reading helps.

          1 Reply Last reply Reply Quote 0
          • T
            Timmeke last edited by

            @Grimson:

            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

            1 Reply Last reply Reply Quote 0
            • Derelict
              Derelict LAYER 8 Netgate last edited by

              The fact that that is a Known Issue means it was tested, and discovered, and a work-around was offered.

              Chattanooga, Tennessee, USA
              The pfSense Book is free of charge!
              DO NOT set a source port in a port forward or firewall rule unless you KNOW you need it!
              Do Not Chat For Help! NO_WAN_EGRESS(TM)

              1 Reply Last reply Reply Quote 0
              • S
                smcclos last edited by

                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/

                1 Reply Last reply Reply Quote 0
                • P
                  pppfsense last edited by

                  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".

                  @Grimson:

                  https://doc.pfsense.org/index.php/2.4_New_Features_and_Changes#Known_Issues reading helps.

                  1 Reply Last reply Reply Quote 0
                  • First post
                    Last post