What driver version is that? Did you try any of those tunables listed there? Steve

I had the exact same issue going to 2.3.3_1. I think the root cause of this issue is a sector errors that I saw in the console when it boot up. This is how it looked: ls -l /usr/local/lib/libintl* -rw-r–r--  1 root  wheel  0 Apr 19 21:59 /usr/local/lib/libintl.a lrwxr-xr-x  1 root  wheel  0 Apr 19 21:59 /usr/local/lib/libintl.so -> lrwxr-xr-x  1 root  wheel  0 Apr 19 21:59 /usr/local/lib/libintl.so.8 -> -rw-r--r--  1 root  wheel  0 Apr 19 21:59 /usr/local/lib/libintl.so.8.1.5 lrwxr-xr-x  1 root  wheel  0 Apr 19 21:59 /usr/local/lib/libintl.so.9 -> Notice the size. luckily I had another pfsense installed with the same version, so I grabbed the libintl.so.8.1.5 from there.

I'm on 2.3.3-RELEASE-p1.  Looks like you are on 2.3.2.  Maybe those files are different between versions.  You could try to spin one up in Virtualbox and extract the files from there.  That could get you going.

What is the model of the GPS Serial unit you are using?

I had the same problem with squidguard. I updated pfsense from version 2.3.3 to 2.3.3_1 and it solved for me.

You can try a couple of option 13 in console -> GUI update cycles, switching back and forth between stable and snapshots in between (skip the actual updates from console and GUI). Or just ignore it.

I figured it hadn't a clue but couldn't work out why it was all going to hell. What I've done now is to move the 2nd one (here, it was high up and while you couldn't see it it was in the open - not IN the cupboard ;) ) to a different room, where there is another switch so I could plug it in. SAme details as the other one so I am presuming my devices will swap from one to another depending on signal. The coverage is really just needed to get to the garage which is away from the house. The original point is as far away from that as is physically possible! Just thinking there that the usual 10/100 card that was teir originally would have been fine for the 72Mbps connection. I did replace the PCs in the house onbaord cards (and the pfsense cards) with 1GB just for internal traffic - a lot of file shifting going on. Thanks for the help.

@renegade: Same here. After upgrading there was no connection to the internet although ppp had a public ip address. I have to disconnect and reconnect manually. This problem exists since 2.3.1 and is in most times reproducible after reboot. Already made a clean install and restored config. Using a vigor 130 for German adsl telekom. I confirm the same problem with 2.3.1 and Telecom Italia as provider. My warkround was to disable the 'fake interface' that i created to access the modem. Since than the connection is stable as never before!

Hi Tnx for your Answer  ,  my problem resolved  So Tnx

@EricE: @2chemlud: This whole TRIM thing is a pile of sh*t on i386 BSD… TRIM is an ugly hack, period.  Mainly a symptom of trying to graft old storage technology that works one way on top of flash memory that works an entirely different way.  Hopefully someone will come up with a replacement for SATA and develop a native flash memory stack end to end. Until then I just buy SSDs that are over-provisioned and do their own garbage collection irrespective of TRIM.  Most Sandforce based SSDs work this way - it just takes a bit more digging to find 'em. With regard to  over-provisioned SSD a good article (at least from Kingston) is https://www.kingston.com/en/ssd/overprovisioning Seagate: http://www.seagate.com/gb/en/tech-insights/ssd-over-provisioning-benefits-master-ti/

Gents, Ultimately I reloaded 2.3.3 and once that came up was immediately presented with the opportunity to update to 2.3.3_1 - which I am pleased to say went off without a hitch. I may have a motherboard issue in that I saw numerous indications on the console during the re-installation that most of my USB ports were having issues remaining "attached" to the several thumbdrives I tested. This complication may account for my failed effort to "automatically restore during the installation" but ultimately I was able restore the config file via the GUI. And then there is the suggestion of an I/O issue in the log noted by doktornotor…  :-\ Although underlying hardware issues may remain, I'm pleased that for now at least my system seems to be operating normally.  ;) Thanks for your assistance.  :)