Kernel Panic

pwnell

1 hour, crashed:

2.0-BETA5 (i386)
built on Wed Feb 9 01:34:47 EST 2011

crash3.jpg_thumb

crash4.jpg_thumb

FisherKing

Just reporting my experiences -
Running 2.0-BETA5 (i386) built on Wed Feb 9 00:54:34 EST 2011 on both machines. (Did a clean install)
uptime = 7+ hours

Testing CARP & failover, FTP traffic, OpenVPN client/server setup.

No crashes so far, and they used to be pretty easy to produce.

This is only a simple test environment, so it doesn't get regular traffic, only a single client at a time for now.

geewhz01

I'm getting a panic in today's snapshot, 2.0-BETA5 (amd64)
built on Wed Feb 9 19:39:50 EST 2011 . This was caused I believe by syncing to slave. I was in the process of setting up a new interface on the master and configuring a vpn to it.

Andy

pfsense2911.png_thumb

eri--

This is master or slave?
That seems like an impossible trace but i will look at it after the information.

geewhz01

This is on the slave. I've not had any problems on the master with this, just the slave.

Thanks,

Andy

sammyfusionsleep.com

snapshot from 2/9/2011.
Dell Poweredge 860
Intel Pentium D CPU 2.80GHz
2 gigs ram.
Openvpn client export plugin is the only plugin installed.
pptp server for remote clients.
4 ipsec tunnels to other networks.

Crashes get stuck at db> prompt.
I have been unable to find a way to reliably trigger a crash but it does so every 24 hours or so.

Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 01
fault virtual address= 0x6c
fault code= supervisor read, page not present
instruction pointer= 0x20:0xc04ee165
stack pointer        = 0x28:0xc5b89c20
frame pointer        = 0x28:0xc5b89c34
code segment= base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process= 8 (pfpurge)
[thread]
Stopped at      pf_state_tree_ext_gwy_RB_REMOVE_COLOR+0x25:   cmpl $0x1,0x6c(%edx)
db>

Happy to provide additional information.[/thread]

jimp

@sammy@fusionsleep.com:

snapshot from 2/9/2011.
[…]
Stopped at      pf_state_tree_ext_gwy_RB_REMOVE_COLOR+0x25:   cmpl $0x1,0x6c(%edx)
db>
Happy to provide additional information.

We also need the output of "bt" at that prompt. Also, is this i386 or amd64?

sammyfusionsleep.com

Will do the bt at the prompt next crash.

snapshot from 2/9/2011.
Dell Poweredge 860
Intel Pentium D CPU 2.80GHz
2 gigs ram.
Openvpn client export plugin is the only plugin installed.
pptp server for remote clients.
4 ipsec tunnels to other networks.

jimp

None of that tells us if you used a 32-bit (i386) or 64-bit (amd64) snapshot.

sammyfusionsleep.com

i386, sorry, I didn't realize the amd64 snapshot would run on a pentium D.

jimp

It may, it may not, I'm not sure what that CPU can do… but it's always best to provide the information requested rather than relying on people to guess what you may have done based on the hardware you have.

eri--

Ok i think i got even this one handled.
Wait for the next snapshot and report back.

disa

2.0-BETA5 (amd64) built on Fri Feb 11 06:51:36 EST 2011 : I was able to add a CARP IP to the master (2.0-BETA5 (amd64) built on Fri Jan 21 23:51:34 EST 2011) and the slave got it but then I've added a certificaton autority on the master and the slave crashed.
By the way: if I add the CA to my primary host, should I be able to use it from the slave right?
thanks

14022011233.jpg_thumb

14022011234.jpg_thumb

cyber7

Hi Guys

I keep getting a kernel panic:

pf_state_tree_id_RB_REMOVE_COLOR+0x25 empl

This keeps happening every so often.

Anything I can do?

Kind regards
Aubrey Kloppers

jimp

Make sure both of your firewalls are on the latest snapshot and try again. Those panics should be cleared up.

disa

Upgraded the slave to 2.0-RC1 (amd64) built on Sun Feb 13 23:53:14 EST 2011.
Crashed after installing autobackup package on master (sync started and slave crashed): I'm really scared to upgrade the master node to the EC1 as I've already put the cluster in production…is the commercial support going to support me even if I'm running on 2.0? thanks

14022011236.jpg_thumb

jimp

Yes, commercial support will assist you even if it's 2.0. Your panic is different than the previous posted in this thread though.

disa

Ok,
I'll try to upgrade the master node in two hours. Thanks

eri--

Can you describe please your setup?

EDIT: I put even more safety belts so your carp panic should not happen on new snapshots.

disa

Hi, I'll open a ticket tomorrow with all the details on my setup. By the way, I have the 2 nodes running 2.0-RC1 (amd64) built on Sun Feb 13 23:53:14 EST 2011 for a few hours without problems. I didn't work on any new carp ips, only on openvpn: the master was synced to the slave many times without problems. I'll try to play more with carp tomorrow and let you know :-)
thanks