Pfsense locking up when specific NIC is installed
-
So I recently bought a Chelsio T580-LP-CR, and when I installed it into my pfsense computer I started getting complete lock ups from pfsense where no traffic would pass through the system at all. This was happening every couple hours. When I unplugged the cables from the NIC this behavior stopped happening quite as often, but still has a system lock up every 2-3 weeks. When I remove the NIC from the system I no longer have this problem, and I never had the problem before I first installed the T580-LP-CR either. This NIC is supposed to be supported by pfsense from what I understand, and the drivers for it are already built in to pfsense. So not really sure what the problem is here. The system doesnt crash and reboot, and there is nothing in the log files that I can see. It simply locks up and traffic no longer will be routed though. I can not press the power button and let the system power off normally when this happens either, I have to hold the power button until the power cuts out, then I can boot it normally. So it isnt just the routing portion that goes down, but a full system lock up when this NIC is installed.
Anyone have some advice for what to check? Or how to make the NIC function properly with pfsense?
-
Are you running 2.4.3?
The was an issue with mbuf leaks in that showed especially badly with the cxl driver. That has been fixed for a few versions though.
Check the Status > Monitoring graphs for mbuf cluster usage.
When you say 'completely locked up' does it stop responding at the console? Try pressing Ctl-T at the console if it appears non-responsive, what output does that give?
Steve
-
Are you running 2.4.3?
The was an issue with mbuf leaks in that showed especially badly with the cxl driver. That has been fixed for a few versions though.
Check the Status > Monitoring graphs for mbuf cluster usage.
When you say 'completely locked up' does it stop responding at the console? Try pressing Ctl-T at the console if it appears non-responsive, what output does that give?
Steve
I have been on 2.4.2 since it was released, I upgraded to 2.4.3 after the most recent lockup.
Next time it happens I will try the console and see if ctrl+T does anything. Both the web connection and console did not function when this happens, but I didnt try the ctrl+T thing so ill have to see.