ixgbe: passing parameters doesn't work?

M

Merwin

New Member
Aug 6, 2023
8
0
1
I'm trying to use the parameter allow_unsupported_sfp=1. One of the SFP modules i'm trying to use is probably not officially supported. I've tried it in/with:
- /etc/modprobe.d/ixgbe.conf
- /etc/default/grub
- modprobe
All with no result.
Also tried it with parameter debug=16 to find out if it even gets passed trough to the driver/module: no result/ no difference in dmesg logging.

I'm using the following NIC: Supermicro AOC-STGN-I2S
Checking dmesg | grep ixgbe gives the following result:
Yes, I'm using VF features on the 2nd port/working sfp module. Based on https://forums.servethehome.com/ind...iny-m920q-or-m720q-with-cx3-and-sr-iov.35664/ Pleas ignore those.

[ 1.225654] ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver
[ 1.225657] ixgbe: Copyright (c) 1999-2016 Intel Corporation.
[ 1.226237] ixgbe 0000:01:00.0: enabling device (0000 -> 0002)
[ 1.249507] ixgbe 0000:01:00.0: failed to load because an unsupported SFP+ or QSFP module type was detected.
[ 1.249513] ixgbe 0000:01:00.0: Reload the driver after installing a supported module.
[ 1.249647] ixgbe 0000:01:00.1: enabling device (0000 -> 0002)
[ 1.422007] ixgbe 0000:01:00.1: Multiqueue Enabled: Rx Queue count = 6, Tx Queue count = 6 XDP Queue count = 0
[ 1.422298] ixgbe 0000:01:00.1: 32.000 Gb/s available PCIe bandwidth (5.0 GT/s PCIe x8 link)
[ 1.422381] ixgbe 0000:01:00.1: MAC: 2, PHY: 19, SFP+: 12, PBA No: 0210FF-0FF
[ 1.422382] ixgbe 0000:01:00.1: 0c:c4:7a:8f:49:13
[ 1.425477] ixgbe 0000:01:00.1: Intel(R) 10 Gigabit Network Connection
[ 1.712359] ixgbe 0000:01:00.1 enp1s0f1: renamed from eth0
[ 4.212019] ixgbe 0000:01:00.1 enp1s0f1: SR-IOV enabled with 3 VFs
[ 4.278631] ixgbe 0000:01:00.1: Multiqueue Enabled: Rx Queue count = 4, Tx Queue count = 4 XDP Queue count = 0
[ 4.388472] ixgbevf: Intel(R) 10 Gigabit PCI Express Virtual Function Network Driver
[ 4.388475] ixgbevf: Copyright (c) 2009 - 2018 Intel Corporation.
[ 4.388575] ixgbevf 0000:02:10.1: enabling device (0000 -> 0002)
[ 4.389826] ixgbevf 0000:02:10.1: PF still in reset state. Is the PF interface up?
[ 4.389827] ixgbevf 0000:02:10.1: Assigning random MAC address
[ 4.390095] ixgbevf 0000:02:10.1: c6:84:d2:a1:ec:3b
[ 4.390097] ixgbevf 0000:02:10.1: MAC: 1
[ 4.390099] ixgbevf 0000:02:10.1: Intel(R) 82599 Virtual Function
[ 4.390179] ixgbevf 0000:02:10.3: enabling device (0000 -> 0002)
[ 4.391418] ixgbevf 0000:02:10.3: PF still in reset state. Is the PF interface up?
[ 4.391420] ixgbevf 0000:02:10.3: Assigning random MAC address
[ 4.391676] ixgbevf 0000:02:10.3: 82:0e:cd:c6:b6:80
[ 4.391678] ixgbevf 0000:02:10.3: MAC: 1
[ 4.391679] ixgbevf 0000:02:10.3: Intel(R) 82599 Virtual Function
[ 4.391724] ixgbevf 0000:02:10.5: enabling device (0000 -> 0002)
[ 4.393052] ixgbevf 0000:02:10.5: PF still in reset state. Is the PF interface up?
[ 4.393053] ixgbevf 0000:02:10.5: Assigning random MAC address
[ 4.393259] ixgbevf 0000:02:10.5: 5a:8b:68:10:77:f5
[ 4.393261] ixgbevf 0000:02:10.5: MAC: 1
[ 4.393278] ixgbevf 0000:02:10.5: Intel(R) 82599 Virtual Function
[ 7.365131] ixgbevf 0000:02:10.5 enp1s0f1v2: renamed from eth2
[ 7.393856] ixgbevf 0000:02:10.1 enp1s0f1v0: renamed from eth0
[ 7.410065] ixgbe 0000:01:00.1: setting MAC aa:bb:cc:f2:00:00 on VF 0
[ 7.410068] ixgbe 0000:01:00.1: Reload the VF driver to make this change effective.
[ 7.410073] ixgbe 0000:01:00.1: The VF MAC address has been set, but the PF device is not up.
[ 7.410074] ixgbe 0000:01:00.1: Bring the PF device up before attempting to use the VF device.
[ 7.410086] ixgbevf 0000:02:10.3 enp1s0f1v1: renamed from eth1
[ 8.423722] ixgbe 0000:01:00.1: setting MAC aa:bb:cc:f2:00:01 on VF 1
[ 8.423726] ixgbe 0000:01:00.1: Reload the VF driver to make this change effective.
[ 8.423744] ixgbe 0000:01:00.1: The VF MAC address has been set, but the PF device is not up.
[ 8.423745] ixgbe 0000:01:00.1: Bring the PF device up before attempting to use the VF device.
[ 10.436938] ixgbe 0000:01:00.1: setting MAC aa:bb:cc:f2:00:02 on VF 2
[ 10.436942] ixgbe 0000:01:00.1: Reload the VF driver to make this change effective.
[ 10.436946] ixgbe 0000:01:00.1: The VF MAC address has been set, but the PF device is not up.
[ 10.436947] ixgbe 0000:01:00.1: Bring the PF device up before attempting to use the VF device.
[ 10.440145] ixgbe 0000:01:00.1 enp1s0f1: VF 0 is trusted
[ 10.443192] ixgbe 0000:01:00.1 enp1s0f1: VF 1 is trusted
[ 10.446341] ixgbe 0000:01:00.1 enp1s0f1: VF 2 is trusted
[ 10.601764] ixgbe 0000:01:00.1: registered PHC device on enp1s0f1
[ 10.773769] ixgbe 0000:01:00.1 enp1s0f1: detected SFP+: 12
[ 10.913783] ixgbe 0000:01:00.1 enp1s0f1: NIC Link is Up 1 Gbps, Flow Control: RX/TX

I'm pretty new to this. I've done a lot of reading forums etc to try to find out what is going on. Also testing and rebooting a lot....
Does anybody have some ideas?

Oh and software:
Proxmox 8.0.4
Default ixgbe driver (I think? I didn't install anything alse).
Also i can't find anything about what version of driver this is.
 
Anyone any idea to test or check? I'm open for anything.
Also if there's something obvious please point it out...
 
Merwin said:
I'm trying to use the parameter allow_unsupported_sfp=1. One of the SFP modules i'm trying to use is probably not officially supported. I've tried it in/with:
- /etc/modprobe.d/ixgbe.conf
- /etc/default/grub
- modprobe
All with no result.
Click to expand...
Can you please post in detail what you tried/modified in each file?

Normally, if you want to pass module parameters an the commandline, they need to be namespaced by the module named, e.g. ixgbe.allow_unsupported_sfp=1, and you need to run update-grub afterwards.
For /etc/modprobe.d, there is options.

You can also look at the output of /sys/module/ixgbe/parameters/allow_unsupported_sfp to verify whether the parameter was set or not.

Further, what kernel are you running exactly (uname -a)? That's always helpful to know.
 
Thnx a lot for replying!

Kernel (uname -a):
Code: 
Linux HomeController 6.2.16-6-pve #1 SMP PREEMPT_DYNAMIC PMX 6.2.16-7 (2023-08-01T11:23Z) x86_64 GNU/Linux

I've added your suggestion to /etc/default/grub, I must say that i've tried that in the same way. Anyway It looks like this:
Code: 
GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet pci=assign-busses intel_iommu=on iommu=pt pcie_acs_override=downstream,multifunction ixgbe.allow_unsupported_sfp=1"
GRUB_CMDLINE_LINUX=""

Than I ran update-grub and rebooted the system.

Result (dmesg | grep ixgbe):

Code: 
root@HomeController:~# dmesg | grep ixgbe
[    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-6.2.16-6-pve root=/dev/mapper/pve-root ro quiet pci=assign-busses intel_iommu=on iommu=pt pcie_acs_override=downstream,multifunction ixgbe.allow_unsupported_sfp=1
[    0.037240] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.2.16-6-pve root=/dev/mapper/pve-root ro quiet pci=assign-busses intel_iommu=on iommu=pt pcie_acs_override=downstream,multifunction ixgbe.allow_unsupported_sfp=1
[    1.178972] ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver
[    1.178974] ixgbe: Copyright (c) 1999-2016 Intel Corporation.
[    1.181803] ixgbe 0000:01:00.0: enabling device (0000 -> 0002)
[    1.206911] ixgbe 0000:01:00.0: failed to load because an unsupported SFP+ or QSFP module type was detected.
[    1.206921] ixgbe 0000:01:00.0: Reload the driver after installing a supported module.
Still, the SFP module is not recognized/accepted.

Trying your suggestion to read /sys/module/ixgbe/parameters/allow_unsupported_sfp doesn't work.
Looks like this doesn't exist:
Code: 
root@HomeController:~# ls /sys/module/ixgbe
coresize  drivers  holders  initsize  initstate  notes  refcnt  sections  srcversion  taint  uevent
I don't know if I did that correct, or to look somewhere else?

Don't no if this is helpfull:
Code: 
root@HomeController:~# modinfo ixgbe
filename:       /lib/modules/6.2.16-6-pve/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko
license:        GPL v2
description:    Intel(R) 10 Gigabit PCI Express Network Driver
author:         Intel Corporation, <linux.nics@intel.com>
srcversion:     F845394A5EF37F466D5DF16
alias:          pci:v00008086d000015E5sv*sd*bc*sc*i*
alias:          pci:v00008086d000015E4sv*sd*bc*sc*i*
alias:          pci:v00008086d000015CEsv*sd*bc*sc*i*
alias:          pci:v00008086d000015C8sv*sd*bc*sc*i*
alias:          pci:v00008086d000015C7sv*sd*bc*sc*i*
alias:          pci:v00008086d000015C6sv*sd*bc*sc*i*
alias:          pci:v00008086d000015C4sv*sd*bc*sc*i*
alias:          pci:v00008086d000015C3sv*sd*bc*sc*i*
alias:          pci:v00008086d000015C2sv*sd*bc*sc*i*
alias:          pci:v00008086d000015AEsv*sd*bc*sc*i*
alias:          pci:v00008086d000015ACsv*sd*bc*sc*i*
alias:          pci:v00008086d000015ADsv*sd*bc*sc*i*
alias:          pci:v00008086d000015ABsv*sd*bc*sc*i*
alias:          pci:v00008086d000015B0sv*sd*bc*sc*i*
alias:          pci:v00008086d000015AAsv*sd*bc*sc*i*
alias:          pci:v00008086d000015D1sv*sd*bc*sc*i*
alias:          pci:v00008086d00001563sv*sd*bc*sc*i*
alias:          pci:v00008086d00001560sv*sd*bc*sc*i*
alias:          pci:v00008086d0000154Asv*sd*bc*sc*i*
alias:          pci:v00008086d00001557sv*sd*bc*sc*i*
alias:          pci:v00008086d00001558sv*sd*bc*sc*i*
alias:          pci:v00008086d0000154Fsv*sd*bc*sc*i*
alias:          pci:v00008086d0000154Dsv*sd*bc*sc*i*
alias:          pci:v00008086d00001528sv*sd*bc*sc*i*
alias:          pci:v00008086d000010F8sv*sd*bc*sc*i*
alias:          pci:v00008086d0000151Csv*sd*bc*sc*i*
alias:          pci:v00008086d00001529sv*sd*bc*sc*i*
alias:          pci:v00008086d0000152Asv*sd*bc*sc*i*
alias:          pci:v00008086d000010F9sv*sd*bc*sc*i*
alias:          pci:v00008086d00001514sv*sd*bc*sc*i*
alias:          pci:v00008086d00001507sv*sd*bc*sc*i*
alias:          pci:v00008086d000010FBsv*sd*bc*sc*i*
alias:          pci:v00008086d00001517sv*sd*bc*sc*i*
alias:          pci:v00008086d000010FCsv*sd*bc*sc*i*
alias:          pci:v00008086d000010F7sv*sd*bc*sc*i*
alias:          pci:v00008086d00001508sv*sd*bc*sc*i*
alias:          pci:v00008086d000010DBsv*sd*bc*sc*i*
alias:          pci:v00008086d000010F4sv*sd*bc*sc*i*
alias:          pci:v00008086d000010E1sv*sd*bc*sc*i*
alias:          pci:v00008086d000010F1sv*sd*bc*sc*i*
alias:          pci:v00008086d000010ECsv*sd*bc*sc*i*
alias:          pci:v00008086d000010DDsv*sd*bc*sc*i*
alias:          pci:v00008086d0000150Bsv*sd*bc*sc*i*
alias:          pci:v00008086d000010C8sv*sd*bc*sc*i*
alias:          pci:v00008086d000010C7sv*sd*bc*sc*i*
alias:          pci:v00008086d000010C6sv*sd*bc*sc*i*
alias:          pci:v00008086d000010B6sv*sd*bc*sc*i*
depends:        dca,xfrm_algo,mdio
retpoline:      Y
intree:         Y
name:           ixgbe
vermagic:       6.2.16-6-pve SMP preempt mod_unload modversions
parm:           max_vfs:Maximum number of virtual functions to allocate per physical function - default is zero and maximum value is 63. (Deprecated) (uint)
parm:           allow_unsupported_sfp:Allow unsupported and untested SFP+ modules on 82599-based adapters (bool)
parm:           debug:Debug level (0=none,...,16=all) (int)

Things i've also tried:
creating /etc/modprobe.d/ixgbe.conf and adding the follwing line:
options ixgbe allow_unsupported_sfp=1

Also manually reloading the module using modprobe with options didn't seem to resolve the issue.

But for now i'm really intrested in where /sys/module/ixgbe/parameters/allow_unsupported_sfp is or how to read it.
 
Last edited:
Merwin said:
But for now i'm really intrested in where /sys/module/ixgbe/parameters/allow_unsupported_sfp is or how to read it.
Click to expand...
My bad .. just looked at the code, the ixgbe driver unfortunately does not expose its module parameter in the sysfs.

Anyway, searching a bit on the web, you are not the only one with the problem, apparently.

Can you try setting the debug parameter and see if that turns up something useful in the logs? I.e. adding ixgbe.debug=16 to the kernel commandline.
This probably will spew a out a lot of information, but maybe there's something else going wrong here.
 
Oh no problem! Thnx for looking it up!

Edited /etc/default/grub:
Code: 
GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet pci=assign-busses intel_iommu=on iommu=pt pcie_acs_override=downstream,multifunction ixgbe.allow_unsupported_sfp=1 ixgbe.debug=16"
GRUB_CMDLINE_LINUX=""

Ran update-grub and rebooted.
Result:

Code: 
root@HomeController:~# dmesg | grep ixgbe
[    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-6.2.16-6-pve root=/dev/mapper/pve-root ro quiet pci=assign-busses intel_iommu=on iommu=pt pcie_acs_override=downstream,multifunction ixgbe.allow_unsupported_sfp=1 ixgbe.debug=16
[    0.038177] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.2.16-6-pve root=/dev/mapper/pve-root ro quiet pci=assign-busses intel_iommu=on iommu=pt pcie_acs_override=downstream,multifunction ixgbe.allow_unsupported_sfp=1 ixgbe.debug=16
[    1.283510] ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver
[    1.283513] ixgbe: Copyright (c) 1999-2016 Intel Corporation.
[    1.283563] ixgbe 0000:01:00.0: enabling device (0000 -> 0002)
[    1.311033] ixgbe 0000:01:00.0: failed to load because an unsupported SFP+ or QSFP module type was detected.
[    1.311040] ixgbe 0000:01:00.0: Reload the driver after installing a supported module.
[    1.311197] ixgbe 0000:01:00.1: enabling device (0000 -> 0002)
[    1.481881] ixgbe 0000:01:00.1: Multiqueue Enabled: Rx Queue count = 6, Tx Queue count = 6 XDP Queue count = 0
[    1.482173] ixgbe 0000:01:00.1: 32.000 Gb/s available PCIe bandwidth (5.0 GT/s PCIe x8 link)
[    1.482255] ixgbe 0000:01:00.1: MAC: 2, PHY: 19, SFP+: 12, PBA No: 0210FF-0FF
[    1.482257] ixgbe 0000:01:00.1: 0c:c4:7a:8f:49:13
[    1.485314] ixgbe 0000:01:00.1: Intel(R) 10 Gigabit Network Connection
[    1.779792] ixgbe 0000:01:00.1 enp1s0f1: renamed from eth0
[    4.377294] ixgbe 0000:01:00.1 enp1s0f1: SR-IOV enabled with 3 VFs
[    4.438654] ixgbe 0000:01:00.1: Multiqueue Enabled: Rx Queue count = 4, Tx Queue count = 4 XDP Queue count = 0
[    4.548928] ixgbevf: Intel(R) 10 Gigabit PCI Express Virtual Function Network Driver
[    4.548930] ixgbevf: Copyright (c) 2009 - 2018 Intel Corporation.
[    4.549034] ixgbevf 0000:02:10.1: enabling device (0000 -> 0002)
[    4.550281] ixgbevf 0000:02:10.1: PF still in reset state.  Is the PF interface up?
[    4.550283] ixgbevf 0000:02:10.1: Assigning random MAC address
[    4.550590] ixgbevf 0000:02:10.1: 82:f3:16:94:c9:ec
[    4.550592] ixgbevf 0000:02:10.1: MAC: 1
[    4.550593] ixgbevf 0000:02:10.1: Intel(R) 82599 Virtual Function
[    4.550615] ixgbevf 0000:02:10.3: enabling device (0000 -> 0002)
[    4.551835] ixgbevf 0000:02:10.3: PF still in reset state.  Is the PF interface up?
[    4.551836] ixgbevf 0000:02:10.3: Assigning random MAC address
[    4.552030] ixgbevf 0000:02:10.3: ce:96:dd:10:83:d2
[    4.552032] ixgbevf 0000:02:10.3: MAC: 1
[    4.552033] ixgbevf 0000:02:10.3: Intel(R) 82599 Virtual Function
[    4.552045] ixgbevf 0000:02:10.5: enabling device (0000 -> 0002)
[    4.553290] ixgbevf 0000:02:10.5: PF still in reset state.  Is the PF interface up?
[    4.553291] ixgbevf 0000:02:10.5: Assigning random MAC address
[    4.553482] ixgbevf 0000:02:10.5: 82:8b:ed:e7:fe:79
[    4.553483] ixgbevf 0000:02:10.5: MAC: 1
[    4.553484] ixgbevf 0000:02:10.5: Intel(R) 82599 Virtual Function
[    7.525600] ixgbevf 0000:02:10.3 enp1s0f1v1: renamed from eth1
[    7.549817] ixgbevf 0000:02:10.5 enp1s0f1v2: renamed from eth2
[    7.581888] ixgbe 0000:01:00.1: setting MAC aa:bb:cc:f2:00:00 on VF 0
[    7.581892] ixgbe 0000:01:00.1: Reload the VF driver to make this change effective.
[    7.581896] ixgbe 0000:01:00.1: The VF MAC address has been set, but the PF device is not up.
[    7.581897] ixgbe 0000:01:00.1: Bring the PF device up before attempting to use the VF device.
[    7.581935] ixgbevf 0000:02:10.1 enp1s0f1v0: renamed from eth0
[    7.652506] ixgbe 0000:01:00.1: setting MAC aa:bb:cc:f2:00:01 on VF 1
[    7.652510] ixgbe 0000:01:00.1: Reload the VF driver to make this change effective.
[    7.652514] ixgbe 0000:01:00.1: The VF MAC address has been set, but the PF device is not up.
[    7.652515] ixgbe 0000:01:00.1: Bring the PF device up before attempting to use the VF device.
[    7.655719] ixgbe 0000:01:00.1: setting MAC aa:bb:cc:f2:00:02 on VF 2
[    7.655723] ixgbe 0000:01:00.1: Reload the VF driver to make this change effective.
[    7.655727] ixgbe 0000:01:00.1: The VF MAC address has been set, but the PF device is not up.
[    7.655728] ixgbe 0000:01:00.1: Bring the PF device up before attempting to use the VF device.
[    7.659133] ixgbe 0000:01:00.1 enp1s0f1: VF 0 is trusted
[    7.662484] ixgbe 0000:01:00.1 enp1s0f1: VF 1 is trusted
[    7.666316] ixgbe 0000:01:00.1 enp1s0f1: VF 2 is trusted
[   10.803381] ixgbe 0000:01:00.1: registered PHC device on enp1s0f1
[   10.973812] ixgbe 0000:01:00.1 enp1s0f1: detected SFP+: 12
[   11.113788] ixgbe 0000:01:00.1 enp1s0f1: NIC Link is Up 1 Gbps, Flow Control: RX/TX
 
Is there something in this line what could break passing paramars to ixgbe?
Code: 
GRUB_CMDLINE_LINUX_DEFAULT="quiet pci=assign-busses intel_iommu=on iommu=pt pcie_acs_override=downstream,multifunction ixgbe.allow_unsupported_sfp=1 ixgbe.debug=16"

Are there other ways to check if parameters are passed trough to and handled by the module/driver?
 
Merwin said:
Is there something in this line what could break passing paramars to ixgbe?
Click to expand...
Looking at it this way, it is possible that the ixgbevf maybe interferes here.

Can you try removing (all) other parameters (best would be one-by-one to narrow it down) and see if that resolves it?
 
Would be strange I think because the second module/port is working.

Anyway, I disabled all modules and a service that I've added to make vf work, also changed grub to disable all the 'unnessecary' things.
After update-grub and a reboot:
Code: 
root@HomeController:~# grep ixgbevf /proc/modules
gives no result so ixgbevf is not loaded.

The following is the result:
Code: 
root@HomeController:~# dmesg | grep ixgbe
[    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-6.2.16-6-pve root=/dev/mapper/pve-root ro quiet ixgbe.allow_unsupported_sfp=1 ixgbe.debug=16
[    0.038272] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.2.16-6-pve root=/dev/mapper/pve-root ro quiet ixgbe.allow_unsupported_sfp=1 ixgbe.debug=16
[    1.243547] ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver
[    1.243550] ixgbe: Copyright (c) 1999-2016 Intel Corporation.
[    1.243593] ixgbe 0000:01:00.0: enabling device (0000 -> 0002)
[    1.268310] ixgbe 0000:01:00.0: failed to load because an unsupported SFP+ or QSFP module type was detected.
[    1.268317] ixgbe 0000:01:00.0: Reload the driver after installing a supported module.
[    1.268466] ixgbe 0000:01:00.1: enabling device (0000 -> 0002)
[    1.441774] ixgbe 0000:01:00.1: Multiqueue Enabled: Rx Queue count = 6, Tx Queue count = 6 XDP Queue count = 0
[    1.442065] ixgbe 0000:01:00.1: 32.000 Gb/s available PCIe bandwidth (5.0 GT/s PCIe x8 link)
[    1.442148] ixgbe 0000:01:00.1: MAC: 2, PHY: 19, SFP+: 12, PBA No: 0210FF-0FF
[    1.442150] ixgbe 0000:01:00.1: 0c:c4:7a:8f:49:13
[    1.445196] ixgbe 0000:01:00.1: Intel(R) 10 Gigabit Network Connection
[    1.752371] ixgbe 0000:01:00.1 enp1s0f1: renamed from eth0
[    5.003599] ixgbe 0000:01:00.1: registered PHC device on enp1s0f1
[    5.173756] ixgbe 0000:01:00.1 enp1s0f1: detected SFP+: 12
[    5.289488] ixgbe 0000:01:00.1 enp1s0f1: NIC Link is Up 1 Gbps, Flow Control: RX/TX
[    8.895394] ixgbe 0000:01:00.1 enp1s0f1: NIC Link is Down
[    9.673582] ixgbe 0000:01:00.1 enp1s0f1: NIC Link is Up 1 Gbps, Flow Control: RX/TX

What else can we check/change/disable?
 
Thnx for your input. Yes, I've tried it. But I followed this description again but sadly no better results.
 
Merwin said:
What else can we check/change/disable?
Click to expand...
Also running out of ideas slowly .. it's really, really weird. The parameter is there, the module just doesn't want to recognize it.

You did try inserting the module directly, with the parameter set, right?
Something like:
Code: 
# rmmod ixgbe
# insmod /lib/modules/6.2.16-6-pve/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko allow_unsupported_sfp=1

And one last thing to I'd like to check .. restore the kernel-commandline to this:
Code: 
GRUB_CMDLINE_LINUX_DEFAULT="quiet pci=assign-busses intel_iommu=on iommu=pt pcie_acs_override=downstream,multifunction ixgbe.allow_unsupported_sfp=1"
Could you then maybe post the full journalctl -b of a reboot with that, attached as a file here, preferably?

Just maybe there is something else earlier in the boot that causes this to fail.
 
This morning I made the choice to not further investigate and to get a different (compatibles) sfp module. The old module is shipped back. For now I leave this investigation as to why it doesn't work unanswered.

Thnx a lot for all the help and idea's!
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back