Ah, so in order to do this, I'd have to have 4 nics in each server, 2 frontside, 2 backside.  Plus, those nics would have to support team failover on whatever OS they're using (mostly MacOS X Servers, and now I'm adding in about 10-11 FreeBSD servers). Yay…that's a lot of nics.  Some of these boxes don't even have that many pci slots.  I know for fact that several of the on-board gigabit ports are supposed to replace the need for pci slots, so they only have 1-2 slots available. Switch failover may be a lost cause in my environment.  I may just have to be ready with the swappable switch sitting there as a just-in-case measure. :(

Actually, upgrading to latest snapshot didn't solve the issue. But i found a fix! Basicaly these xseries spare an internal adaptec controller and a pci board with the ServeRAID controller. That internal controller has no devices attached to it in my server. Disabling the internal adaptec controller seem to chase that bad timeout.. Boot isn't delayed anymore after finding ipsd0 logical volume.

Well to answer my own question. I was reading around on the freebsd mailing list and found that the message is the result of a known, but harmless, bug in dc(4). Since its not a show stopper I'll let it slide.

You may want to test a recent FreeBSD 6.1 beta and see if this an issue there as well while its still in the beta cycle.

Patches do not apply to 6.1. Last update is 2004, this is not something we want in our codebase.

Check out the high-end pci-x and pci-e nexcom boxes.  I have a feeling you will want the dual xeon model.

:D Thanks, thats fix it. Enabling and disabling polling with the web gui now works.

Thank you very much for the quick response.

1 have 1GHz P3 and 512 Mb RAM with Intel Server DualPort Server Cards and have 100MBit wirespeed performance

The 4805 should work fine with the iso image, embedded has had a lot of stuff removed lately. If it's not supported in our kernel build i'm sure we can add the correct "device blah" line to the kernel. You can find the current kernel config here http://pfsense.com/cgi-bin/cvsweb.cgi/tools/builder_scripts/conf/pfSense.6?rev=1.14;content-type=text%2Fplain

The kernel in the latest builds has been "trimmed" quite a lot lately. I think you will find that the newest builds are much faster due to several improvements (like APC, smaller kernel for faster boot, a few tweaks here and there).

I can tell you right now that a VIA cpu at 533 is not going to give you anything close to gigabit thruput. Other then that the board looks ok, and will most likely work fine with a embedded image.

you can use the embedded or regular version of pfsense with the box. All you need to do is to load either image onto the compact flash or hard drive. After loading it on the boot device of your choice the video card doesn't help much other than to post check as there is no keyboard interface. Also, you don't need to have a pci video card as there is onboard video(trident chipset). I have yet to get the serial port working properly with pfsense nor the leds on the front of the chassis. When booted up all i normally see is the spinning thing.

So far, I've seen this error only because of an IRQ-Problem with an ACPI System, running pfsense on. It seems to me, that the realtek-driver is not able to share IRQ's under some circumstances with other drivers… So, you might probably put the card in another pci-slot, and check, if the error occurs further on. Second, it may help to disable unneeded onboard components, as USB or LPT or a soundcard.

@jeroen234: disable dma in bios off youre pc use pio mode By bios doesnt have that option.