pfSense

Works just fine here. Please, use the forums before you have some specific confirmed issue. Total lack of information here.

I have made additional tests for explanation.

It's mine phone video of this incident.
http://dfiles.ru/files/pxrfq8ffq
Boot freezes in pfSense 2.2.2, after upgrading from working 2.2.1 to pfSense-Full-Update-2.2.2-DEVELOPMENT-amd64-20150412-0813.tgz

Another video - http://dfiles.ru/files/34qutxu39 - displays that 2.2.2 LiveCD booting perfectly.

Next video - http://dfiles.ru/files/7i4pwy5ya - installation 2.2.2 to internal SSD.

Video http://dfiles.ru/files/8688knvtz displays that 2.2.2 Perfectly Booting Default Empty Config

Video http://dfiles.ru/files/23ztopm5d - how freezes booting 2.2.2 after restoring working 2.2.1-config (backup-ed before upgrading to 2.2.2)

As you can see - config conversion from 2.2.1 to 2.2.2 can't be done successfully while upgrading version!
And previuosly 2.2.1-config can't be successfully uploaded to a clean 2.2.2-installation while last 2.2.2 freezes booting after that.

My hardware config placed here - http://dfiles.ru/files/yn77a6666

After automatic upgrade from 2.2.1 to 2.2.2 I have the same problem.

not sure the cause of this, trying to track down more info.
https://forum.pfsense.org/index.php?topic=92415.0

anyone who's seeing this, could you get me a config backup? Copy/paste via status.php is fine, which trims out certs, passwords, etc. Email to cmb at pfsense dot org. At least OP's situation seems to be something in the config triggering the issue

Still an issue with recent pfSense-2.2.2-RELEASE-4g-amd64-nanobsd-vga.img.gz, just downloaded and installed a few hours ago.

System boots fine at first, but after uploading an (encrypted) config file in Diagnostics -> Backup/Restore, boot is slowed down as described
here. Only the slice that was active while I uploaded the config is affected. Booting from the other slice worked fine and duplicating the
known good slice fixed the issue.

I also repeated the process to confirm the issue, but this time exported the config file from the previous 2.2.2 installation. So no version mismatch, no config update in the process. Just uploading a 2.2.2 config to a fresh 2.2.2 installation. Still triggered the issue.

The config file was always encrypted.

Unfortunately, I did not (yet) figure out how to access the inactive slice to check its loader.conf. On the "good" slice it was empty.
However, the fact that disabling the serial ports in BIOS setup also fixed booting made me chose this ticket. (I just prefer keeping them enabled and copying over the slice instead.)