I'm no Linux/Unix guru, nor do I have very much time I can allocate to seeing this through to a resolution, but I will try to assist in any testing or data collection needed to hopefully address this issue. I have not looked up the correlation between pfSense and FreeBSD versions. Issue does not occur with NC112T (Intel 82574L-based single port NIC)Ĥ. Issue occurs on NC360T (dual-port Intel 82571EB NIC)ģ. Issue reoccurs with on every NC364T card when testing several of themĢ. Other user reports (see Reddit discussion link) indicate that:ġ. Hardware works perfectly fine when booting to Ubuntu live USB for testing Issue reoccurs when using either USB or SSD boot mediaĥ. Issue reoccurs using included 7.6.1 and latest 7.7.5 Intel driversĤ. Issue reoccurs with onboard NIC disabledģ. Issue reoccurs using both UEFI and Legacy boot methodsĢ. There are no log entries or bug checks present (that I have seen)ġ. Step 4) You need to make a few changes on your server. Step 3) Upload both files ( File 1 & File 2) to your server and change the permissions to 755. Step 2) Create index.html (or a page from the same domain) file and paste our widget code. System has been left in unresponsive state for 12+ hours with no change. Step 1) Create a domain/subdomain for your server. I have to hold power button to do a hard reboot. No amount of Ctl-Alt-Del will do anything. When it crashes, the system goes 100% unresponsive. Crash happens within the first 60 seconds. Run "dhclient em3" to get network access.ħ. Boot up in UEFI or Legacy to flash driveĥ. HP NC364T Network Controller (Uses Intel 82571EB chipset)ġ. Hardware used for testing and reproduction: I have confirmed this issue is present even on the FreeBSD 12.0 release so it is not an issue introduced by pfSense or OPNsense. Initial discussion of this issue can be found in the pfSense subreddit: When using an Intel 82571EB quad-port gigabit NIC (HP NC364T) in a system with an AMD Piledriver or Steamroller APU, any taxing Ethernet workload will cause the entire system to either permanently lock up (requiring a hard reboot by holding down the power button to reset), or crash and reboot.
0 Comments
Leave a Reply. |