PfSense Crashed

jits

Ahh..whew!! That's a good crash!

At least it wasn't someone on the network trying to play master hacker.

markuhde

Anyone dare load today's build yet?

mdima

@markuhde:

Anyone dare load today's build yet?

Why, the 24th April build is running soooooo well… :D

eri--

The changes that caused the crashes have been reverted.
So the new snapshots are safe.

I would have been interested on your backtraces shown in the info when you rebooted pfSense, if you can get those.

mdima

I confirm… after a remote update the box is still there...

Thank Ermal to you and all the staff!

Michele

rcfa

@ermal:

The changes that caused the crashes have been reverted.
So the new snapshots are safe.

I would have been interested on your backtraces shown in the info when you rebooted pfSense, if you can get those.

So was it the build process crashing that caused the issue, or a code change?
If code change, what was it? Just curious as to what has such strange effects.

Oh, yes, and also, so far no issues with the new build…

markuhde

Thank you everybody! Updating now (no one's on the campground today so it's perfect for this).

jits

Hi.

How do you do a backtrace?

I'm doubtful if I can do it now. I re-installed from scratch and my latest backup were from December 2012. Serves me right!

In any case, on that particular system running an intel atom 1.3Ghz processor with Realtek daughterboard NIC card, all is well when rebooted with no network cables connected. The second I connect the LAN cable, there is a huge amount of data that starts scrolling up the screen, then it stops for half-a-sec, and reboots. Will do this repeatedly.

When cable is already connected, the screen halts at either NTP Configured or WAN Configured, then you hear the sound it makes when there is supposedly a successful reboot or restart.

lucky

Just tried today's build - 2.1-BETA1 (amd64) built on Mon Apr 29 09:14:28 EDT 2013.

So far, so good.

freebee

sbflush_internal cc 0 || mb 0xc2651c00 || mbcnt 4352

Clear-Pixel

@lucky:

Just tried today's build - 2.1-BETA1 (amd64) built on Mon Apr 29 09:14:28 EDT 2013.

So far, so good.

Not showing a Apr 29 09:14:28 build ???
http://snapshots.pfsense.org/FreeBSD_RELENG_8_3/i386/pfSense_HEAD/livecd_installer/?C=M;O=D

It's only showing ???
pfSense-LiveCD-2.1-BETA1-i386-20130429-0914.iso.gz 29-Apr-2013 09:43 85M

Was planning on doing a fresh install but I'm a bit Scared. :-\

Maybe tomorrow do a fresh install off the latest snap shot ???

lucky

@Clear-Pixel:

It's only showing ???
pfSense-LiveCD-2.1-BETA1-i386-20130429-0914.iso.gz 29-Apr-2013 09:43 85M

Was planning on doing a fresh install but I'm a bit Scared. :-\

Seems like you looked at the i386 build vs amd64, which is what I'm running. Not sure how i386 is working out.

Clear-Pixel

Oops my bad…

Guest

@rcfa:

If code change, what was it? Just curious as to what has such strange effects.

My bet would be on this one:
https://github.com/pfsense/pfsense-tools/commit/3fe8a9cd9297d64ab243fe3f38cea8b4ef147899

cmb

@alexh:

My bet would be on this one:
https://github.com/pfsense/pfsense-tools/commit/3fe8a9cd9297d64ab243fe3f38cea8b4ef147899

That's it, disabling those kernel patches gets us back to where we were last week before the bad snapshot.

Clear-Pixel

@cmb:

@alexh:

My bet would be on this one:
https://github.com/pfsense/pfsense-tools/commit/3fe8a9cd9297d64ab243fe3f38cea8b4ef147899

That's it, disabling those kernel patches gets us back to where we were last week before the bad snapshot.

What was the important s of the patches?

cmb

They weren't important. They'll have a performance improvement at some point in the future if they can be stabilized outside the main tree first.