Hello, I am using an ASUS AMD 768 Motherboard and Intel 82546/82544 NICs. In both 33 MHZ and 66 MHZ, the NIC indicates a number of receive errors. An example: Rx_Packets 3608189 Tx_Packets 614204 Rx_Bytes 591775085 Tx_Bytes 433241952 Rx_Errors 2018 Tx_Errors 0 Rx_Dropped 0 Tx_Dropped 0 Multicast 17708 Collisions 0 Rx_Length_Errors 0 Rx_Over_Errors 0 Rx_CRC_Errors 0 Rx_Frame_Errors 0 Rx_FIFO_Errors 2018 Rx_Missed_Errors 2018 Tx_Aborted_Errors 0 I tried increasing the Rx Descriptors size upto 4096 but that still did not help. Looking into the README, I find: RxIntDelay Valid Range: 0-65535 (0=off) Default Value: 0 (82542, 82543, and 82544-based adapters) 128 (82540, 82545, and 82546-based adapters) This value delays the generation of receive interrupts in units of 1.024 microseconds. Receive interrupt reduction can improve CPU efficiency if properly tuned for specific network traffic. Increasing this value adds extra latency to frame reception and can end up decreasing the throughput of TCP traffic. If the system is reporting dropped receives, this value may be set too high, causing the driver to run out of available receive descriptors. CAUTION: When setting RxIntDelay to a value other than 0, adapters based on the Intel 82543 and 82544 LAN controllers may hang (stop transmitting) under certain network conditions. If this occurs a message is logged in the system event log. In addition, the controller is automatically reset, restoring the network connection. To eliminate the potential for the hang ensure that RxIntDelay is set to 0. So, I set the RxIntDelay to 0. That definately reduced the Rx Errors but it still occurs. I tried using 4.3.2/4.3.15 driver but the problem persists. Has anybody seen this problem before? Any solutions is greatly appreciated ... Thanks Manish __________________________________________________ Do you Yahoo!? New DSL Internet Access from SBC & Yahoo! http://sbc.yahoo.com - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
