Kernel Panic
-
Hi,
Like cyber7, I'm getting kernel panics (pf_state_tree_id_RB_REMOVE_COLOR, pfpurge is always the current process) since two weeks (approx. 2 to 3 times a week) on a VMWare setup. Here's a screenshot :
-
spacelui,
amd64 or i386? snapshot date? What type of setup, CARP? Multi-WAN? anything special going on with FTP/PPTP? Any more detail might help. Posting the same panic that someone else had doesn't help much (unless you also have the bt output to go with it) but if we can track down what about your setup might be related to the panics, that would be more helpful. What we need is to find some commonality between the people still getting them.
-
Hi Guys.
I am still getting the same panic, just this time with a cmpl error. I am busy updating to the new snapshot, but why is it that after months of running fine, I am starting to see this panic?Kind regards
Aubrey Kloppers
ps - I am updating to the following snapshot:Auto Update Download Status
–--------------------------------------------------
Current Version : 2.0-RC1
Latest Version : Tue Feb 15 16:36:07 EST 2011 -
If it's a different error, it's not the same panic. We need the full text of the panic and the backtrace (bt at the db> prompt) in order to say anything.
But don't report anything until you've replicated it on the new snapshot you're updating to.
-
Thank you Jim.
ps - It was nice to chat to you yesterday. Do you not ever sleep :)Kind regards
Aubrey Kloppers -
Sorry, I cut the details…
It's a 2.0-RC1 of yesterday running on an i386.No multiwan, no carp and I have indeed some incoming pptp traffic going to a nated server on the lan. VMWare ESX setup. I do an upgrade every week, it began to happen on the 28th of january. I tried to look in the repo to see commits between 21st and 28th, to see if something relevant has changed, but a lot of things happened... plus, I'm not sure that couldn't happen before.
Next time it happens, I'll post the backtrace.
Edit : I reverted to the last backup I had before upgrading on the 28th, it's a Fri Jan 7 15:25:33 EST 2011 snapshot…
-
Hi Guys
look at my panic: http://forum.pfsense.org/index.php/topic,33403.0.html
and see if this does not solve your problemsKind regards
Aubrey -
Hey Aubrey, changing my mtu's didn't fix anything. In fact it caused a panic on both boxes when trying to apply the changes. I don't think I will try that again.
-
Hey Aubrey, changing my mtu's didn't fix anything. In fact it caused a panic on both boxes when trying to apply the changes. I don't think I will try that again.
Did you get the panic/crash info when it did that? Also, are you on i386 or amd64? What snapshot date?
-
No, I didn't. Sorry. But I'm sure it will happen again soon and I have the camera ready. I am running i386 and build Mon Jan 31 07:16:37 EST 2011 right now (saw the same issues with Mon Feb 14 02:12:45 EST 2011 and I can't remember which one from the 15th).
-
Update to the most current snap ASAP and then test again. Testing on old snaps isn't likely to provide any useful feedback for this. There were patches after those dates to help prevent panics in other situations.
-
I was able to make my CARP slave fail again (seems reproducable) - I was changing the mtu's back to default, if making one change and applying it things seemed fine, when I changed a few of them and applied them but applied changes after a few (maybe 5) then it hung.
I will update to the latest snap and see if I can make it fail again…
-
I updated my CARP backup to the latest snap - Thu Feb 17 02:14:25 EST 2011 - and ran through similar motions that caused the panics before with no issues. I have updated my master as well and will update if things fail again.
-
Can any of you with the pf_state_tree_id_RB_REMOVE_COLOR panic
try and set debug.pfpptpproxy=1 and see if they get the panic? -
Sure, let me now how to do it (sorry) and if I get the panic running today's snapshot that can be my next step.
-
Remember messing with the GUI when this happened, and then it stopped working… and then that.
-
Please give info on each screenshot you put in here.
Its absolutely required the date of the snapshot and how the box is cofnigured: carp, vlan, pptp,….@ acherman
Go to system->Advanced->System tunables->Click +(at the end)Tunable: debug.pfpptpproxy
Value: 1
Description: Testing pptp fixClick save and try to see if it panics still.
-
Had 3 panics on my CARP master and 1 on my backup - I assume they were panics, lost comms to them but no physical access, just cycled power remotely. I just entered the tunable requested, I will update when/if something happens. I will upload a drawing of my network config when I get to the office, as well as more config details.
-
Had another panic on my master this morning as I was doing up a quick drawing - looks like the same situation, even with the pptp tunable noted by ermal. It ran fine for almost 14 hours yesterday before the first one last night (from 9:05 am to 10:56 pm). Anyway, screenshots from this mornings panic:
Now, here is a basic layout of my config:
Directly connected to the Sync interface is an identical box with all other interfaces running in parallel. Our WAN is a static connection. DHCP is served out to our corp LAN, remote office LAN, and a couple of our WiSP VLANs (625, 626) - I do not have the CARP backup DHCP turned on. The only VPN I have configured is OpenVPN (one server connection). The only package installed is the OpenVPN client config export utility. I do have a number of virtual IPs configured for inbound and outbound NAT. No traffic shaping turned on. I think that's it for special stuff, let me know if more is required, or I can upload my config files.
I am still running on the build from Thu Feb 17 02:14:25 EST 2011, with the pptp fix tunable noted by ermal.
-
I just put a patch up.
The snapshot has to build but when it comes out try with that.
