NETDEV WATCHDOG: eth1 (r8169): transmit queue 0 timed out
2018-02-23 15:59
926 查看
https://www.douban.com/note/251201964/
From: http://marc.info/?l=linux-netdev&m=135474171009246&w=2
The watchdog will fire if all these conditions are met:
1. The interface is up
2. A TX queue is stopped (normally because it is full)
3. No packets have been added to the queue in the last 5 seconds
4. The driver has not told the kernel that the device is unable to
transmit now (e.g. link is down).
Conditions 2 and 3 together normally mean that the TX queue has been
stopped for 5 seconds and therefore that few packets (not necessarily
none at all) have been completed in that time. The time taken for
individual packets to be completed is *not* considered.
This can happen due to:
a. Driver bug causing conditions 2 and 4 to be true during
reconfiguration
b. MAC blocked by a pause frame flood
c. IRQ handling is delayed by a long time (can happen due to excessive
serial logging)
d. Firmware bug causes driver to see link as up when it's not
e. Hardware fault (always a possibility)
---
Item d should really be expanded to hardware/firmware/software bug.
From: http://marc.info/?l=linux-netdev&m=135474171009246&w=2
The watchdog will fire if all these conditions are met:
1. The interface is up
2. A TX queue is stopped (normally because it is full)
3. No packets have been added to the queue in the last 5 seconds
4. The driver has not told the kernel that the device is unable to
transmit now (e.g. link is down).
Conditions 2 and 3 together normally mean that the TX queue has been
stopped for 5 seconds and therefore that few packets (not necessarily
none at all) have been completed in that time. The time taken for
individual packets to be completed is *not* considered.
This can happen due to:
a. Driver bug causing conditions 2 and 4 to be true during
reconfiguration
b. MAC blocked by a pause frame flood
c. IRQ handling is delayed by a long time (can happen due to excessive
serial logging)
d. Firmware bug causes driver to see link as up when it's not
e. Hardware fault (always a possibility)
---
Item d should really be expanded to hardware/firmware/software bug.
相关文章推荐
- [ISSUE]NETDEV WATCHDOG: eth0 (enc424j600): transmit queue 0 timed out
- “NETDEV WATCHDOG: eth0: transmit timed out”问题解决办法小结
- “NETDEV WATCHDOG: eth0: transmit timed out”问题解决办法小结
- linux-2.6.22 移植DM9000 micro2440 s3c2440 :NETDEV WATCHDOG: eth0: transmit timed out
- server kernel: NETDEV WATCHDOG: eth0: transmit timed out
- “NETDEV WATCHDOG: eth0: transmit timed out”问题解决办法小结
- “NETDEV WATCHDOG: eth0: transmit timed out” 后网卡当掉
- Asianux3 报kernel: NETDEV WATCHDOG: eth1: transmit timed out
- SOAPUI Exception:ERROR:java.net.ConnectException: Connection timed out: connect Solution
- java.net.SocketTimeoutException: connect timed out
- java.net.connectexception connection timed out connect 加载配置
- 【生产问题直播】java.net.SocketTimeoutException: Read timed out
- 调用webservice的时候报错 java.net.SocketTimeoutException: Read timed out
- 异常:java.net.ConnectException: Connection timed out: no further information
- java.net.SocketException: Connection timed out的一种情况
- Caused by: java.net.ConnectException: Connection timed out: connect||Caused by: com.mysql.jdbc.excep
- java.net.SocketTimeoutException: Connection timed out
- Caused by: java.net.ConnectException: Connection timed out: connect||Caused by: com.mysql.jdbc.excep
- java.net.SocketTimeoutException: Read timed out
- connection.getOutputStream() 报java.net.ConnectException: Connection timed out: connect