- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
I have a strange behavior with I226V NICs on a QOTOM QDNV01 device. I don't know if is a real issue or not, but maybe somebody from Intel can give me some advices.
dmidecode:
# dmidecode 3.5
Getting SMBIOS data from sysfs.
SMBIOS 3.0.0 present.
Table at 0x7F2FF000.
Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
Vendor: American Megatrends Inc.
Version: 5.13
Release Date: 02/21/2024
Address: 0xF0000
Runtime Size: 64 kB
ROM Size: 8 MB
Characteristics:
PCI is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
BIOS ROM is socketed
EDD is supported
5.25"/1.2 MB floppy services are supported (int 13h)
3.5"/720 kB floppy services are supported (int 13h)
3.5"/2.88 MB floppy services are supported (int 13h)
Print screen service is supported (int 5h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
ACPI is supported
USB legacy is supported
BIOS boot specification is supported
Targeted content distribution is supported
UEFI is supported
BIOS Revision: 5.13
Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: Default string
Product Name: QDNV01
Version: Default string
Serial Number: Default string
UUID: 03000200-0400-0500-0006-000700080009
Wake-up Type: Power Switch
SKU Number: Default string
Family: Default string
Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
Manufacturer: Default string
Product Name: QDNV01
Version: Default string
Serial Number: Default string
Asset Tag: Default string
Features:
Board is a hosting board
Board is replaceable
Location In Chassis: Default string
Chassis Handle: 0x0003
Type: Motherboard
Contained Object Handles: 0
Handle 0x0003, DMI type 3, 22 bytes
Chassis Information
Manufacturer: Default string
Type: Desktop
Lock: Not Present
Version: Default string
Serial Number: Default string
Asset Tag: Default string
Boot-up State: Safe
Power Supply State: Safe
Thermal State: Safe
Security Status: None
OEM Information: 0x00000000
Height: Unspecified
Number Of Power Cords: 1
Contained Elements: 0
SKU Number: Default string
Handle 0x0004, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J1A1
Internal Connector Type: None
External Reference Designator: PS2Mouse
External Connector Type: PS/2
Port Type: Mouse Port
Handle 0x0005, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J1A1
Internal Connector Type: None
External Reference Designator: Keyboard
External Connector Type: PS/2
Port Type: Keyboard Port
Handle 0x0006, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J2A1
Internal Connector Type: None
External Reference Designator: TV Out
External Connector Type: Mini Centronics Type-14
Port Type: Other
Handle 0x0007, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J2A2A
Internal Connector Type: None
External Reference Designator: COM A
External Connector Type: DB-9 male
Port Type: Serial Port 16550A Compatible
Handle 0x0008, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J2A2B
Internal Connector Type: None
External Reference Designator: Video
External Connector Type: DB-15 female
Port Type: Video Port
Handle 0x0009, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J3A1
Internal Connector Type: None
External Reference Designator: USB1
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x000A, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J3A1
Internal Connector Type: None
External Reference Designator: USB2
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x000B, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J3A1
Internal Connector Type: None
External Reference Designator: USB3
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x000C, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J9A1 - TPM HDR
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x000D, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J9C1 - PCIE DOCKING CONN
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x000E, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J2B3 - CPU FAN
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x000F, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J6C2 - EXT HDMI
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x0010, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J3C1 - GMCH FAN
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x0011, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J1D1 - ITP
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x0012, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J9E2 - MDC INTPSR
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x0013, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J9E4 - MDC INTPSR
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x0014, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J9E3 - LPC HOT DOCKING
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x0015, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J9E1 - SCAN MATRIX
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x0016, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J9G1 - LPC SIDE BAND
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x0017, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J8F1 - UNIFIED
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x0018, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J6F1 - LVDS
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x0019, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J2F1 - LAI FAN
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x001A, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J2G1 - GFX VID
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x001B, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J1G6 - AC JACK
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x001C, DMI type 9, 17 bytes
System Slot Information
Designation: Slot1
Type: x8 PCI Express 3 x8
Current Usage: In Use
Length: Long
ID: 1
Characteristics:
3.3 V is provided
PME signal is supported
Bus Address: 0000:00:09.0
Handle 0x001D, DMI type 9, 17 bytes
System Slot Information
Designation: Slot2
Type: x4 PCI Express 3 x4
Current Usage: In Use
Length: Long
ID: 2
Characteristics:
3.3 V is provided
PME signal is supported
Bus Address: 0000:00:0e.0
Handle 0x001E, DMI type 9, 17 bytes
System Slot Information
Designation: Slot3
Type: x4 PCI Express 3 x4
Current Usage: In Use
Length: Long
ID: 3
Characteristics:
3.3 V is provided
PME signal is supported
Bus Address: 0000:00:10.0
Handle 0x001F, DMI type 10, 6 bytes
On Board Device Information
Type: Video
Status: Enabled
Description: To Be Filled By O.E.M.
Handle 0x0020, DMI type 11, 5 bytes
OEM Strings
String 1: Default string
Handle 0x0021, DMI type 12, 5 bytes
System Configuration Options
Option 1: Default string
Handle 0x0022, DMI type 32, 20 bytes
System Boot Information
Status: No errors detected
Handle 0x0023, DMI type 41, 11 bytes
Onboard Device
Reference Designation: Onboard Video
Type: Video
Status: Enabled
Type Instance: 1
Bus Address: 0000:0b:00.0
Handle 0x0024, DMI type 15, 73 bytes
System Event Log
Area Length: 65535 bytes
Header Start Offset: 0x0000
Header Length: 16 bytes
Data Start Offset: 0x0010
Access Method: Memory-mapped physical 32-bit address
Access Address: 0xFF850000
Status: Valid, Not Full
Change Token: 0x0000013B
Header Format: Type 1
Supported Log Type Descriptors: 25
Descriptor 1: Single-bit ECC memory error
Data Format 1: Multiple-event handle
Descriptor 2: Multi-bit ECC memory error
Data Format 2: Multiple-event handle
Descriptor 3: Parity memory error
Data Format 3: None
Descriptor 4: Bus timeout
Data Format 4: None
Descriptor 5: I/O channel block
Data Format 5: None
Descriptor 6: Software NMI
Data Format 6: None
Descriptor 7: POST memory resize
Data Format 7: None
Descriptor 8: POST error
Data Format 8: POST results bitmap
Descriptor 9: PCI parity error
Data Format 9: Multiple-event handle
Descriptor 10: PCI system error
Data Format 10: Multiple-event handle
Descriptor 11: CPU failure
Data Format 11: None
Descriptor 12: EISA failsafe timer timeout
Data Format 12: None
Descriptor 13: Correctable memory log disabled
Data Format 13: None
Descriptor 14: Logging disabled
Data Format 14: None
Descriptor 15: System limit exceeded
Data Format 15: None
Descriptor 16: Asynchronous hardware timer expired
Data Format 16: None
Descriptor 17: System configuration information
Data Format 17: None
Descriptor 18: Hard disk information
Data Format 18: None
Descriptor 19: System reconfigured
Data Format 19: None
Descriptor 20: Uncorrectable CPU-complex error
Data Format 20: None
Descriptor 21: Log area reset/cleared
Data Format 21: None
Descriptor 22: System boot
Data Format 22: None
Descriptor 23: End of log
Data Format 23: None
Descriptor 24: OEM-specific
Data Format 24: OEM-specific
Descriptor 25: OEM-specific
Data Format 25: OEM-specific
Handle 0x0025, DMI type 16, 23 bytes
Physical Memory Array
Location: System Board Or Motherboard
Use: System Memory
Error Correction Type: None
Maximum Capacity: 128 GB
Error Information Handle: Not Provided
Number Of Devices: 4
Handle 0x0026, DMI type 19, 31 bytes
Memory Array Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x001FFFFFFFF
Range Size: 8 GB
Physical Array Handle: 0x0025
Partition Width: 1
Handle 0x0027, DMI type 17, 40 bytes
Memory Device
Array Handle: 0x0025
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 8 GB
Form Factor: DIMM
Set: None
Locator: DIMM0
Bank Locator: BANK 0
Type: DDR4
Type Detail: Synchronous Unbuffered (Unregistered)
Speed: 2400 MT/s
Manufacturer: Crucial
Serial Number: XXXXXXXX
Asset Tag: BANK 0 DIMM0 AssetTag
Part Number: CT8G4SFS824A.C8FE
Rank: 1
Configured Memory Speed: 2400 MT/s
Minimum Voltage: 1.2 V
Maximum Voltage: 1.2 V
Configured Voltage: 1.2 V
Handle 0x0028, DMI type 20, 35 bytes
Memory Device Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x001FFFFFFFF
Range Size: 8 GB
Physical Device Handle: 0x0027
Memory Array Mapped Address Handle: 0x0026
Partition Row Position: Unknown
Handle 0x0029, DMI type 17, 40 bytes
Memory Device
Array Handle: 0x0025
Error Information Handle: Not Provided
Total Width: Unknown
Data Width: Unknown
Size: No Module Installed
Form Factor: DIMM
Set: None
Locator: DIMM0
Bank Locator: BANK 1
Type: Unknown
Type Detail: Unknown
Handle 0x002A, DMI type 17, 40 bytes
Memory Device
Array Handle: 0x0025
Error Information Handle: Not Provided
Total Width: Unknown
Data Width: Unknown
Size: No Module Installed
Form Factor: DIMM
Set: None
Locator: DIMM1
Bank Locator: BANK 0
Type: Unknown
Type Detail: Unknown
Handle 0x002B, DMI type 17, 40 bytes
Memory Device
Array Handle: 0x0025
Error Information Handle: Not Provided
Total Width: Unknown
Data Width: Unknown
Size: No Module Installed
Form Factor: DIMM
Set: None
Locator: DIMM1
Bank Locator: BANK 1
Type: Unknown
Type Detail: Unknown
Handle 0x002C, DMI type 7, 19 bytes
Cache Information
Socket Designation: L1-Cache
Configuration: Enabled, Not Socketed, Level 1
Operational Mode: Write Back
Location: Internal
Installed Size: 56 kB
Maximum Size: 56 kB
Supported SRAM Types:
Synchronous
Installed SRAM Type: Synchronous
Speed: Unknown
Error Correction Type: Single-bit ECC
System Type: Instruction
Associativity: 8-way Set-associative
Handle 0x002D, DMI type 7, 19 bytes
Cache Information
Socket Designation: L2-Cache
Configuration: Enabled, Not Socketed, Level 2
Operational Mode: Write Back
Location: Internal
Installed Size: 2 MB
Maximum Size: 2 MB
Supported SRAM Types:
Synchronous
Installed SRAM Type: Synchronous
Speed: Unknown
Error Correction Type: Single-bit ECC
System Type: Unified
Associativity: 16-way Set-associative
Handle 0x002E, DMI type 4, 48 bytes
Processor Information
Socket Designation: CPU0
Type: Central Processor
Family: Pentium 4
Manufacturer: Intel(R) Corporation
ID: F1 06 05 00 FF FB EB BF
Signature: Type 0, Family 6, Model 95, Stepping 1
Flags:
FPU (Floating-point unit on-chip)
VME (Virtual mode extension)
DE (Debugging extension)
PSE (Page size extension)
TSC (Time stamp counter)
MSR (Model specific registers)
PAE (Physical address extension)
MCE (Machine check exception)
CX8 (CMPXCHG8 instruction supported)
APIC (On-chip APIC hardware supported)
SEP (Fast system call)
MTRR (Memory type range registers)
PGE (Page global enable)
MCA (Machine check architecture)
CMOV (Conditional move instruction supported)
PAT (Page attribute table)
PSE-36 (36-bit page size extension)
CLFSH (CLFLUSH instruction supported)
DS (Debug store)
ACPI (ACPI supported)
MMX (MMX technology supported)
FXSR (FXSAVE and FXSTOR instructions supported)
SSE (Streaming SIMD extensions)
SSE2 (Streaming SIMD extensions 2)
SS (Self-snoop)
HTT (Multi-threading)
TM (Thermal monitor supported)
PBE (Pending break enabled)
Version: Intel(R) Atom(TM) CPU C3758R @ 2.40GHz
Voltage: 1.6 V
External Clock: 100 MHz
Max Speed: 3800 MHz
Current Speed: 2400 MHz
Status: Populated, Enabled
Upgrade: Socket LGA775
L1 Cache Handle: 0x002C
L2 Cache Handle: 0x002D
L3 Cache Handle: Not Provided
Serial Number: Not Specified
Asset Tag: UNKNOWN
Part Number: Not Specified
Core Count: 8
Core Enabled: 8
Thread Count: 8
Characteristics:
64-bit capable
Multi-Core
Hardware Thread
Execute Protection
Enhanced Virtualization
Power/Performance Control
Handle 0x0035, DMI type 41, 11 bytes
Onboard Device
Reference Designation: Onboard SATA
Type: SATA Controller
Status: Enabled
Type Instance: 1
Bus Address: 0000:00:13.0
Handle 0x0037, DMI type 41, 11 bytes
Onboard Device
Reference Designation: Onboard SATA
Type: SATA Controller
Status: Enabled
Type Instance: 2
Bus Address: 0000:00:14.0
Handle 0x0039, DMI type 41, 11 bytes
Onboard Device
Reference Designation: Onboard LAN
Type: Ethernet
Status: Enabled
Type Instance: 1
Bus Address: 0000:0c:00.0
Handle 0x003B, DMI type 41, 11 bytes
Onboard Device
Reference Designation: Onboard LAN
Type: Ethernet
Status: Enabled
Type Instance: 2
Bus Address: 0000:0c:00.1
Handle 0x003D, DMI type 41, 11 bytes
Onboard Device
Reference Designation: Onboard LAN
Type: Ethernet
Status: Enabled
Type Instance: 3
Bus Address: 0000:0e:00.0
Handle 0x003F, DMI type 41, 11 bytes
Onboard Device
Reference Designation: Onboard LAN
Type: Ethernet
Status: Enabled
Type Instance: 4
Bus Address: 0000:0e:00.1
Handle 0x0041, DMI type 127, 4 bytes
End Of Table
lspci:
00:00.0 Host bridge: Intel Corporation Atom Processor C3000 Series System Agent (rev 11)
00:04.0 Host bridge: Intel Corporation Atom Processor C3000 Series Error Registers (rev 11)
00:05.0 Generic system peripheral [0807]: Intel Corporation Atom Processor C3000 Series Root Complex Event Collector (rev 11)
00:06.0 PCI bridge: Intel Corporation Atom Processor C3000 Series Integrated QAT Root Port (rev 11)
00:09.0 PCI bridge: Intel Corporation Atom Processor C3000 Series PCI Express Root Port #0 (rev 11)
00:0a.0 PCI bridge: Intel Corporation Atom Processor C3000 Series PCI Express Root Port #1 (rev 11)
00:0b.0 PCI bridge: Intel Corporation Atom Processor C3000 Series PCI Express Root Port #2 (rev 11)
00:0c.0 PCI bridge: Intel Corporation Atom Processor C3000 Series PCI Express Root Port #3 (rev 11)
00:0e.0 PCI bridge: Intel Corporation Atom Processor C3000 Series PCI Express Root Port #4 (rev 11)
00:0f.0 PCI bridge: Intel Corporation Atom Processor C3000 Series PCI Express Root Port #5 (rev 11)
00:10.0 PCI bridge: Intel Corporation Atom Processor C3000 Series PCI Express Root Port #6 (rev 11)
00:11.0 PCI bridge: Intel Corporation Atom Processor C3000 Series PCI Express Root Port #7 (rev 11)
00:12.0 System peripheral: Intel Corporation Atom Processor C3000 Series SMBus Contoller - Host (rev 11)
00:13.0 SATA controller: Intel Corporation Atom Processor C3000 Series SATA Controller 0 (rev 11)
00:14.0 SATA controller: Intel Corporation Atom Processor C3000 Series SATA Controller 1 (rev 11)
00:15.0 USB controller: Intel Corporation Atom Processor C3000 Series USB 3.0 xHCI Controller (rev 11)
00:16.0 PCI bridge: Intel Corporation Atom Processor C3000 Series Integrated LAN Root Port #0 (rev 11)
00:17.0 PCI bridge: Intel Corporation Atom Processor C3000 Series Integrated LAN Root Port #1 (rev 11)
00:18.0 Communication controller: Intel Corporation Atom Processor C3000 Series ME HECI 1 (rev 11)
00:1a.0 Serial controller: Intel Corporation Atom Processor C3000 Series HSUART Controller (rev 11)
00:1f.0 ISA bridge: Intel Corporation Atom Processor C3000 Series LPC or eSPI (rev 11)
00:1f.2 Memory controller: Intel Corporation Atom Processor C3000 Series Power Management Controller (rev 11)
00:1f.4 SMBus: Intel Corporation Atom Processor C3000 Series SMBus controller (rev 11)
00:1f.5 Serial bus controller: Intel Corporation Atom Processor C3000 Series SPI Controller (rev 11)
01:00.0 Co-processor: Intel Corporation Atom Processor C3000 Series QuickAssist Technology (rev 11)
02:00.0 Non-Volatile memory controller: Hosin Global Electronics Device 2283
05:00.0 Ethernet controller: Intel Corporation Ethernet Controller I226-V (rev 04)
06:00.0 Ethernet controller: Intel Corporation Ethernet Controller I226-V (rev 04)
07:00.0 Ethernet controller: Intel Corporation Ethernet Controller I226-V (rev 04)
08:00.0 Ethernet controller: Intel Corporation Ethernet Controller I226-V (rev 04)
09:00.0 Ethernet controller: Intel Corporation Ethernet Controller I226-V (rev 04)
0a:00.0 PCI bridge: ASPEED Technology, Inc. AST1150 PCI-to-PCI Bridge (rev 03)
0b:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED Graphics Family (rev 30)
0c:00.0 Ethernet controller: Intel Corporation Ethernet Connection X553 10 GbE SFP+ (rev 11)
0c:00.1 Ethernet controller: Intel Corporation Ethernet Connection X553 10 GbE SFP+ (rev 11)
0e:00.0 Ethernet controller: Intel Corporation Ethernet Connection X553 10 GbE SFP+ (rev 11)
0e:00.1 Ethernet controller: Intel Corporation Ethernet Connection X553 10 GbE SFP+ (rev 11)
Linux: Debian Trixie with Kernel 6.6.15-amd64 and 6.7.9-amd64
All I226-V Ethernet controllers are working fine if I'm using iperf3 on one direction: upload or download.
When I'm using iperf3 -s 10.10.10.1 --bidir then I'm getting these messages in dmesg:
[ 3138.590555] ixgbe 0000:0e:00.1 eth4: detected SFP+: 6
[ 3139.506623] ixgbe 0000:0e:00.0 eth3: NIC Link is Down
[ 3139.734453] ixgbe 0000:0e:00.1 eth4: NIC Link is Up 10 Gbps, Flow Control: RX/TX
[ 3140.306450] ixgbe 0000:0e:00.0 eth3: NIC Link is Up 10 Gbps, Flow Control: RX/TX
[ 3141.418810] igc 0000:08:00.0 eth5: NIC Link is Up 2500 Mbps Full Duplex, Flow Control: RX/TX
[ 3141.418813] igc 0000:06:00.0 eth6: NIC Link is Up 2500 Mbps Full Duplex, Flow Control: RX/TX
[ 3141.530803] igc 0000:05:00.0 eth8: NIC Link is Up 2500 Mbps Full Duplex, Flow Control: RX/TX
[ 3141.530804] igc 0000:07:00.0 eth7: NIC Link is Up 2500 Mbps Full Duplex, Flow Control: RX/TX
[ 3355.115211] {1}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 0
[ 3355.127649] {1}[Hardware Error]: It has been corrected by h/w and requires no further action
[ 3355.140277] {1}[Hardware Error]: event severity: corrected
[ 3355.150000] {1}[Hardware Error]: Error 0, type: corrected
[ 3355.159682] {1}[Hardware Error]: section_type: PCIe error
[ 3355.169350] {1}[Hardware Error]: port_type: 4, root port
[ 3355.178856] {1}[Hardware Error]: version: 1.16
[ 3355.187396] {1}[Hardware Error]: command: 0x0010, status: 0x0546
[ 3355.197496] {1}[Hardware Error]: device_id: 0000:06:00.0
[ 3355.206816] {1}[Hardware Error]: slot: 0
[ 3355.214643] {1}[Hardware Error]: secondary_bus: 0x00
[ 3355.223580] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x125c
[ 3355.234027] {1}[Hardware Error]: class_code: 000200
[ 3355.243159] igc 0000:06:00.0: AER: aer_status: 0x00002000, aer_mask: 0x00002000
[ 3355.254359] igc 0000:06:00.0: AER: aer_layer=Transaction Layer, aer_agent=Receiver ID
[ 3360.590158] igc 0000:06:00.0: AER: aer_status: 0x00002000, aer_mask: 0x00002000
[ 3360.601628] igc 0000:06:00.0: AER: aer_layer=Transaction Layer, aer_agent=Receiver ID
[ 3360.784137] {2}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 0
[ 3360.796847] {2}[Hardware Error]: It has been corrected by h/w and requires no further action
[ 3360.809883] {2}[Hardware Error]: event severity: corrected
[ 3360.820031] {2}[Hardware Error]: Error 0, type: corrected
[ 3360.830113] {2}[Hardware Error]: section_type: PCIe error
[ 3360.840212] {2}[Hardware Error]: port_type: 4, root port
[ 3360.850177] {2}[Hardware Error]: version: 1.16
[ 3360.859177] {2}[Hardware Error]: command: 0x0010, status: 0x0546
[ 3360.869845] {2}[Hardware Error]: device_id: 0000:08:00.0
[ 3360.879663] {2}[Hardware Error]: slot: 0
[ 3360.887982] {2}[Hardware Error]: secondary_bus: 0x00
[ 3360.897291] {2}[Hardware Error]: vendor_id: 0x8086, device_id: 0x125c
[ 3360.908091] {2}[Hardware Error]: class_code: 000200
[ 3360.917457] igc 0000:08:00.0: AER: aer_status: 0x00002000, aer_mask: 0x00002000
[ 3360.929080] igc 0000:08:00.0: AER: aer_layer=Transaction Layer, aer_agent=Receiver ID
[ 3362.172784] igc 0000:06:00.0: AER: aer_status: 0x00002000, aer_mask: 0x00002000
[ 3362.184536] igc 0000:06:00.0: AER: aer_layer=Transaction Layer, aer_agent=Receiver ID
[ 3363.313749] igc 0000:06:00.0: AER: aer_status: 0x00002000, aer_mask: 0x00002000
[ 3363.325663] igc 0000:06:00.0: AER: aer_layer=Transaction Layer, aer_agent=Receiver ID
[ 3369.411711] igc 0000:08:00.0: AER: aer_status: 0x00002000, aer_mask: 0x00002000
[ 3369.423719] igc 0000:08:00.0: AER: aer_layer=Transaction Layer, aer_agent=Receiver ID
[ 3371.361921] {3}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 0
[ 3371.374855] {3}[Hardware Error]: It has been corrected by h/w and requires no further action
[ 3371.388152] {3}[Hardware Error]: event severity: corrected
[ 3371.398433] {3}[Hardware Error]: Error 0, type: corrected
[ 3371.408691] {3}[Hardware Error]: section_type: PCIe error
[ 3371.419038] {3}[Hardware Error]: port_type: 4, root port
[ 3371.429281] {3}[Hardware Error]: version: 1.16
[ 3371.438614] {3}[Hardware Error]: command: 0x0010, status: 0x0546
[ 3371.449575] {3}[Hardware Error]: device_id: 0000:06:00.0
[ 3371.459845] {3}[Hardware Error]: slot: 0
[ 3371.468646] {3}[Hardware Error]: secondary_bus: 0x00
[ 3371.478475] {3}[Hardware Error]: vendor_id: 0x8086, device_id: 0x125c
[ 3371.489760] {3}[Hardware Error]: class_code: 000200
[ 3371.499494] igc 0000:06:00.0: AER: aer_status: 0x00002000, aer_mask: 0x00002000
[ 3371.511511] igc 0000:06:00.0: AER: aer_layer=Transaction Layer, aer_agent=Receiver ID
[ 3375.864209] {4}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 0
[ 3375.877210] {4}[Hardware Error]: It has been corrected by h/w and requires no further action
[ 3375.890399] {4}[Hardware Error]: event severity: corrected
[ 3375.900543] {4}[Hardware Error]: Error 0, type: corrected
[ 3375.910682] {4}[Hardware Error]: section_type: PCIe error
[ 3375.920915] {4}[Hardware Error]: port_type: 4, root port
[ 3375.931062] {4}[Hardware Error]: version: 1.16
[ 3375.940315] {4}[Hardware Error]: command: 0x0010, status: 0x0546
[ 3375.951193] {4}[Hardware Error]: device_id: 0000:08:00.0
[ 3375.961354] {4}[Hardware Error]: slot: 0
[ 3375.970116] {4}[Hardware Error]: secondary_bus: 0x00
[ 3375.979926] {4}[Hardware Error]: vendor_id: 0x8086, device_id: 0x125c
[ 3375.991246] {4}[Hardware Error]: class_code: 000200
[ 3376.001048] igc 0000:08:00.0: AER: aer_status: 0x00002000, aer_mask: 0x00002000
[ 3376.013092] igc 0000:08:00.0: AER: aer_layer=Transaction Layer, aer_agent=Receiver ID
Also the driver is crashing as soon I'm pushing over 1GbE traffic.
[ 3138.590555] ixgbe 0000:0e:00.1 eth4: detected SFP+: 6
[ 3139.506623] ixgbe 0000:0e:00.0 eth3: NIC Link is Down
[ 3139.734453] ixgbe 0000:0e:00.1 eth4: NIC Link is Up 10 Gbps, Flow Control: RX/TX
[ 3140.306450] ixgbe 0000:0e:00.0 eth3: NIC Link is Up 10 Gbps, Flow Control: RX/TX
[ 3141.418810] igc 0000:08:00.0 eth5: NIC Link is Up 2500 Mbps Full Duplex, Flow Control: RX/TX
[ 3141.418813] igc 0000:06:00.0 eth6: NIC Link is Up 2500 Mbps Full Duplex, Flow Control: RX/TX
[ 3141.530803] igc 0000:05:00.0 eth8: NIC Link is Up 2500 Mbps Full Duplex, Flow Control: RX/TX
[ 3141.530804] igc 0000:07:00.0 eth7: NIC Link is Up 2500 Mbps Full Duplex, Flow Control: RX/TX
[ 3355.115211] {1}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 0
[ 3355.127649] {1}[Hardware Error]: It has been corrected by h/w and requires no further action
[ 3355.140277] {1}[Hardware Error]: event severity: corrected
[ 3355.150000] {1}[Hardware Error]: Error 0, type: corrected
[ 3355.159682] {1}[Hardware Error]: section_type: PCIe error
[ 3355.169350] {1}[Hardware Error]: port_type: 4, root port
[ 3355.178856] {1}[Hardware Error]: version: 1.16
[ 3355.187396] {1}[Hardware Error]: command: 0x0010, status: 0x0546
[ 3355.197496] {1}[Hardware Error]: device_id: 0000:06:00.0
[ 3355.206816] {1}[Hardware Error]: slot: 0
[ 3355.214643] {1}[Hardware Error]: secondary_bus: 0x00
[ 3355.223580] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x125c
[ 3355.234027] {1}[Hardware Error]: class_code: 000200
[ 3355.243159] igc 0000:06:00.0: AER: aer_status: 0x00002000, aer_mask: 0x00002000
[ 3355.254359] igc 0000:06:00.0: AER: aer_layer=Transaction Layer, aer_agent=Receiver ID
[ 3360.590158] igc 0000:06:00.0: AER: aer_status: 0x00002000, aer_mask: 0x00002000
[ 3360.601628] igc 0000:06:00.0: AER: aer_layer=Transaction Layer, aer_agent=Receiver ID
[ 3360.784137] {2}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 0
[ 3360.796847] {2}[Hardware Error]: It has been corrected by h/w and requires no further action
[ 3360.809883] {2}[Hardware Error]: event severity: corrected
[ 3360.820031] {2}[Hardware Error]: Error 0, type: corrected
[ 3360.830113] {2}[Hardware Error]: section_type: PCIe error
[ 3360.840212] {2}[Hardware Error]: port_type: 4, root port
[ 3360.850177] {2}[Hardware Error]: version: 1.16
[ 3360.859177] {2}[Hardware Error]: command: 0x0010, status: 0x0546
[ 3360.869845] {2}[Hardware Error]: device_id: 0000:08:00.0
[ 3360.879663] {2}[Hardware Error]: slot: 0
[ 3360.887982] {2}[Hardware Error]: secondary_bus: 0x00
[ 3360.897291] {2}[Hardware Error]: vendor_id: 0x8086, device_id: 0x125c
[ 3360.908091] {2}[Hardware Error]: class_code: 000200
[ 3360.917457] igc 0000:08:00.0: AER: aer_status: 0x00002000, aer_mask: 0x00002000
[ 3360.929080] igc 0000:08:00.0: AER: aer_layer=Transaction Layer, aer_agent=Receiver ID
[ 3362.172784] igc 0000:06:00.0: AER: aer_status: 0x00002000, aer_mask: 0x00002000
[ 3362.184536] igc 0000:06:00.0: AER: aer_layer=Transaction Layer, aer_agent=Receiver ID
[ 3363.313749] igc 0000:06:00.0: AER: aer_status: 0x00002000, aer_mask: 0x00002000
[ 3363.325663] igc 0000:06:00.0: AER: aer_layer=Transaction Layer, aer_agent=Receiver ID
[ 3369.411711] igc 0000:08:00.0: AER: aer_status: 0x00002000, aer_mask: 0x00002000
[ 3369.423719] igc 0000:08:00.0: AER: aer_layer=Transaction Layer, aer_agent=Receiver ID
[ 3371.361921] {3}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 0
[ 3371.374855] {3}[Hardware Error]: It has been corrected by h/w and requires no further action
[ 3371.388152] {3}[Hardware Error]: event severity: corrected
[ 3371.398433] {3}[Hardware Error]: Error 0, type: corrected
[ 3371.408691] {3}[Hardware Error]: section_type: PCIe error
[ 3371.419038] {3}[Hardware Error]: port_type: 4, root port
[ 3371.429281] {3}[Hardware Error]: version: 1.16
[ 3371.438614] {3}[Hardware Error]: command: 0x0010, status: 0x0546
[ 3371.449575] {3}[Hardware Error]: device_id: 0000:06:00.0
[ 3371.459845] {3}[Hardware Error]: slot: 0
[ 3371.468646] {3}[Hardware Error]: secondary_bus: 0x00
[ 3371.478475] {3}[Hardware Error]: vendor_id: 0x8086, device_id: 0x125c
[ 3371.489760] {3}[Hardware Error]: class_code: 000200
[ 3371.499494] igc 0000:06:00.0: AER: aer_status: 0x00002000, aer_mask: 0x00002000
[ 3371.511511] igc 0000:06:00.0: AER: aer_layer=Transaction Layer, aer_agent=Receiver ID
[ 3375.864209] {4}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 0
[ 3375.877210] {4}[Hardware Error]: It has been corrected by h/w and requires no further action
[ 3375.890399] {4}[Hardware Error]: event severity: corrected
[ 3375.900543] {4}[Hardware Error]: Error 0, type: corrected
[ 3375.910682] {4}[Hardware Error]: section_type: PCIe error
[ 3375.920915] {4}[Hardware Error]: port_type: 4, root port
[ 3375.931062] {4}[Hardware Error]: version: 1.16
[ 3375.940315] {4}[Hardware Error]: command: 0x0010, status: 0x0546
[ 3375.951193] {4}[Hardware Error]: device_id: 0000:08:00.0
[ 3375.961354] {4}[Hardware Error]: slot: 0
[ 3375.970116] {4}[Hardware Error]: secondary_bus: 0x00
[ 3375.979926] {4}[Hardware Error]: vendor_id: 0x8086, device_id: 0x125c
[ 3375.991246] {4}[Hardware Error]: class_code: 000200
[ 3376.001048] igc 0000:08:00.0: AER: aer_status: 0x00002000, aer_mask: 0x00002000
[ 3376.013092] igc 0000:08:00.0: AER: aer_layer=Transaction Layer, aer_agent=Receiver ID
I did tests also under Windows 11 using IP Forwarding enabled and as soon I'm starting to push the traffic towards the ports is showing WHEA error pointing to PCIe roots.
Is it the hardware DOA or is another problem that can cause these issues?
I tried different options in Kernel: pcie_port_pm=off pcie_aspm.policy=performance
Or pci=nommconf pci=noaer. None of them fix anykind of issues. Maybe some of them doesn't crash the driver, but I'm not 100% sure.
In BIOS System Logs shows errors about PCI System Error and Parity Error. I tested the RAM and it passes without issues.
I did some video captures with my tests. I tried to disable ASPM in BIOS for all links and globally, I set PCIE Gen2 and Gen1. None of them are fixing the issue.
I have some video captures in different situations, in case somebody needs to see them.
Thank you.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello @EasyNet,
Thank you for contacting Intel Embedded Community.
You may check the with latest drivers:
https://sourceforge.net/projects/e1000/files/
Regarding the WHEA error in Windows, I looked internally that in Windows 10 this issue may not happen.
The APEI Generic Hardware Error can be due to the cable I've seen, you may try with a different one.
Also, being a third party device, may be best to make the consultation to Qotom so they can address the issue.
Best regards,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @Diego_INTEL
You understand that I didn't use only one cable. I have Cat6 and Cat6e cables and it was the first think I did.
Same cables I test between my Ryzen 5900X with an dual Intel I226-V PCIe card and my laptop Asus Zenbook UX461FN with i7-8565U using an USB Realtek RTL8156B.
Same cables between these 2 devices can handle 2.5GbE without any crashes. I'm repeating again: Ryzen 5900X with dual Intel I226-V PCIe card, same I226-V chips as Qotom.
As soon I'm passing the traffic through Qotom on 2.5GbE, same chipset as the PCIe card in my Ryzen 5900X, is crashing and receiving these hardware error from PCIe root ports:
Here is the video I did it in Windows 11 as router on Qotom:
Qotom in Windows 11 as router - PCIe root WHEA
Here is one of the videos done with Qotom in Debian Trixie running Kernel 6.7.9:
Qotom igc kernel crash in Linux
Qotom igc kernel crash and PCIe root error
I can't believe that 5 cables in total, all Cat6 or Cat6e are broken and are working fine only between Ryzen 5900X i226-V PCIe card and USB Realtek RTL8156B on my laptop or between my NAS using an I225-V M.2 card.
And the crash is not just on one port: both ports are crashing. Longer the test is, more crashes you will see on both ports.
Last Thursday the supplier told me that he will refund and I will return the device. He doesn't want to change it because he's afraid to not have the same issue also with the new one.
When I'm seeing errors related to PCIe root port, the only idea I have is the CPU itself has an malfunction, not the I226-V chip itself. When you see that all 5 I226-V have the same behavior and are triggering PCIe root port errors, is not the cable.
Please check the output of the lspci:
00:0c.0 PCI bridge: Intel Corporation Atom Processor C3000 Series PCI Express Root Port #3 (rev 11) 00:0e.0 PCI bridge: Intel Corporation Atom Processor C3000 Series PCI Express Root Port #4 (rev 11) 00:0f.0 PCI bridge: Intel Corporation Atom Processor C3000 Series PCI Express Root Port #5 (rev 11)
Under each PCIe root port these NICs are attached.
That's why I suspect CPU malfunction. At least in HSIO port (PCIe lanes). The 10GbE ports are not affected by this malfunction because, if you check the overview of the Atom C3000 series, are not using PCIe lanes to communicate with the CPU.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hey i have the exact same device with the exact same problem. Whenever there is an error (which seems to happen every 5-15 seconds) the network traffic on the i226 port stops processing. As I use this device as my router this is obviously a big problem. I have worked around it by getting a SFP+ to 10GBe adapter and just using that.
Ever get it fixed? Gotta say these i226 controllers seem like trash.... Years and years of people having issues. Intel USED to have a great reputation for network chipsets....
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The solution was to return the device back to the seller and refund the money.
I will never buy any Intel devices like this ever.
The 10GbE interfaces worked very nice, but as you said, 2.5GbE are crap.
I couldn't find out what was the issue. I still believe it was the CPU. I have a PCI-E dual I226-V card and is working fine on my AMD Ryzen 5900X.
I also have some NVME I225-V cards and I test them on this board and I got the same issues with PCI-e errors. So @intel your CPU is waste of sand.
Now I'm testing a Banana Pi BPI-R4 board with dual 10GbE. Main advantage it has very low power consumption.
The Intel in ilde I got 16W. This one is about 3-4W.
The second advantage it has an NPU (network process unit).
Next router, also based on ARM64 CPU, will be this one:
https://youtu.be/Ooj2fviV1rk?si=dxl6iWaoAvneYanr
This CPU from NXP, like the Mediatek CPU which has NPU, has DPAA2 which helps the network packets to not be processed by Linux Kernel.
Unfortunately Intel was not giving me any help regarding their broken CPU, so I'm not buying anything from Intel anymore.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello, @train_wreck:
Thank you for contacting Intel Embedded Community.
We received your consultation, but we want to address the following questions to understand it:
Could you please confirm if the device related to this situation has been designed by you or a third-party developer? In case it is a third-party device, please let us know the name of the manufacturer and the part number of the device.
For the i226, could you please confirm if this situation is related to an Intel Ethernet Controller, NIC card, or an adding card? Please mention the name of the manufacturer and part number.
Where do you purchase the device related to your request?
We are waiting for your clarification.
Best regards,
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page