I dont expect a kernel change…

I don't have anyway to debug my crash logs and possibly help the freebsd people out.

I know a few pfsense devs have a way to possible fix or provide better details to them for solving this.

I am using a motherboard that 2 of pf sense's hardware products run on...

I have been annoyed by the in the past when setting up systems that are currently offline.
Bug report https://redmine.pfsense.org/issues/7031
Suggested fix https://github.com/pfsense/pfsense/pull/3306

You fixed it, working as expected now!

Thank you @jimp

@jimp:

Maybe they are trying IPv6 first then falling back to IPv4?

Good thinking, I asked him to check that using 'IPv6 and more' for Android, however, there is no guarantee he did so I'll ask him again.

@jimp:

Try it again with a current snapshot

That fixed the boot issue, apparently he struggled with the display over serial but that's a different issue. :)

Thanks for the fix jimp.

He has come up with another issue I cannot replicate, I'll post a separate thread on that one.

I have had same crashes on igb cards with 2.4, but with shaper enabled and speedtest.net  test, I think load does matter. But on latest versions I can not reproduce the crash.
All I have in loader.conf.local regarding igb is
kern.ipc.nmbclusters="131072"
kern.ipc.nmbjumbo9="20000"
kern.ipc.nmbclusters="1000000"
legal.intel_wpi.license_ack=1
legal.intel_ipw.license_ack=1

@jimp:

Are you seeing the exact same error as the person on that page? That isn't pfSense, so there is no guarantee the behavior would be similar.

Mount the memstick image in another pfSense or FreeBSD box and edit /boot/loader.conf or /boot/loader.conf.local on the stick (create one if it does not exist) and add this line:

kern.cam.boot_delay=”10000″

See if that helps.

I saw it, I did a fresh install at the weekend and I cannot remember what I did to fix it as I thought at the time it was just me. Whatever I did I got past it and all was good.

However, one of my testers was doing fresh install of 2.4b and sent a nice picture..

has anyone came across this yet? I have tried the latest snapshot and its still the same,

it works fine with 2.3.3

thanks!

More info…

https://www.freebsd.org/doc/en_US.ISO8859-1/books/dev-model/committing.html

Here is where the commits to FreeBSD are listed:

https://freshbsd.org/

Screenshot of the floating rules.


Does anyone know why?

Probably someone does.

Or perhaps asynchronous routing.? There should be packet trying to make a connection before the [S.] packet.. Why don't we see that one? How is it routed 'around' pfSense?

I thought I had it working, but on the first install although it said all OK there were no entries in my rules; removed it and added the early shell 'touch' and refetched xmlrpc.inc and re-installed and still nothing showing in the rules. Any ideas?

fs0:\EFI\BOOT\BOOTX64.EFI should not work for DVD, I think.
Depending on hardware you must search for similar instructions like this one http://www.dell.com/support/article/us/en/19/SLN142679/en
Or if you hardware supports booting into EFI shell you can research boot entries with bcfg utility. You can even make an USB with EFI shell and boot from it.
https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2/ShellBinPkg/UefiShell/X64/Shell.efi
Just format your USB with FAT32 and rename/create path  /EFI/boot/bootx64.efi
Boot from USB and you must enter into shell directly. Use https://software.intel.com/en-us/articles/efi-shells-and-scripting/ for help

Not sure if anything changed, but I just installed the 2.4.0.b.20161125.1740 snapshot, and I did not have this issue.

Thanks!

Good to hear. We also fixed some issues with collecting data from crash dumps, so if it does crash again on a current snapshot you'll get the correct info this time.