Kernel Panics
-
Received a kernel panic tonight, which I think came from the pf FTP rewrite module, but I'm not a FreeBSD expert. I rebooted and I've hit the same FTP a few times since and can't reproduce, but I figured I'd report it in any case.
FreeBSD router.xxx.ca 8.0-RC3 FreeBSD 8.0-RC3 #0: Thu Nov 19 20:05:47 EST 2009
-
Strange, here is another one an hour later. Coincidentally both of my WANs were down at this time (cable provider outage), so there was very little traffic, just lots of DHCP attempts and me trying to do some diagnostics on the modems. I've been using this hardware for about a year without any issues, ditto for this image for a week. Odd.
-
Hi
Try snaps built on Nov 20th or later, at least. See http://forum.pfsense.org/index.php/topic,20199.0.html
cheers,
-
Interesting, thanks for linking to the post I should have seen on the forum index. Upgrading now!
-
I've got a couple more of these tonight while fiddling in the DHCP server configuration. Seemed pretty reproducible, I tried making the same configuration change 3 times and all 3 it paniced on me in 'arpresolve' very similar to the last image I posted. Twice the configuration was corrupted during the failure. I'm on
FreeBSD router.home.gotroot.ca 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Wed Nov 25 22:35:41 EST 2009
now. I think the problem is something else, unrelated to FTP.
-
I am from Peru and I have the same problems when I set up with WAN option DHCP actived Can you explain us whta happened=???
-
Seems like that was resolved already, I thought.
It looks like the errors we had been seeing from either the FTP kernel proxy an ipsec sysctl patch, but both of those have been fixed.
I've been using a nanobsd image from the 27th and I had no problems making any configuration changes.
-
The panics shown here are all fixed, make sure you're using the latest version.
-
I still have the panic on arpresolve as of 2.0-ALPHA-ALPHA-20091201-0017. On intel EM cards, can be reproduced easily on cards connected to Cisco 3550-12G with TP gbic.
-
redmine.pfsense.org file a bug there
