Created attachment 283871 [details] dmesg of falied initialization (1000baseT SFP in) The NIC is: 01:00.0 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 01) 01:00.1 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 01) If the NIC has a 1000baseT SFP module plugged in, the driver will fail to initialize it. Tried 3 different brand SFP modules, same problem with all of them. Removing the module, doing an rmmod then modprobe, and the NIC initializes fine; AFTER it has initialized, I can plug in the same 1000baseT SFP module, and it will immediately start working with no problem whatsoever. So the issue is only when the module is already plugged in while the driver loads (e.g. on boot-up). Messages are as follows (also attached). $ sudo grep be2net /var/log/syslog.1 Jul 19 22:39:19 natsu kernel: [ 1.885490] be2net 0000:01:00.0: be2net version is 11.4.0.0 Jul 19 22:39:19 natsu kernel: [ 1.886037] be2net 0000:01:00.0: PCIe error reporting enabled Jul 19 22:39:19 natsu kernel: [ 1.886119] be2net 0000:01:00.0: Waiting for POST, 0s elapsed Jul 19 22:39:19 natsu kernel: [ 3.900096] be2net 0000:01:00.0: Waiting for POST, 2s elapsed Jul 19 22:39:19 natsu kernel: [ 5.916093] be2net 0000:01:00.0: Waiting for POST, 4s elapsed Jul 19 22:39:19 natsu kernel: [ 7.932101] be2net 0000:01:00.0: Waiting for POST, 6s elapsed Jul 19 22:39:19 natsu kernel: [ 9.948093] be2net 0000:01:00.0: Waiting for POST, 8s elapsed Jul 19 22:39:19 natsu kernel: [ 11.964085] be2net 0000:01:00.0: Waiting for POST, 10s elapsed Jul 19 22:39:19 natsu kernel: [ 13.980093] be2net 0000:01:00.0: Waiting for POST, 12s elapsed Jul 19 22:39:19 natsu kernel: [ 15.996090] be2net 0000:01:00.0: Waiting for POST, 14s elapsed Jul 19 22:39:19 natsu kernel: [ 18.012094] be2net 0000:01:00.0: Waiting for POST, 16s elapsed Jul 19 22:39:19 natsu kernel: [ 20.028084] be2net 0000:01:00.0: Waiting for POST, 18s elapsed Jul 19 22:39:19 natsu kernel: [ 22.044091] be2net 0000:01:00.0: Waiting for POST, 20s elapsed Jul 19 22:39:19 natsu kernel: [ 24.060083] be2net 0000:01:00.0: Waiting for POST, 22s elapsed Jul 19 22:39:19 natsu kernel: [ 26.076091] be2net 0000:01:00.0: Waiting for POST, 24s elapsed Jul 19 22:39:19 natsu kernel: [ 28.092103] be2net 0000:01:00.0: Waiting for POST, 26s elapsed Jul 19 22:39:19 natsu kernel: [ 30.108090] be2net 0000:01:00.0: Waiting for POST, 28s elapsed Jul 19 22:39:19 natsu kernel: [ 32.124103] be2net 0000:01:00.0: Waiting for POST, 30s elapsed Jul 19 22:39:19 natsu kernel: [ 34.140089] be2net 0000:01:00.0: Waiting for POST, 32s elapsed Jul 19 22:39:19 natsu kernel: [ 36.156103] be2net 0000:01:00.0: Waiting for POST, 34s elapsed Jul 19 22:39:19 natsu kernel: [ 38.172089] be2net 0000:01:00.0: Waiting for POST, 36s elapsed Jul 19 22:39:19 natsu kernel: [ 40.188102] be2net 0000:01:00.0: Waiting for POST, 38s elapsed Jul 19 22:39:19 natsu kernel: [ 42.204088] be2net 0000:01:00.0: Waiting for POST, 40s elapsed Jul 19 22:39:19 natsu kernel: [ 44.220101] be2net 0000:01:00.0: Waiting for POST, 42s elapsed Jul 19 22:39:19 natsu kernel: [ 46.236087] be2net 0000:01:00.0: Waiting for POST, 44s elapsed Jul 19 22:39:19 natsu kernel: [ 48.252100] be2net 0000:01:00.0: Waiting for POST, 46s elapsed Jul 19 22:39:19 natsu kernel: [ 50.268087] be2net 0000:01:00.0: Waiting for POST, 48s elapsed Jul 19 22:39:19 natsu kernel: [ 52.284099] be2net 0000:01:00.0: Waiting for POST, 50s elapsed Jul 19 22:39:19 natsu kernel: [ 54.300087] be2net 0000:01:00.0: Waiting for POST, 52s elapsed Jul 19 22:39:19 natsu kernel: [ 56.316099] be2net 0000:01:00.0: Waiting for POST, 54s elapsed Jul 19 22:39:19 natsu kernel: [ 58.332086] be2net 0000:01:00.0: Waiting for POST, 56s elapsed Jul 19 22:39:19 natsu kernel: [ 60.348099] be2net 0000:01:00.0: Waiting for POST, 58s elapsed Jul 19 22:39:19 natsu kernel: [ 62.364085] be2net 0000:01:00.0: POST timeout; stage=0xfd01 Jul 19 22:39:19 natsu kernel: [ 62.364308] be2net 0000:01:00.0: Emulex OneConnect(be3) initialization failed Jul 19 22:39:19 natsu kernel: [ 62.364462] be2net: probe of 0000:01:00.0 failed with error -110
Created attachment 283873 [details] dmesg of successful initialization (no 1000baseT SFP plugged) for reference
In fact digging into this some more, it turns out the card will lock-up the machine during the BIOS initialization process, if such an SFP is inserted and it has an active 1Gbps link. So I guess this can be closed as not the Linux driver fault, perhaps incompatible SFPs (all 3?) or buggy card firmware.