Cannot keep 2.0.2 pfsense firewall from crashing daily in production environment

rclaus

my previous message seemed to not get much response and i am struggling trying to figure out why i am having so many crashes.
my apologies for jumping the gun and posting new message and thank you for your reply.
i have not tried 2.03 yet since this is production fw and leary of applying beta code.
regards
Richard

jimp

2.0.3 is more stable than 2.0.2. Don't consider it a "beta". It's practically RELEASE we are just waiting on FreeBSD to issue an OpenSSL security advisory before we can wrap it up.

And multiple threads are never the correct answer. One issue, one thread.

rclaus

noted and understood about multiple threads. i wont do that again.
could you tell me where i can get the 2.0.3 code? i am unable to locate.
thanks

jimp

Follow the link in the earlier message I posted.

felipe.fsso

rclaus,
I have the same problem. Please give us a feedback after 2.0.3 install.

tnx

rclaus

installed 2.0.3 this morning and it crashed about 2 hours ago >:(

rclaus

looking at the dmesg.boot log i have the following error on all 4 of the intel nics
"Memory Access and/or Bus Master bits were not set!"
was wondering if this error be related to my daily crashes on pfsense 2.0.3 on amd64 build?

rclaus

this issue is resolved now. i installed 2.1 beta version which has newer release of FreeBSD and updated Intel nic drivers and i am having no more daily crashes.
i assume the older version of FreeBSD that the 2.0.x pfSense uses had bad em(4) drivers :) the 2.1 beta version is performing well for me.
thanks
Richard

jon_pow

@rclaus:

i assume the older version of FreeBSD that the 2.0.x pfSense uses had bad em(4) drivers :)

I confirm it, there is something wrong with the em(4) drivers, even in the PRE-RELEASE 2.0.3 version (amd64). Tested with multiple machines, all wtih Intel NICs.
Is there a chance to correct the driver before launch 2.0.3 Final Release ?

jimp

We've seen a few complaints about the em drivers but nothing specific enough to act on. We can certainly update the drivers, but it would be most helpful to know what is wrong so we can confirm fixes.

I have em(4) NICs on practically everything (physical and virtual) and have had zero issues on 2.0.x or 2.1. It's not a universal/general issue, it must be specific to a certain set of chips.

jon_pow

Jimp,

I had open this thread with a lots of info:
http://forum.pfsense.org/index.php/topic,60237.0.html

I don't know if it's enough.

Unfortunately, I can't reproduce the crash in a lab yet.

rclaus

i also unable to reproduce the error but it happened consistently on a daily basis. my environment was a vm running on the kvm hypervisor
the physical nics are e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI
the hypervisor os is Ubuntu 11.10 (GNU/Linux 3.0.0-16-server x86_64)