Bug #4617


boot_serial="YES" in loader.conf causes very slow boot on some hardware where serial console not enabled

Added by Testerrr Testerrr over 6 years ago. Updated over 6 years ago.

Very High
Target version:
Start date:
Due date:
% Done:


Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
Affected Architecture:


Manual update of working configuration (in GUI-menu System:Firmware, Invoke pfSense Manual Upgrade) from version 2.2.1-final to
freezes booting of this pfSense-Full-Update-2.2.2-DEVELOPMENT-amd64-20150412-0813-build.
On screen of pfsense-host in initial strings of booting system characters writes one by one in seconds!
Therefore booting practically freezes completely. Booting can't be done in 10 minutes on powerfull workstation (intel i3 - CPU unit) with SSD-hard drive!

Actions #1

Updated by Kill Bill over 6 years ago

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

Actions #2

Updated by Chris Buechler over 6 years ago

  • Status changed from New to Feedback

having just gone through all the testing for 2.2.2-RELEASE, this most definitely is not a general problem.

need more details on exactly what is happening, the description doesn't tell anything specific enough to even guess at what's happening.

Actions #3

Updated by Testerrr Testerrr over 6 years ago

I have made additional tests for explanation.

It's mine phone video of this incident.
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 - - displays that 2.2.2 LiveCD booting perfectly.

Next video - - installation 2.2.2 to internal SSD.

Video displays that 2.2.2 Perfectly Booting Default Empty Config

Video - 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 -

Actions #4

Updated by Bartłomiej Bujak over 6 years ago

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

Actions #5

Updated by Chris Buechler over 6 years ago

not sure the cause of this, trying to track down more info.

Actions #6

Updated by Chris Buechler over 6 years ago

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

Actions #7

Updated by Chris Buechler over 6 years ago

  • Priority changed from Normal to High
  • Target version set to 2.2.3
  • Affected Version changed from 2.2.1 to 2.2.2

Thanks Testerr for the config. Pretty sure we know the cause of this, awaiting feedback on the forum thread.

Actions #8

Updated by Chris Buechler over 6 years ago

  • Subject changed from Manual update to 2.2.2 (amd64 build 12-Apr-2015 13:46 size 86321898) freezes booting to boot_serial="YES" in loader.conf causes very slow boot on some hardware where serial console not enabled
  • Status changed from Feedback to Resolved
  • Priority changed from High to Very High

this is fixed completely for 2.2.3, and fixed in the full update files for 2.2.2.

Actions #9

Updated by Andreas Bochem over 6 years ago

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


Also available in: Atom PDF