Enabling CARP just crashes/panics

  • Everytime I try to enable Carp my pfSense system crashes.  Searching the forums showed that this was a known issue back in May, and people were suggested to use the snapshots at:

    However, I read the warning.txt file, and don't want to use alpha code in production.  Does anyone know why this is crashing?

    It's with pfSense 1.2RC2.  I can supply the hardware details if wanted?  Or what other info would be useful?

    I've tried this with a developers kernel, and it says something like:
    panic mutex pf task mtx owned at /usr/srv/sys/contrub/pf/net/pf.c:6474
    KDB: enter: panic
    thread pid 2694 tid 100088
    Stopped at kdb_enter+0x2b: nop

    If that is any use to anyone?!

    pfSense looks really good, and I love it when it works, but I've been majorly stuggling through with various issues with it crashing on installs (ok, dodgy memory!), not being able to find CD drives (new Intel motherboard), and crashing on booting post install (seem it can't cope with a certain 80Gb hard drive, 40Gb is OK).  I'd love to get this working, but it is getting so frustrating!! CARP was the main reason I decided to go with pfSense, so anyone that has any ideas would be very grateful!

  • http://snapshots.pfsense.org/FreeBSD6/RELENG_1_2/ is what ou should use, not releng_1.

  • I'm not sure what the RELENG_1_2 means, but this snapshot releases is considered stable enough to run in production?  I notice that it doesn't have the warning.txt file all the others do.

    It does however fix the problem!

    (And it is labelled pfSense 1.2-RC3 when it boots, maybe the download mirrors should be updated to have this as the most recent copy?)

  • Yep 1.2-RC3 is very stable (better than 1.0.1) and I would use it in production. The RELENG_1 path is the next 1.3 edition in its very early stages (it is a slightly confusing numbering system maybe RELENG_1_3 would be better).

Log in to reply