2.0-RC1 fix ?
-
http://marc.info/?l=pfsense-support&m=129903385420047&w=2
http://marc.info/?l=pfsense-support&m=129913331924304&w=2
To summarize, I was the OP in that thread. Routing performance in the March 1 RC snap was poorer than expected, and inconsistent. Then on the March 4 RC snap routing performance improved to the expected level, and Seth Mos indicated that the Yandex driver had just gone into the builds.
I had no other issues with that system, except maybe mbuf leaks. I no longer have access to it.
-
Any build I've used after March 3rd has giving me a couple of issues. Mostly with the LCDproc package sockets timing out after a reboot. Restart the service and it works like it did before. I have to do this with every 'reset of states' also..And I have the NTPd issue. When using the build right before the Yandex drivers were added, no issues.
Since i'm testing the IPv6 code, I ended up using the pfSense-2.0-RC1-ipv6-i386-20110228-1715.iso.gz image and gitsync as updates are added, mostly after a mainline merge to smos git.
I've heard of some performance issues with RC1 but I haven't experience any as I'm routing over a 50/5 cable link.
-
Will be testing the following commits tomorrow once there is a snapshot built that includes them.
https://rcs.pfsense.org/projects/pfsense-tools/repos/mainline/commits/9ef97a5994abb78061277f4f29d2067b7b833a9d
https://rcs.pfsense.org/projects/pfsense/repos/mainline/commits/b2305621e59b330290d337e7855acb8e90b6dd65
Fingers crossed
-
NTPD seems to be fixed but I'm still getting the watchdog messages on the 3/19 RC1 snapshot
Mar 20 05:27:03 php: : Hotplug event detected for lan but ignoring since interface is configured with static IP (aaa.bbb.ccc.ddd) Mar 20 05:27:03 check_reload_status: Linkup starting em0 Mar 20 05:27:03 kernel: em0: link state changed to UP Mar 20 05:27:01 php: : Hotplug event detected for lan but ignoring since interface is configured with static IP (aaa.bbb.ccc.ddd) Mar 20 05:27:00 check_reload_status: Linkup starting em0 Mar 20 05:27:00 kernel: em0: link state changed to DOWN Mar 20 05:27:00 kernel: em0: Watchdog timeout -- resetting Mar 20 05:23:33 php: : Hotplug event detected for lan but ignoring since interface is configured with static IP (aaa.bbb.ccc.ddd) Mar 20 05:23:33 kernel: em0: link state changed to UP Mar 20 05:23:33 check_reload_status: Linkup starting em0 Mar 20 05:23:31 php: : Hotplug event detected for lan but ignoring since interface is configured with static IP (aaa.bbb.ccc.ddd) Mar 20 05:23:30 check_reload_status: Linkup starting em0
Edit: OK, looking good with the snap from the 20th.
-
Hello,
I'm using a Jasomi 7650 (alias Lanner FW 7650 - [network: Intel 82540EM and Intel 82551QM])
with Pfsense 2.0-RC1 (i386) built on Sun Mar 20 02:20:38 EDT 2011
and have the same problem :
Mar 21 18:52:12 php: : Hotplug event detected for opt4 but ignoring since interface is configured with static IP (192.168.5.1) Mar 21 18:52:12 kernel: em0: link state changed to UP Mar 21 18:52:12 check_reload_status: Linkup starting em0 Mar 21 18:52:09 php: : Hotplug event detected for opt4 but ignoring since interface is configured with static IP (192.168.5.1) Mar 21 18:52:09 kernel: em0: link state changed to DOWN Mar 21 18:52:09 kernel: em0: Watchdog timeout -- resetting Mar 21 18:52:09 check_reload_status: Linkup starting em0 Mar 21 18:45:02 php: : Hotplug event detected for opt4 but ignoring since interface is configured with static IP (192.168.5.1) Mar 21 18:45:01 kernel: em0: link state changed to UP Mar 21 18:45:01 check_reload_status: Linkup starting em0 Mar 21 18:44:59 php: : Hotplug event detected for opt4 but ignoring since interface is configured with static IP (192.168.5.1) Mar 21 18:44:58 check_reload_status: Linkup starting em0 Mar 21 18:44:58 kernel: em0: link state changed to DOWN
just to complet the informations …
-
Estragon, this was fixed, upgrade to a newer snap.
-
@onhel:
Estragon, this was fixed, upgrade to a newer snap.
the EM watchdog errors are fixed now?
-
Yes, I used the 3/20 update snapshot 1657 and my em's are running without error.
-
hello,
I go on the newer snap
2.0-RC1 (i386) built on Tue Mar 22 01:13:42 EDT 2011
and no more watchdog issue … (my system log entries is now so depopulate ::))incidentally, from some snap install I need to reboot after the installation in the way that the Wan interface can acquire the IP from DHCP, and these issue seam's to be resolved too ...
many tanks :)
-
yandex drivers are out now so no more guarddogs
were the yandex supposed to be better performance?