search for: i350

Hi, I'm on a Dell VEP 1405 running Debian 9.11 and I'm running a few tests with various interfaces given in PCI passthrough to a qemu/KVM Virtual Machine also running Debian 9.11. I noticed that only one of the four I350 network controllers can be used in PCI passthrough. The available interfaces are: *# dpdk-devbind.py --status Network devices using kernel driver ==============================* *===== 0000:02:00.0 'I350 Gigabit Network Connection 1521' if=eth2 drv=igb unused=igb_uio,vfio-pci,uio_* *pci_...

...well. > > I'm not going to post any further updates unless something breaks. > Thanks to everyone that provided tips and suggestions along the way. > Do you mind sharing what hardware have you been running the 4.9 kernel on other than "Supermicro X9DRT, Dual Xeon E5-2650, 2x I350, 2x 82571EB" and "Supermicro X9DRD-iF/LF, Dual Xeon E5-2630, 2x I350, 2x 82575EB" if any? Are you using any SATA/SAS controllers? Thanks, Sarah

...ng to post any further updates unless something breaks. >>> Thanks to everyone that provided tips and suggestions along the way. >>> >> >> Do you mind sharing what hardware have you been running the 4.9 kernel on other than "Supermicro X9DRT, Dual Xeon E5-2650, 2x I350, 2x 82571EB" and >> "Supermicro X9DRD-iF/LF, Dual Xeon E5-2630, 2x I350, 2x 82575EB" if any? Are you using any SATA/SAS controllers? > > We have no expansion cards installed except for the dual-port gigabit > NICs. We're using the onboard SATA controller for only...

Hi there, I?m working on deploying our new cluster. Masters have 5?1gbps (i210 and i350, thus using igb.ko), configured with mtu 9000, 802.3ad. Works fine *but* I can?t get DCB working (pause frame, aka flow control, which is supported by and enabled on our switches). [root at master2 ~]# dcbtool gc eno1 dcb Command: Get Config Feature: DCB State Port: e...

...erity=Corrected, type=Physical Layer, id=0401(Receiver ID) igb 0000:04:00.1: device [8086:10a7] error status/mask=00002001/00002000 igb 0000:04:00.1: [ 0] Receiver Error (First) This spams to the console continuously until hard booting. - Supermicro X9DRD-iF/LF, Dual Xeon E5-2630, 2x I350, 2x 82575EB igb 0000:82:00.0: Detected Tx Unit Hang Tx Queue <1> TDH <43> TDT <50> next_to_use <50> next_to_clean <43> buffer_info[next_to_clean] time_stamp <12e6bc0b6> next_to_watch...

Does anyone here know which CentOS release added support for 8086:1521, some I350 class device? We cannot get it to work under 5.4/igb driver version 1.3.16-k2. There must have been some major updates since, 5.8 driver is 3.0.6-k2-2 and current is 3.3.6.

...st from the repo and report back. > > 2) What's the system? The sole system I have confirmation of a > remaining EFI64 issue is a VMware VM with the e1000e NIC, in fact with > similar symptoms. > The system is a Dell PowerEdge R730xd with 4 NICs: Intel(R) Ethernet 10G 4P X520/I350 rNDC Intel(R) Gigabit 4P X520/I350 rNDC Current connection on the 10G port. I have noticed something else a little weird via the UEFI setting for the NIC's. I seem to have to enable two NICs for PXE booting to even successfully PXE boot. When I do this the first NIC fails to boot and the...

Hi, I managed to get SR-IOV with an Intel I350 NIC to work.For this I followed the documentation on this page: https://wiki.libvirt.org/page/Networking#Assignment_from_a_pool_of_SRIOV_VFs_in_a_libvirt_.3Cnetwork.3E_definition But as I have more VMs then VF on the NIC I also have a bridge wich serves the other guests. As I run Debian Buster a...

...> > > 2) What's the system? The sole system I have confirmation of a > > remaining EFI64 issue is a VMware VM with the e1000e NIC, in fact with > > similar symptoms. > > > > The system is a Dell PowerEdge R730xd with 4 NICs: > Intel(R) Ethernet 10G 4P X520/I350 rNDC > Intel(R) Gigabit 4P X520/I350 rNDC > > Current connection on the 10G port. > > I have noticed something else a little weird via the UEFI setting for > the NIC's. I seem to have to enable two NICs for PXE booting to even > successfully PXE boot. When I do this t...

Hello, CentOS 7(1) I like to setup a new Server with SR-IOV for Networking.. I have a I350 Network Card on Board. But on my System this is, I mean, not correct working ? When I like to have Virtual Network Cards I have to unload / reload the "igb" driver? afterward I have my virtual Network Cards. Have any a way, to have the virtual Network Cards on boot time? Thanks for...

...I'm not going to post any further updates unless something breaks. >> Thanks to everyone that provided tips and suggestions along the way. >> > > Do you mind sharing what hardware have you been running the 4.9 kernel on other than "Supermicro X9DRT, Dual Xeon E5-2650, 2x I350, 2x 82571EB" and > "Supermicro X9DRD-iF/LF, Dual Xeon E5-2630, 2x I350, 2x 82575EB" if any? Are you using any SATA/SAS controllers? We have no expansion cards installed except for the dual-port gigabit NICs. We're using the onboard SATA controller for only the local Dom0 OS,...

On Thu, Feb 26, 2015 at 9:18 AM, Laurent Wandrebeck < l.wandrebeck at quelquesmots.fr> wrote: > Hi there, > > I?m working on deploying our new cluster. > Masters have 5?1gbps (i210 and i350, thus using igb.ko), configured with > mtu 9000, 802.3ad. Works fine *but* I can?t get DCB working (pause frame, > aka flow control, which is supported by and enabled on our switches). > > [root at master2 ~]# dcbtool gc eno1 dcb > Command: Get Config > Feature: DCB...

Team I have a Dell PowerEdge R720xd, with the Broadcom NetXtreme bcm5720. I found the following thread: http://forums.freebsd.org/showthread.php?t=31769 I find I am unable to use the NIC's (there are 4 on the server). When we put a cable into it we get a "watchdog timeout -- resetting" error, and the machine will pause for 5 or so seconds. IP may or may not come up randomly.

...erity=Corrected, type=Physical Layer, id=0401(Receiver ID) igb 0000:04:00.1: device [8086:10a7] error status/mask=00002001/00002000 igb 0000:04:00.1: [ 0] Receiver Error (First) This spams to the console continuously until hard booting. - Supermicro X9DRD-iF/LF, Dual Xeon E5-2630, 2x I350, 2x 82575EB igb 0000:82:00.0: Detected Tx Unit Hang Tx Queue <1> TDH <43> TDT <50> next_to_use <50> next_to_clean <43> buffer_info[next_to_clean] time_stamp <12e6bc0b6> next_to_watch...

...Layer, id=0401(Receiver ID) > igb 0000:04:00.1: device [8086:10a7] error status/mask=00002001/00002000 > igb 0000:04:00.1: [ 0] Receiver Error (First) > > This spams to the console continuously until hard booting. > > - Supermicro X9DRD-iF/LF, Dual Xeon E5-2630, 2x I350, 2x 82575EB > > igb 0000:82:00.0: Detected Tx Unit Hang > Tx Queue <1> > TDH <43> > TDT <50> > next_to_use <50> > next_to_clean <43> > buffer_info[next_to_clean] > time_stam...

On 02/21/2017 05:32 PM, Kevin Stange wrote: > On 02/21/2017 11:50 AM, Johnny Hughes wrote: >> On 02/21/2017 11:47 AM, Johnny Hughes wrote: >>> >>> >>> Kevin, >>> >>> Please try the 4.9.11-22 kernel that I just released for CentOS-6 (along >>> with the newer linux-firmare packages and xfsprogs). >>> >>> If you enable

...following this thread all that closely, so I'm unsure what system and firmware you have -- but we recently encountered a BIOS bug that has disrupted some local kickstarts. The short version is that our Intel SMBIOS reports duplicate names for onboard ethernet devices, which in our case are I350 1G cards: [root ~]# biosdevname -d | grep 'BIOS device' BIOS device: em1 BIOS device: em1 BIOS device: p785p1 Ideally, the second device would be em2. Since they report the same, systemd gets inconsistently confused and the devices' "Kernel name" entries bounce between eno...

I'm setting up UEFI booting and got to the point of having the system talk to the dhcpd/tftpd server, grab the first image files (syslinux.efi) and then continuously request the secondary image file (ldlinux.e64). I'm wondering if I'm missing something or if someone can point me in the right direction of trouble shooting this. The tftp root has all the files to boot a BIOS type

...9;unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success? > > > Before the network configuration used to be rock-solid. I?m running on a Xeon D-1548 SoC with an on-chip X552/557 (ixgbe.ko) and an off-chip i350 (igb.ko) quad-NIC. In this case, I?m using the first port of the i350. > > The VM?s XML is unchanged, as it was previously (while things were working reliably): > > <interface type='network'> > <mac address='52:54:00:29:01:5b'/> > <so...

...er ID) >> igb 0000:04:00.1: device [8086:10a7] error status/mask=00002001/00002000 >> igb 0000:04:00.1: [ 0] Receiver Error (First) >> >> This spams to the console continuously until hard booting. >> >> - Supermicro X9DRD-iF/LF, Dual Xeon E5-2630, 2x I350, 2x 82575EB >> >> igb 0000:82:00.0: Detected Tx Unit Hang >> Tx Queue <1> >> TDH <43> >> TDT <50> >> next_to_use <50> >> next_to_clean <43> >> buffer_info...