Unexpected Issue - Intel Pro/1000 PT Quad Port Low Profile
-
It is the IBM version 39Y6138/39Y6137 - YK50KK. I got it for $27 shipped on Ebay which is why I went for it.
A very odd thing is happening with this card. It is recognized and works perfectly in both Windows and Linux, but it isn't having it with pfSense or more likely FreeBSD in general. The machine will boot and I can assign the interfaces, but this small kink is ruining it. The issue is the system rebooting. A window of about 1 to 10 minutes after booting the machine will just reboot. It happens faster if you put any load on the NIC. I've tested it without the NIC and the system will run fine over the onboard Realtek and a Wi-Fi module.
I could upload a video of the issue if requested. Very easy to reproduce as I have to do nothing for it to happen.
Specs of the machine are:
ECS KAM1-I (I have reflashed the BIOS to rule some sort of corruption out.)
AMD Sempron 3850 @ 1.3GHz
4GB DDR3 1333 (I have run memtest and that came up clean.)
IBM Intel Pro/1000 PT Quad Port Low Profile Server Adapter (39Y6138/39Y6137 - YK50KK) (Tested all ports working in Windows and Linux.)
Atheros 9285 (Tested without it installed. The issue still persists.)
2.5" 160GB 5400RPM HDD (Used in the machine this is meant to replace.) -
It is the IBM version 39Y6138/39Y6137 - YK50KK. I got it for $27 shipped on Ebay which is why I went for it.
Sold from China? There are also some fakes out at the market that will not be making problems with
Windows or Linux but perhaps with FreeBSD!Did you test the NIC under FreeBSD 10.1 only?
-
This is where I got mine. http://www.ebay.com/itm/271953268010
I have only run it on FreeBSD 10.1. I could probably try a normal FreeBSD install. Not really feeling it, but it really seems like the only thing I have left to try.
-
Maybe this will tell a story. It shows on the other three as well.
em0@pci0:3:0:0: class=0x020000 card=0x11bc8086 chip=0x10bc8086 rev=0x06 hdr=0x00 class = network subclass = ethernet bar [10] = type Memory, range 32, base 0xfe9a0000, size 131072, enabled bar [14] = type Memory, range 32, base 0xfe980000, size 131072, enabled bar [18] = type I/O Port, range 32, base 0xe020, size 32, enabled cap 01[c8] = powerspec 2 supports D0 D3 current D0 cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message cap 10[e0] = PCI-Express 1 endpoint max data 256(256) link x4(x4) speed 2.5(2.5) ASPM L0s(L0s) ecap 0001[100] = AER 1 0 fatal 1 non-fatal 4 corrected ecap 0003[140] = Serial 1 001b21ffff95f5fc PCI-e errors = Correctable Error Detected Non-Fatal Error Detected Unsupported Request Detected Non-fatal = Unsupported Request Corrected = Receiver Error Bad TLP Bad DLLP Replay Timer Timeout
-
I found something a while ago, about a HP NC364T card, which looks to be the same card:
http://h20565.www2.hpe.com/hpsc/doc/public/display?sp4ts.oid=3367979&docId=emr_na-c01501574&docLocale=en_USSomething about a recall, for which you need a valid support contract - of course. Perhaps the IBM card is the same sort of intel oem card, an maybe IBM has put out a recall for it. It's a very very slight chance that your card suffers from this issue, but a chance is better than no chance, right?
Otherwise you might check your bios for PCIe power states L0 and L1, things…? There was also something about disabling something in the BIOS because that might interfere with some PCIe cards. This is a vague memory, but perhaps it gives a clue, and maybe you can find more about this, or try a few different bios settings. Or try it in another computer, see if the problem moves with the card.
-
No issues at all in my main PC.
em0@pci0:4:0:0: class=0x020000 card=0x11bc8086 chip=0x10bc8086 rev=0x06 hdr=0x00 class = network subclass = ethernet cap 01[c8] = powerspec 2 supports D0 D3 current D0 cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x4(x4) speed 2.5(2.5) ASPM disabled(L0s) ecap 0001[100] = AER 1 0 fatal 1 non-fatal 0 corrected ecap 0003[140] = Serial 1 001b21ffff95f5fc PCI-e errors = Non-Fatal Error Detected Unsupported Request Detected Non-fatal = Unsupported Request
Now that this bit is sorted I guess this is where I go silent and find a way to get it working on the intended hardware. Thank you. 8)