I have brand new PC with this components: CPU Intel® Pentium G5400, LGA1151 motherboard ASUS PRIME B360M-C 16 GB RAM HDD 2x ADATA SSD 256GB XPG GAMMIX S11, PCIe Gen3x4 M.2 2280 (RAID1) NIC Intel X550-T1 Ethernet Converged Network Adapter
I installed CentOS 7 and two NICs were detected: eno1 (on motherboard) enp1s0 (Intel X550-T1)
When I restart the machine sometimes enp1s0 is missing. It is not detected during boot. It looks like NIC card is not installed / not present. After next reboot everything is fine and I do not see any problems with NIC card.
How can I avoid this problem with missing NIC? Can you help me, please?
Miroslav Geisselreiter
On Tue, Sep 17, 2019 at 7:06 AM Miroslav Geisselreiter mg@intar.cz wrote:
I have brand new PC with this components: CPU Intel® Pentium G5400, LGA1151 motherboard ASUS PRIME B360M-C 16 GB RAM HDD 2x ADATA SSD 256GB XPG GAMMIX S11, PCIe Gen3x4 M.2 2280 (RAID1) NIC Intel X550-T1 Ethernet Converged Network Adapter
I installed CentOS 7 and two NICs were detected: eno1 (on motherboard) enp1s0 (Intel X550-T1)
When I restart the machine sometimes enp1s0 is missing. It is not detected during boot. It looks like NIC card is not installed / not present. After next reboot everything is fine and I do not see any problems with NIC card.
How can I avoid this problem with missing NIC? Can you help me, please?
Nothing exciting on dmesg? Did you check the pci chain to see if it is being reported as there?
Miroslav Geisselreiter
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Dne 17.9.2019 v 14:02 Mauricio Tavares napsal(a):
On Tue, Sep 17, 2019 at 7:06 AM Miroslav Geisselreiter mg@intar.cz wrote:
I have brand new PC with this components: CPU Intel® Pentium G5400, LGA1151 motherboard ASUS PRIME B360M-C 16 GB RAM HDD 2x ADATA SSD 256GB XPG GAMMIX S11, PCIe Gen3x4 M.2 2280 (RAID1) NIC Intel X550-T1 Ethernet Converged Network Adapter
I installed CentOS 7 and two NICs were detected: eno1 (on motherboard) enp1s0 (Intel X550-T1)
When I restart the machine sometimes enp1s0 is missing. It is not detected during boot. It looks like NIC card is not installed / not present. After next reboot everything is fine and I do not see any problems with NIC card.
How can I avoid this problem with missing NIC? Can you help me, please?
Nothing exciting on dmesg? Did you check the pci chain to see ifit is being reported as there?
From /var/log/dmesg, when NIC is detected and working: grep ixgbe dmesg [ 0.999078] ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver - version 5.1.0-k-rh7.6 [ 0.999081] ixgbe: Copyright (c) 1999-2016 Intel Corporation. [ 1.720556] ixgbe 0000:01:00.0: irq 138 for MSI/MSI-X [ 1.720563] ixgbe 0000:01:00.0: irq 139 for MSI/MSI-X [ 1.720568] ixgbe 0000:01:00.0: irq 140 for MSI/MSI-X [ 1.720573] ixgbe 0000:01:00.0: irq 141 for MSI/MSI-X [ 1.720578] ixgbe 0000:01:00.0: irq 142 for MSI/MSI-X [ 1.720602] ixgbe 0000:01:00.0: Multiqueue Enabled: Rx Queue count = 4, Tx Queue count = 4 XDP Queue count = 0 [ 1.821743] ixgbe 0000:01:00.0: PCI Express bandwidth of 32GT/s available [ 1.821754] ixgbe 0000:01:00.0: (Speed:8.0GT/s, Width: x4, Encoding Loss:N/a) [ 1.933432] ixgbe 0000:01:00.0: MAC: 4, PHY: 0, PBA No: H92506-004 [ 1.933434] ixgbe 0000:01:00.0: a0:36:9f:f8:46:28 [ 2.093020] ixgbe 0000:01:00.0: Intel(R) 10 Gigabit Network Connection
When NIC is not detected, there is no ixgbe message in dmesg.
I can list irq from dmesg (with NIC detected) and dmesg.old (NIS is not tedected) grep irq dmesg [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [ 0.000000] NR_IRQS:327936 nr_irqs:1024 0 [ 0.531915] pcieport 0000:00:01.0: irq 120 for MSI/MSI-X [ 0.532038] pcieport 0000:00:1b.0: irq 121 for MSI/MSI-X [ 0.532309] pcieport 0000:00:1c.5: irq 122 for MSI/MSI-X [ 0.532534] pcieport 0000:00:1d.0: irq 123 for MSI/MSI-X [ 0.604204] 00:05: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A [ 0.625761] 00:06: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A [ 0.628502] xhci_hcd 0000:00:14.0: irq 124 for MSI/MSI-X [ 0.630583] i8042: PNP: PS/2 Controller [PNP0303:PS2K,PNP0f03:PS2M] at 0x60,0x64 irq 1,12 [ 0.634280] serio: i8042 KBD port at 0x60,0x64 irq 1 [ 0.634284] serio: i8042 AUX port at 0x60,0x64 irq 12 [ 0.635917] rtc_cmos rtc_cmos: alarms up to one month, y3k, 114 bytes nvram, hpet irqs [ 1.027014] e1000e 0000:00:1f.6: irq 125 for MSI/MSI-X [ 1.028089] nvme 0000:02:00.0: irq 126 for MSI/MSI-X [ 1.029367] nvme 0000:06:00.0: irq 127 for MSI/MSI-X [ 1.130027] nvme 0000:02:00.0: irq 126 for MSI/MSI-X [ 1.130033] nvme 0000:02:00.0: irq 128 for MSI/MSI-X [ 1.130038] nvme 0000:02:00.0: irq 129 for MSI/MSI-X [ 1.130041] nvme 0000:02:00.0: irq 130 for MSI/MSI-X [ 1.130045] nvme 0000:02:00.0: irq 131 for MSI/MSI-X [ 1.233841] nvme 0000:06:00.0: irq 127 for MSI/MSI-X [ 1.233846] nvme 0000:06:00.0: irq 132 for MSI/MSI-X [ 1.233851] nvme 0000:06:00.0: irq 133 for MSI/MSI-X [ 1.233855] nvme 0000:06:00.0: irq 134 for MSI/MSI-X [ 1.233858] nvme 0000:06:00.0: irq 135 for MSI/MSI-X [ 1.378373] ahci 0000:00:17.0: irq 136 for MSI/MSI-X [ 1.433203] ata1: SATA max UDMA/133 abar m2048@0xa2439000 port 0xa2439100 irq 136 [ 1.433214] ata2: SATA max UDMA/133 abar m2048@0xa2439000 port 0xa2439180 irq 136 [ 1.433226] ata3: SATA max UDMA/133 abar m2048@0xa2439000 port 0xa2439200 irq 136 [ 1.433238] ata4: SATA max UDMA/133 abar m2048@0xa2439000 port 0xa2439280 irq 136 [ 1.433250] ata5: SATA max UDMA/133 abar m2048@0xa2439000 port 0xa2439300 irq 136 [ 1.433262] ata6: SATA max UDMA/133 abar m2048@0xa2439000 port 0xa2439380 irq 136 [ 1.438562] i915 0000:00:02.0: irq 137 for MSI/MSI-X [ 1.720556] ixgbe 0000:01:00.0: irq 138 for MSI/MSI-X [ 1.720563] ixgbe 0000:01:00.0: irq 139 for MSI/MSI-X [ 1.720568] ixgbe 0000:01:00.0: irq 140 for MSI/MSI-X [ 1.720573] ixgbe 0000:01:00.0: irq 141 for MSI/MSI-X [ 1.720578] ixgbe 0000:01:00.0: irq 142 for MSI/MSI-X [ 2.762813] parport0: PC-style at 0x378, irq 5 [PCSPP] [ 2.931480] snd_hda_intel 0000:00:1f.3: irq 143 for MSI/MSI-X
grep irq dmesg.old [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [ 0.000000] NR_IRQS:327936 nr_irqs:1024 0 [ 0.531838] pcieport 0000:00:01.0: irq 120 for MSI/MSI-X [ 0.531961] pcieport 0000:00:1b.0: irq 121 for MSI/MSI-X [ 0.532189] pcieport 0000:00:1c.5: irq 122 for MSI/MSI-X [ 0.532360] pcieport 0000:00:1d.0: irq 123 for MSI/MSI-X [ 0.604543] 00:05: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A [ 0.626093] 00:06: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A [ 0.628860] xhci_hcd 0000:00:14.0: irq 124 for MSI/MSI-X [ 0.630950] i8042: PNP: PS/2 Controller [PNP0303:PS2K,PNP0f03:PS2M] at 0x60,0x64 irq 1,12 [ 0.634787] serio: i8042 KBD port at 0x60,0x64 irq 1 [ 0.634792] serio: i8042 AUX port at 0x60,0x64 irq 12 [ 0.636314] rtc_cmos rtc_cmos: alarms up to one month, y3k, 114 bytes nvram, hpet irqs [ 0.990007] nvme 0000:02:00.0: irq 125 for MSI/MSI-X [ 0.991375] ahci 0000:00:17.0: irq 126 for MSI/MSI-X [ 0.992906] nvme 0000:06:00.0: irq 127 for MSI/MSI-X [ 1.092088] nvme 0000:02:00.0: irq 125 for MSI/MSI-X [ 1.092095] nvme 0000:02:00.0: irq 128 for MSI/MSI-X [ 1.092099] nvme 0000:02:00.0: irq 129 for MSI/MSI-X [ 1.092103] nvme 0000:02:00.0: irq 130 for MSI/MSI-X [ 1.092107] nvme 0000:02:00.0: irq 131 for MSI/MSI-X [ 1.095722] ata1: SATA max UDMA/133 abar m2048@0xa1339000 port 0xa1339100 irq 126 [ 1.095776] ata2: SATA max UDMA/133 abar m2048@0xa1339000 port 0xa1339180 irq 126 [ 1.095782] ata3: SATA max UDMA/133 abar m2048@0xa1339000 port 0xa1339200 irq 126 [ 1.095787] ata4: SATA max UDMA/133 abar m2048@0xa1339000 port 0xa1339280 irq 126 [ 1.095798] ata5: SATA max UDMA/133 abar m2048@0xa1339000 port 0xa1339300 irq 126 [ 1.095810] ata6: SATA max UDMA/133 abar m2048@0xa1339000 port 0xa1339380 irq 126 [ 1.096503] e1000e 0000:00:1f.6: irq 132 for MSI/MSI-X [ 1.196872] nvme 0000:06:00.0: irq 127 for MSI/MSI-X [ 1.196877] nvme 0000:06:00.0: irq 133 for MSI/MSI-X [ 1.196882] nvme 0000:06:00.0: irq 134 for MSI/MSI-X [ 1.196886] nvme 0000:06:00.0: irq 135 for MSI/MSI-X [ 1.196889] nvme 0000:06:00.0: irq 136 for MSI/MSI-X [ 1.436844] i915 0000:00:02.0: irq 137 for MSI/MSI-X [ 2.351174] parport0: PC-style at 0x378, irq 5 [PCSPP] [ 2.525337] snd_hda_intel 0000:00:1f.3: irq 138 for MSI/MSI-X
I do not know what you mean "check the pci chain". My knowledge of kernel level is weak, sorry. What else can I do?
Miroslav
On Tue, Sep 17, 2019 at 9:11 AM Miroslav Geisselreiter mg@intar.cz wrote:
Dne 17.9.2019 v 14:02 Mauricio Tavares napsal(a):
On Tue, Sep 17, 2019 at 7:06 AM Miroslav Geisselreiter mg@intar.cz wrote:
I have brand new PC with this components: CPU Intel® Pentium G5400, LGA1151 motherboard ASUS PRIME B360M-C 16 GB RAM HDD 2x ADATA SSD 256GB XPG GAMMIX S11, PCIe Gen3x4 M.2 2280 (RAID1) NIC Intel X550-T1 Ethernet Converged Network Adapter
I installed CentOS 7 and two NICs were detected: eno1 (on motherboard) enp1s0 (Intel X550-T1)
When I restart the machine sometimes enp1s0 is missing. It is not detected during boot. It looks like NIC card is not installed / not present. After next reboot everything is fine and I do not see any problems with NIC card.
How can I avoid this problem with missing NIC? Can you help me, please?
Nothing exciting on dmesg? Did you check the pci chain to see ifit is being reported as there?
From /var/log/dmesg, when NIC is detected and working: grep ixgbe dmesg [ 0.999078] ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver - version 5.1.0-k-rh7.6 [ 0.999081] ixgbe: Copyright (c) 1999-2016 Intel Corporation. [ 1.720556] ixgbe 0000:01:00.0: irq 138 for MSI/MSI-X [ 1.720563] ixgbe 0000:01:00.0: irq 139 for MSI/MSI-X [ 1.720568] ixgbe 0000:01:00.0: irq 140 for MSI/MSI-X [ 1.720573] ixgbe 0000:01:00.0: irq 141 for MSI/MSI-X [ 1.720578] ixgbe 0000:01:00.0: irq 142 for MSI/MSI-X [ 1.720602] ixgbe 0000:01:00.0: Multiqueue Enabled: Rx Queue count = 4, Tx Queue count = 4 XDP Queue count = 0 [ 1.821743] ixgbe 0000:01:00.0: PCI Express bandwidth of 32GT/s available [ 1.821754] ixgbe 0000:01:00.0: (Speed:8.0GT/s, Width: x4, Encoding Loss:N/a) [ 1.933432] ixgbe 0000:01:00.0: MAC: 4, PHY: 0, PBA No: H92506-004 [ 1.933434] ixgbe 0000:01:00.0: a0:36:9f:f8:46:28 [ 2.093020] ixgbe 0000:01:00.0: Intel(R) 10 Gigabit Network Connection
When NIC is not detected, there is no ixgbe message in dmesg.
I can list irq from dmesg (with NIC detected) and dmesg.old (NIS is not tedected) grep irq dmesg [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [ 0.000000] NR_IRQS:327936 nr_irqs:1024 0 [ 0.531915] pcieport 0000:00:01.0: irq 120 for MSI/MSI-X [ 0.532038] pcieport 0000:00:1b.0: irq 121 for MSI/MSI-X [ 0.532309] pcieport 0000:00:1c.5: irq 122 for MSI/MSI-X [ 0.532534] pcieport 0000:00:1d.0: irq 123 for MSI/MSI-X [ 0.604204] 00:05: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A [ 0.625761] 00:06: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A [ 0.628502] xhci_hcd 0000:00:14.0: irq 124 for MSI/MSI-X [ 0.630583] i8042: PNP: PS/2 Controller [PNP0303:PS2K,PNP0f03:PS2M] at 0x60,0x64 irq 1,12 [ 0.634280] serio: i8042 KBD port at 0x60,0x64 irq 1 [ 0.634284] serio: i8042 AUX port at 0x60,0x64 irq 12 [ 0.635917] rtc_cmos rtc_cmos: alarms up to one month, y3k, 114 bytes nvram, hpet irqs [ 1.027014] e1000e 0000:00:1f.6: irq 125 for MSI/MSI-X [ 1.028089] nvme 0000:02:00.0: irq 126 for MSI/MSI-X [ 1.029367] nvme 0000:06:00.0: irq 127 for MSI/MSI-X [ 1.130027] nvme 0000:02:00.0: irq 126 for MSI/MSI-X [ 1.130033] nvme 0000:02:00.0: irq 128 for MSI/MSI-X [ 1.130038] nvme 0000:02:00.0: irq 129 for MSI/MSI-X [ 1.130041] nvme 0000:02:00.0: irq 130 for MSI/MSI-X [ 1.130045] nvme 0000:02:00.0: irq 131 for MSI/MSI-X [ 1.233841] nvme 0000:06:00.0: irq 127 for MSI/MSI-X [ 1.233846] nvme 0000:06:00.0: irq 132 for MSI/MSI-X [ 1.233851] nvme 0000:06:00.0: irq 133 for MSI/MSI-X [ 1.233855] nvme 0000:06:00.0: irq 134 for MSI/MSI-X [ 1.233858] nvme 0000:06:00.0: irq 135 for MSI/MSI-X [ 1.378373] ahci 0000:00:17.0: irq 136 for MSI/MSI-X [ 1.433203] ata1: SATA max UDMA/133 abar m2048@0xa2439000 port 0xa2439100 irq 136 [ 1.433214] ata2: SATA max UDMA/133 abar m2048@0xa2439000 port 0xa2439180 irq 136 [ 1.433226] ata3: SATA max UDMA/133 abar m2048@0xa2439000 port 0xa2439200 irq 136 [ 1.433238] ata4: SATA max UDMA/133 abar m2048@0xa2439000 port 0xa2439280 irq 136 [ 1.433250] ata5: SATA max UDMA/133 abar m2048@0xa2439000 port 0xa2439300 irq 136 [ 1.433262] ata6: SATA max UDMA/133 abar m2048@0xa2439000 port 0xa2439380 irq 136 [ 1.438562] i915 0000:00:02.0: irq 137 for MSI/MSI-X [ 1.720556] ixgbe 0000:01:00.0: irq 138 for MSI/MSI-X [ 1.720563] ixgbe 0000:01:00.0: irq 139 for MSI/MSI-X [ 1.720568] ixgbe 0000:01:00.0: irq 140 for MSI/MSI-X [ 1.720573] ixgbe 0000:01:00.0: irq 141 for MSI/MSI-X [ 1.720578] ixgbe 0000:01:00.0: irq 142 for MSI/MSI-X [ 2.762813] parport0: PC-style at 0x378, irq 5 [PCSPP] [ 2.931480] snd_hda_intel 0000:00:1f.3: irq 143 for MSI/MSI-X
grep irq dmesg.old [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [ 0.000000] NR_IRQS:327936 nr_irqs:1024 0 [ 0.531838] pcieport 0000:00:01.0: irq 120 for MSI/MSI-X [ 0.531961] pcieport 0000:00:1b.0: irq 121 for MSI/MSI-X [ 0.532189] pcieport 0000:00:1c.5: irq 122 for MSI/MSI-X [ 0.532360] pcieport 0000:00:1d.0: irq 123 for MSI/MSI-X [ 0.604543] 00:05: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A [ 0.626093] 00:06: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A [ 0.628860] xhci_hcd 0000:00:14.0: irq 124 for MSI/MSI-X [ 0.630950] i8042: PNP: PS/2 Controller [PNP0303:PS2K,PNP0f03:PS2M] at 0x60,0x64 irq 1,12 [ 0.634787] serio: i8042 KBD port at 0x60,0x64 irq 1 [ 0.634792] serio: i8042 AUX port at 0x60,0x64 irq 12 [ 0.636314] rtc_cmos rtc_cmos: alarms up to one month, y3k, 114 bytes nvram, hpet irqs [ 0.990007] nvme 0000:02:00.0: irq 125 for MSI/MSI-X [ 0.991375] ahci 0000:00:17.0: irq 126 for MSI/MSI-X [ 0.992906] nvme 0000:06:00.0: irq 127 for MSI/MSI-X [ 1.092088] nvme 0000:02:00.0: irq 125 for MSI/MSI-X [ 1.092095] nvme 0000:02:00.0: irq 128 for MSI/MSI-X [ 1.092099] nvme 0000:02:00.0: irq 129 for MSI/MSI-X [ 1.092103] nvme 0000:02:00.0: irq 130 for MSI/MSI-X [ 1.092107] nvme 0000:02:00.0: irq 131 for MSI/MSI-X [ 1.095722] ata1: SATA max UDMA/133 abar m2048@0xa1339000 port 0xa1339100 irq 126 [ 1.095776] ata2: SATA max UDMA/133 abar m2048@0xa1339000 port 0xa1339180 irq 126 [ 1.095782] ata3: SATA max UDMA/133 abar m2048@0xa1339000 port 0xa1339200 irq 126 [ 1.095787] ata4: SATA max UDMA/133 abar m2048@0xa1339000 port 0xa1339280 irq 126 [ 1.095798] ata5: SATA max UDMA/133 abar m2048@0xa1339000 port 0xa1339300 irq 126 [ 1.095810] ata6: SATA max UDMA/133 abar m2048@0xa1339000 port 0xa1339380 irq 126 [ 1.096503] e1000e 0000:00:1f.6: irq 132 for MSI/MSI-X [ 1.196872] nvme 0000:06:00.0: irq 127 for MSI/MSI-X [ 1.196877] nvme 0000:06:00.0: irq 133 for MSI/MSI-X [ 1.196882] nvme 0000:06:00.0: irq 134 for MSI/MSI-X [ 1.196886] nvme 0000:06:00.0: irq 135 for MSI/MSI-X [ 1.196889] nvme 0000:06:00.0: irq 136 for MSI/MSI-X [ 1.436844] i915 0000:00:02.0: irq 137 for MSI/MSI-X [ 2.351174] parport0: PC-style at 0x378, irq 5 [PCSPP] [ 2.525337] snd_hda_intel 0000:00:1f.3: irq 138 for MSI/MSI-X
I do not know what you mean "check the pci chain". My knowledge of kernel level is weak, sorry. What else can I do?
The "checking the pci chain" argument is that sometimes the card is there but is cheerfully ignored. From
[ 1.720556] ixgbe 0000:01:00.0: irq 138 for MSI/MSI-X
You know that it is in bus 1 slot 0, so try something like
lspci -s 01:00.0 -v
to see if it reports something there. Just in the odd case the pci side of your computer knows there is a card there but the kernel can't be bothered (flaky driver?). I am probably not using the right terminology, and clearly expect someone to set me right, I've had network cards that would show in the pci chain but not in dmesg. Other thing you want to think about is that I've had cards that only worked if were inserted in a specific slot for no reason whatsoever.
Miroslav
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Dne 17.9.2019 v 15:25 Mauricio Tavares napsal(a):
On Tue, Sep 17, 2019 at 9:11 AM Miroslav Geisselreiter mg@intar.cz wrote:
Dne 17.9.2019 v 14:02 Mauricio Tavares napsal(a):
On Tue, Sep 17, 2019 at 7:06 AM Miroslav Geisselreiter mg@intar.cz wrote:
I have brand new PC with this components: CPU Intel® Pentium G5400, LGA1151 motherboard ASUS PRIME B360M-C 16 GB RAM HDD 2x ADATA SSD 256GB XPG GAMMIX S11, PCIe Gen3x4 M.2 2280 (RAID1) NIC Intel X550-T1 Ethernet Converged Network Adapter
I installed CentOS 7 and two NICs were detected: eno1 (on motherboard) enp1s0 (Intel X550-T1)
When I restart the machine sometimes enp1s0 is missing. It is not detected during boot. It looks like NIC card is not installed / not present. After next reboot everything is fine and I do not see any problems with NIC card.
How can I avoid this problem with missing NIC? Can you help me, please?
Nothing exciting on dmesg? Did you check the pci chain to see ifit is being reported as there?
I do not know what you mean "check the pci chain". My knowledge of kernel level is weak, sorry. What else can I do?
The "checking the pci chain" argument is that sometimes the cardis there but is cheerfully ignored. From
[ 1.720556] ixgbe 0000:01:00.0: irq 138 for MSI/MSI-X
You know that it is in bus 1 slot 0, so try something like
lspci -s 01:00.0 -v
to see if it reports something there. Just in the odd case the pci side of your computer knows there is a card there but the kernel can't be bothered (flaky driver?). I am probably not using the right terminology, and clearly expect someone to set me right, I've had network cards that would show in the pci chain but not in dmesg. Other thing you want to think about is that I've had cards that only worked if were inserted in a specific slot for no reason whatsoever.
Thank you Mauricio and Mark for fast response. lspci -s 01:00.0 -v 01:00.0 Ethernet controller: Intel Corporation Ethernet Controller 10G X550T (rev 01) Subsystem: Intel Corporation Ethernet Converged Network Adapter X550-T1 Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at a0000000 (64-bit, prefetchable) [size=2M] Memory at a0200000 (64-bit, prefetchable) [size=16K] Expansion ROM at a2300000 [disabled] [size=512K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+ Capabilities: [70] MSI-X: Enable+ Count=64 Masked- Capabilities: [a0] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Device Serial Number 9f-f8-46-ff-ff-28-00-00 Capabilities: [150] Alternative Routing-ID Interpretation (ARI) Capabilities: [160] Single Root I/O Virtualization (SR-IOV) Capabilities: [1a0] Transaction Processing Hints Capabilities: [1b0] Access Control Services Capabilities: [1c0] Latency Tolerance Reporting Capabilities: [1d0] #19 Kernel driver in use: ixgbe Kernel modules: ixgbe
I will check again after reboot and as Mark recommend I will reseat the card. I will check BIOS too. As this is production machine I cannot do that now. I am going to buy another cheaper 1 Gb Intel card for testing purposes. I will report my results later.
Miroslav
On Tue, Sep 17, 2019 at 9:55 AM Miroslav Geisselreiter mg@intar.cz wrote:
Dne 17.9.2019 v 15:25 Mauricio Tavares napsal(a):
On Tue, Sep 17, 2019 at 9:11 AM Miroslav Geisselreiter mg@intar.cz wrote:
Dne 17.9.2019 v 14:02 Mauricio Tavares napsal(a):
On Tue, Sep 17, 2019 at 7:06 AM Miroslav Geisselreiter mg@intar.cz wrote:
I have brand new PC with this components: CPU Intel® Pentium G5400, LGA1151 motherboard ASUS PRIME B360M-C 16 GB RAM HDD 2x ADATA SSD 256GB XPG GAMMIX S11, PCIe Gen3x4 M.2 2280 (RAID1) NIC Intel X550-T1 Ethernet Converged Network Adapter
I installed CentOS 7 and two NICs were detected: eno1 (on motherboard) enp1s0 (Intel X550-T1)
When I restart the machine sometimes enp1s0 is missing. It is not detected during boot. It looks like NIC card is not installed / not present. After next reboot everything is fine and I do not see any problems with NIC card.
How can I avoid this problem with missing NIC? Can you help me, please?
Nothing exciting on dmesg? Did you check the pci chain to see ifit is being reported as there?
I do not know what you mean "check the pci chain". My knowledge of kernel level is weak, sorry. What else can I do?
The "checking the pci chain" argument is that sometimes the cardis there but is cheerfully ignored. From
[ 1.720556] ixgbe 0000:01:00.0: irq 138 for MSI/MSI-X
You know that it is in bus 1 slot 0, so try something like
lspci -s 01:00.0 -v
to see if it reports something there. Just in the odd case the pci side of your computer knows there is a card there but the kernel can't be bothered (flaky driver?). I am probably not using the right terminology, and clearly expect someone to set me right, I've had network cards that would show in the pci chain but not in dmesg. Other thing you want to think about is that I've had cards that only worked if were inserted in a specific slot for no reason whatsoever.
Thank you Mauricio and Mark for fast response. lspci -s 01:00.0 -v 01:00.0 Ethernet controller: Intel Corporation Ethernet Controller 10G X550T (rev 01) Subsystem: Intel Corporation Ethernet Converged Network Adapter X550-T1 Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at a0000000 (64-bit, prefetchable) [size=2M] Memory at a0200000 (64-bit, prefetchable) [size=16K] Expansion ROM at a2300000 [disabled] [size=512K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+ Capabilities: [70] MSI-X: Enable+ Count=64 Masked- Capabilities: [a0] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Device Serial Number 9f-f8-46-ff-ff-28-00-00 Capabilities: [150] Alternative Routing-ID Interpretation (ARI) Capabilities: [160] Single Root I/O Virtualization (SR-IOV) Capabilities: [1a0] Transaction Processing Hints Capabilities: [1b0] Access Control Services Capabilities: [1c0] Latency Tolerance Reporting Capabilities: [1d0] #19 Kernel driver in use: ixgbe Kernel modules: ixgbe
I will check again after reboot and as Mark recommend I will reseat the card. I will check BIOS too. As this is production machine I cannot do that now. I am going to buy another cheaper 1 Gb Intel card for testing purposes. I will report my results later.
If lspci *always* show card, check the kernel module.
Miroslav
Miroslav Geisselreiter wrote:
Dne 17.9.2019 v 14:02 Mauricio Tavares napsal(a):
On Tue, Sep 17, 2019 at 7:06 AM Miroslav Geisselreiter mg@intar.cz wrote:
I have brand new PC with this components: CPU Intel® Pentium G5400, LGA1151 motherboard ASUS PRIME B360M-C 16 GB RAM HDD 2x ADATA SSD 256GB XPG GAMMIX S11, PCIe Gen3x4 M.2 2280 (RAID1) NIC Intel X550-T1 Ethernet Converged Network Adapter
I installed CentOS 7 and two NICs were detected: eno1 (on motherboard) enp1s0 (Intel X550-T1)
When I restart the machine sometimes enp1s0 is missing. It is not detected during boot. It looks like NIC card is not installed / not present. After next reboot everything is fine and I do not see any problems with NIC card.
How can I avoid this problem with missing NIC? Can you help me, please?
Nothing exciting on dmesg? Did you check the pci chain to see if it is being reported as there?
<snip> Have you done lspci when it happens, and compared to when it's working?
I almost wonder if it's either a hardware error, or something in the BIOS. Have you tried opening up the box and reseating the card?
mark
Am 17.09.2019 um 13:05 schrieb Miroslav Geisselreiter:
I have brand new PC with this components: CPU Intel® Pentium G5400, LGA1151 motherboard ASUS PRIME B360M-C 16 GB RAM HDD 2x ADATA SSD 256GB XPG GAMMIX S11, PCIe Gen3x4 M.2 2280 (RAID1) NIC Intel X550-T1 Ethernet Converged Network Adapter
I installed CentOS 7 and two NICs were detected: eno1 (on motherboard) enp1s0 (Intel X550-T1)
When I restart the machine sometimes enp1s0 is missing. It is not detected during boot. It looks like NIC card is not installed / not present. After next reboot everything is fine and I do not see any problems with NIC card.
How can I avoid this problem with missing NIC? Can you help me, please?
Hallo, perhaps a timing problem until the nic is up or a bios bug.
Ralf
Dne 17.9.2019 v 16:14 Ralf Prengel napsal(a):
Am 17.09.2019 um 13:05 schrieb Miroslav Geisselreiter:
I have brand new PC with this components: CPU Intel® Pentium G5400, LGA1151 motherboard ASUS PRIME B360M-C 16 GB RAM HDD 2x ADATA SSD 256GB XPG GAMMIX S11, PCIe Gen3x4 M.2 2280 (RAID1) NIC Intel X550-T1 Ethernet Converged Network Adapter
I installed CentOS 7 and two NICs were detected: eno1 (on motherboard) enp1s0 (Intel X550-T1)
When I restart the machine sometimes enp1s0 is missing. It is not detected during boot. It looks like NIC card is not installed / not present. After next reboot everything is fine and I do not see any problems with NIC card.
How can I avoid this problem with missing NIC? Can you help me, please?
Hallo, perhaps a timing problem until the nic is up or a bios bug.
Ralf
Thank you, Ralf. I will check if there is a new bios. If it is timing problem, can I do anything to solve this?
Mauricio:
If lspci*always* show card, check the kernel module.
modinfo ixgbe filename: /lib/modules/3.10.0-957.27.2.el7.x86_64/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko.xz version: 5.1.0-k-rh7.6 license: GPL description: Intel(R) 10 Gigabit PCI Express Network Driver author: Intel Corporation, linux.nics@intel.com retpoline: Y rhelversion: 7.6 srcversion: 8A6178275DDA252CA16D17C 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: mdio,ptp,dca intree: Y vermagic: 3.10.0-957.27.2.el7.x86_64 SMP mod_unload modversions signer: CentOS Linux kernel signing key sig_key: 52:0A:4E:2D:9D:55:3E:F8:42:01:C1:88:B8:7F:E5:1B:9D:E1:1A:5E sig_hashalgo: sha256 parm: max_vfs:Maximum number of virtual functions to allocate per physical function - default is zero and maximum value is 63 (uint) parm: allow_unsupported_sfp:Allow unsupported and untested SFP+ modules on 82599-based adapters (uint) parm: debug:Debug level (0=none,...,16=all) (int)
Mauricio, what else shloud I check with kernel module?
Mirek
Am 17.09.2019 um 16:31 schrieb Miroslav Geisselreiter:
Hallo, perhaps a timing problem until the nic is up or a bios bug.
Ralf
Thank you, Ralf. I will check if there is a new bios. If it is timing problem, can I do anything to solve this?
Use a delay in the grub config to verify that the nic is active before booting. For testing you can insert sleeps in the starting scripts to identify timing problems. If both cards are connected with the switch does anything change when the cables are changed a to b and b to a?
Ralf
Dne 17.9.2019 v 17:34 Ralf Prengel napsal(a):
Am 17.09.2019 um 16:31 schrieb Miroslav Geisselreiter:
Hallo, perhaps a timing problem until the nic is up or a bios bug.
Ralf
Thank you, Ralf. I will check if there is a new bios. If it is timing problem, can I do anything to solve this?
Use a delay in the grub config to verify that the nic is active before booting. For testing you can insert sleeps in the starting scripts to identify timing problems. If both cards are connected with the switch does anything change when the cables are changed a to b and b to a?
Ralf
I set the delay and it seems to have helped. After several restarts without problems.
Mirek
-
mark -
Mauricio Tavares -
Miroslav Geisselreiter -
Ralf Prengel