Really big problem to go to 2.2.2 from 2.2.1

mococanet

After upgrade the errors come up :

Kdb: debugger backend: ddb

Amd64

Restalling everything right now!!!

Supermule

No issues here.

ahking19

Upgraded from 2.2.1 –> 2.2.2. After 1 hour the server is still booting. The boot process is not hung, its still loading slowly. Outputting to screen character by character - 1 char every 2-3 seconds.

-Andrew

cmb

@ahking19:

Upgraded from 2.2.1 –> 2.2.2. After 1 hour the server is still booting. The boot process is not hung, its still loading slowly. Outputting to screen character by character - 1 char every 2-3 seconds.

Outputting what to the screen?

Trel

@cmb:

@ahking19:

Upgraded from 2.2.1 –> 2.2.2. After 1 hour the server is still booting. The boot process is not hung, its still loading slowly. Outputting to screen character by character - 1 char every 2-3 seconds.

Outputting what to the screen?

I'm having this exact same problem.
It looks like the normal boot messages, but as soon as the boot menu is done it's progressing at about one character every 5 second.

After 2 hours it got this far

http://i.imgur.com/FlqtWPp.jpg

Edit: and a video

https://docs.google.com/file/d/0B3EMGKybvzsJMjRtWnhIV0t5dHM/edit?usp=docslist_api

Michael Sh.

It appeared on the snapshots since April 11. It is treated by replacing the top-level of directory /boot on the content from 10 April.

cmb

@Michael:

It appeared on the snapshots since April 11. It is treated by replacing the top-level of directory /boot on the content from 10 April.

do you know which file specifically? That timeline seems to match some loader.conf changes for serial console, but I don't see how that would impact things in that way. That's been tested on numerous different hardware platforms and VMs, not sure how other situations can be different.

Those affected, are you running full installs or nano? What kind of hardware? Is the serial console enabled?

Trel

@cmb:

@Michael:

It appeared on the snapshots since April 11. It is treated by replacing the top-level of directory /boot on the content from 10 April.

do you know which file specifically? That timeline seems to match some loader.conf changes for serial console, but I don't see how that would impact things in that way. That's been tested on numerous different hardware platforms and VMs, not sure how other situations can be different.

Those affected, are you running full installs or nano? What kind of hardware? Is the serial console enabled?

Full install, physical hardware, I don't recall my settings for serial console.

dr.diesel

Here is a quick video of mine after just over an hour of booting. Make sure and notice how slow the text is appearing.

https://youtu.be/7JIgWEhBzPg

dr.diesel

@cmb:

Those affected, are you running full installs or nano? What kind of hardware? Is the serial console enabled?

Full install, intel hardware, default serial settings.

Michael Sh.

@cmb:

do you know which file specifically? That timeline seems to match some loader.conf changes for serial console, but I don't see how that would impact things in that way. That's been tested on numerous different hardware platforms and VMs, not sure how other situations can be different.

Those affected, are you running full installs or nano? What kind of hardware? Is the serial console enabled?

Zotac IONITX-P-E, 4GB RAM, 1TB HDD. Full install AMD64. Serial console disabled.
I don`t know which file specifically, but is top level of /boot - not a kernel. Can an experiment, but it will take some time.

jwhostet

Just took the upgrade and was sad to find out that I had the problem stated above. I am running the asrock q1900m system with 4gb of ram. I had serial console enabled. I went to the BIOS and disabled the serial port all together and rebooted. Upon reboot my system is back to normal. Boot up took normal amount of time.
I have a full install upgrading from 2.2.1

Any questions let me know I'll see what I can do.

dr.diesel

Yup, same here, fixed! I disabled the serial port and it's back up and normal.

ptt

Yup… same here

Full install (64bits) on a "cheap" Asrock C70M1, 8Gb of RAM, 80Gb SATA HDD.

"Solved" disabling "Serial port"

Michael Sh.

@cmb:

do you know which file specifically? That timeline seems to match some loader.conf changes for serial console, but I don't see how that would impact things in that way. That's been tested on numerous different hardware platforms and VMs, not sure how other situations can be different.

Immediately after the upgrade file loader.conf contains:


boot_serial="YES"
comconsole_speed="9600"
hw.usb.no_pf="1"

Сleaning it solves the problem.

Crescens

@cmb:

Those affected, are you running full installs or nano? What kind of hardware? Is the serial console enabled?

FWIW, I'm running on a cheapo eMachines w/ Atom processors and was having the same issue with the upgrade (full install). Wiping back to a clean install booted fine, but as soon as I imported my old config, it would slow down again.

I don't recall what the status of the serial console was initially, but like the others above, disabling my serial port in the BIOS allowed it to boot up normally.

Trel

I did a fresh install of 2.2.2 and restored my config.
Immediately after that, it did the slow down again.

Disabling the serial port in my bios fixed it for me as well.

this is a low risk upgrade

To everyone in this thread. I recommend NEVER playing Russian Roulette.

pfff

Hi,

Upgrade from full install of 2.2.1 to 2.2.2 on a

Intel DQ77KB
Xeon E3-1265v2
8GB 40GB Intel mSATA SSD

Running pfsense without problems for about a year. Same problem where the system boots character by character with a speed reminding me of my first 150 baud modem :). Disabled the serial port and the system boots fine with connectivity restored. I forgot to check which BIOS version I had installed, I'll check upon request. Just filing to perhaps aid in finding a pattern. Thanks folks for finding a workaround so fast.

IMG_0619.JPG_thumb

cmb

@Michael:

Immediately after the upgrade file loader.conf contains:
boot_serial="YES"
comconsole_speed="9600"
hw.usb.no_pf="1"
Сleaning it solves the problem.

Thanks, that's helpful. I think it's the boot_serial line on its own that does it, but have no means of confirming as it seems to be somehow hardware-specific.

Knight

@Michael:

Zotac IONITX-P-E, 4GB RAM, 1TB HDD. Full install AMD64. Serial console disabled.
I don`t know which file specifically, but is top level of /boot - not a kernel. Can an experiment, but it will take some time.

I have similar hardware but Atom based…

Disabling the serial port fixed the problem, thank you jwhostet (I believe he is the first one who suggested disabling the serial port)!

I guess it's trying to access a serial console and stays stuck there...

Is it possible to temporarily deactivate offering the update until this is fixed so that nobody else gets caught without Internet access? The forum is not very mobile friendly so it was a pain to search for a fix...

Nick