<![CDATA[Kernel panic in amd64 Thu Nov 4 23:13:51 UTC 2010 build]]>Upgrading from working version: Wed Nov  3 15:52:22 UTC 2010  (fresh install)

To latest amd64: Thu Nov  4 23:13:51 UTC 2010

After reboot, machine hangs at:

IPsec: Initialized Security Association Processing.
panic: tcp_init

Screenshot attached.

Have encountered this on both real hardware (dell boxes) and on Virtualbox VMs.

So… I think it's just a broken build?

Rob

pf_amd64.png
pf_amd64.png_thumb

]]>https://forum.netgate.com/topic/27788/kernel-panic-in-amd64-thu-nov-4-23-13-51-utc-2010-buildRSS for NodeSat, 18 Apr 2026 13:06:26 GMTFri, 05 Nov 2010 13:31:40 GMT60<![CDATA[Reply to Kernel panic in amd64 Thu Nov 4 23:13:51 UTC 2010 build on Tue, 09 Nov 2010 19:09:11 GMT]]>Current snap is OK:

2.0-BETA4 (amd64)
built on Tue Nov 9 17:26:01 UTC 2010

]]>https://forum.netgate.com/post/252205https://forum.netgate.com/post/252205Tue, 09 Nov 2010 19:09:11 GMT<![CDATA[Reply to Kernel panic in amd64 Thu Nov 4 23:13:51 UTC 2010 build on Sat, 06 Nov 2010 14:29:28 GMT]]>Known issue:

http://redmine.pfsense.org/issues/995

You have to reinstall from a good ISO to get it back, since it won't boot far enough in any mode to get back to a working state.

]]>https://forum.netgate.com/post/251831https://forum.netgate.com/post/251831Sat, 06 Nov 2010 14:29:28 GMT<![CDATA[Reply to Kernel panic in amd64 Thu Nov 4 23:13:51 UTC 2010 build on Fri, 05 Nov 2010 19:57:54 GMT]]>Any idea how to roll back the firmware using a known working .gz?  Any way to do this in the boot console?

]]>https://forum.netgate.com/post/251793https://forum.netgate.com/post/251793Fri, 05 Nov 2010 19:57:54 GMT