macb 1f00100000.ethernet eth0: NETDEV WATCHDOG: CPU: 3: transmit queue 0 timed out 201988 ms
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 25/100
- Issue 类型
- 缺陷
- 描述清晰度
- 需要澄清
- 活跃度
- 活跃
- 技术栈
- c, linux, raspberry-pi
调研方向
Start with the macb Ethernet driver entry point and the supplied kernel logs and raspinfo.txt. Investigate what causes the Raspberry Pi 5 transmit queue to stop completing without a reliable reproduction path. Done means identifying a reproducible trigger or root cause and validating a fix against the reported NETDEV WATCHDOG failures.
由索引模型根据 Issue 内容生成。
描述
Describe the bug
I have a toy cluster of Pi 5 devices. Every so often one of them stops responding over the network.
Steps to reproduce the behaviour
Unclear, seems to happen spontaneously.
Device (s)
Raspberry Pi 5
System
Logs
Here's the end of the kernel logs for the previous boot:
Sep 26 19:27:03 pi5c kernel: cni0: port 8(veth21d981ec) entered disabled state
Sep 26 19:27:03 pi5c kernel: veth21d981ec (unregistering): left allmulticast mode
Sep 26 19:27:03 pi5c kernel: veth21d981ec (unregistering): left promiscuous mode
Sep 26 19:27:03 pi5c kernel: cni0: port 8(veth21d981ec) entered disabled state
Sep 26 19:30:00 pi5c kernel: cni0: port 8(veth8d5ceb02) entered blocking state
Sep 26 19:30:00 pi5c kernel: cni0: port 8(veth8d5ceb02) entered disabled state
Sep 26 19:30:00 pi5c kernel: veth8d5ceb02: entered allmulticast mode
Sep 26 19:30:00 pi5c kernel: veth8d5ceb02: entered promiscuous mode
Sep 26 19:30:00 pi5c kernel: cni0: port 8(veth8d5ceb02) entered blocking state
Sep 26 19:30:00 pi5c kernel: cni0: port 8(veth8d5ceb02) entered forwarding state
Sep 26 19:30:03 pi5c kernel: cni0: port 8(veth8d5ceb02) entered disabled state
Sep 26 19:30:03 pi5c kernel: veth8d5ceb02 (unregistering): left allmulticast mode
Sep 26 19:30:03 pi5c kernel: veth8d5ceb02 (unregistering): left promiscuous mode
Sep 26 19:30:03 pi5c kernel: cni0: port 8(veth8d5ceb02) entered disabled state
Sep 27 03:29:13 pi5c kernel: macb 1f00100000.ethernet eth0: NETDEV WATCHDOG: CPU: 3: transmit queue 0 timed out 5004 ms
Sep 27 03:36:16 pi5c kernel: macb 1f00100000.ethernet eth0: NETDEV WATCHDOG: CPU: 3: transmit queue 0 timed out 5316 ms
Sep 27 04:14:19 pi5c kernel: macb 1f00100000.ethernet eth0: NETDEV WATCHDOG: CPU: 3: transmit queue 0 timed out 5724 ms
Sep 27 05:02:23 pi5c kernel: macb 1f00100000.ethernet eth0: NETDEV WATCHDOG: CPU: 3: transmit queue 0 timed out 5004 ms
Sep 27 07:44:41 pi5c kernel: sd 10:0:0:1: [sdk] 2129920 512-byte logical blocks: (1.09 GB/1.02 GiB)
Sep 27 07:44:41 pi5c kernel: sdk: detected capacity change from 1081344 to 2129920
Sep 27 09:42:53 pi5c kernel: macb 1f00100000.ethernet eth0: NETDEV WATCHDOG: CPU: 3: transmit queue 0 timed out 5004 ms
Sep 27 10:16:20 pi5c kernel: macb 1f00100000.ethernet eth0: NETDEV WATCHDOG: CPU: 3: transmit queue 0 timed out 5968 ms
Sep 27 13:37:43 pi5c kernel: macb 1f00100000.ethernet eth0: NETDEV WATCHDOG: CPU: 3: transmit queue 0 timed out 5540 ms
Sep 27 17:02:58 pi5c kernel: macb 1f00100000.ethernet eth0: NETDEV WATCHDOG: CPU: 3: transmit queue 0 timed out 5008 ms
Sep 27 17:14:46 pi5c kernel: macb 1f00100000.ethernet eth0: NETDEV WATCHDOG: CPU: 3: transmit queue 0 timed out 5204 ms
Sep 28 04:39:03 pi5c kernel: macb 1f00100000.ethernet eth0: NETDEV WATCHDOG: CPU: 3: transmit queue 0 timed out 5120 ms
Sep 28 04:39:08 pi5c kernel: macb 1f00100000.ethernet eth0: NETDEV WATCHDOG: CPU: 3: transmit queue 0 timed out 9984 ms
Sep 28 04:39:13 pi5c kernel: macb 1f00100000.ethernet eth0: NETDEV WATCHDOG: CPU: 3: transmit queue 0 timed out 15104 ms
Sep 28 04:39:18 pi5c kernel: macb 1f00100000.ethernet eth0: NETDEV WATCHDOG: CPU: 3: transmit queue 0 timed out 19968 ms
Sep 28 04:39:23 pi5c kernel: macb 1f00100000.ethernet eth0: NETDEV WATCHDOG: CPU: 3: transmit queue 0 timed out 25088 ms
Sep 28 04:39:28 pi5c kernel: macb 1f00100000.ethernet eth0: NETDEV WATCHDOG: CPU: 3: transmit queue 0 timed out 29952 ms
Sep 28 04:39:33 pi5c kernel: macb 1f00100000.ethernet eth0: NETDEV WATCHDOG: CPU: 3: transmit queue 0 timed out 35072 ms
Sep 28 04:39:38 pi5c kernel: macb 1f00100000.ethernet eth0: NETDEV WATCHDOG: CPU: 3: transmit queue 0 timed out 39936 ms
Sep 28 04:39:43 pi5c kernel: macb 1f00100000.ethernet eth0: NETDEV WATCHDOG: CPU: 3: transmit queue 0 timed out 45056 ms
Sep 28 04:39:48 pi5c kernel: macb 1f00100000.ethernet eth0: NETDEV WATCHDOG: CPU: 3: transmit queue 0 timed out 50180 ms
Sep 28 04:39:54 pi5c kernel: macb 1f00100000.ethernet eth0: NETDEV WATCHDOG: CPU: 3: transmit queue 0 timed out 56068 ms
Sep 28 04:39:59 pi5c kernel: macb 1f00100000.ethernet eth0: NETDEV WATCHDOG: CPU: 3: transmit queue 0 timed out 60928 ms
...more of that...
Sep 28 08:03:31 pi5c kernel: macb 1f00100000.ethernet eth0: NETDEV WATCHDOG: CPU: 3: transmit queue 0 timed out 12273152 ms
Sep 28 08:03:36 pi5c kernel: macb 1f00100000.ethernet eth0: NETDEV WATCHDOG: CPU: 3: transmit queue 0 timed out 12278016 ms
Sep 28 08:03:41 pi5c kernel: macb 1f00100000.ethernet eth0: NETDEV WATCHDOG: CPU: 3: transmit queue 0 timed out 12283136 ms
Sep 28 08:03:46 pi5c kernel: macb 1f00100000.ethernet eth0: NETDEV WATCHDOG: CPU: 3: transmit queue 0 timed out 12288000 ms
Sep 28 08:03:51 pi5c kernel: macb 1f00100000.ethernet eth0: NETDEV WATCHDOG: CPU: 3: transmit queue 0 timed out 12293120 ms
Sep 28 08:03:56 pi5c kernel: macb 1f00100000.ethernet eth0: NETDEV WATCHDOG: CPU: 3: transmit queue 0 timed out 12297988 ms
Sep 28 08:04:01 pi5c kernel: macb 1f00100000.ethernet eth0: NETDEV WATCHDOG: CPU: 3: transmit queue 0 timed out 12303104 ms
Sep 28 08:04:06 pi5c kernel: macb 1f00100000.ethernet eth0: NETDEV WATCHDOG: CPU: 3: transmit queue 0 timed out 12307968 ms
Sep 28 08:04:11 pi5c kernel: macb 1f00100000.ethernet eth0: NETDEV WATCHDOG: CPU: 3: transmit queue 0 timed out 12313088 ms
Sep 28 08:04:16 pi5c kernel: macb 1f00100000.ethernet eth0: NETDEV WATCHDOG: CPU: 3: transmit queue 0 timed out 12317952 ms
Sep 28 08:04:21 pi5c kernel: macb 1f00100000.ethernet eth0: NETDEV WATCHDOG: CPU: 3: transmit queue 0 timed out 12323072 ms
Additional context
No response
- 主要语言
- C
- 星标
- 13.2k
- 派生
- 5.5k
- 平均合并
- 1 天 16 小时
- 30 天内合并 PR
- 23
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
raspberrypi/linux 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 68/100
raspberrypi/linux#7415 · 2 条评论 · 1 个 reaction ·
维护者通常 1 天内回复
-
rp1-cfe doesn't forward V4L2_EVENT_SOURCE_CHANGE event from csi-2 sensor driver to userspace app未关闭
难度 2/5 1-3 小时 新手友好度 72/100
raspberrypi/linux#7399 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 82/100
raspberrypi/linux#7357 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
raspberrypi/linux#7054 · 2 条评论 ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 15/100
raspberrypi/linux#7683 · 8 条评论 ·
维护者通常 1 天内回复
查看 raspberrypi/linux 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 70/100
OpenPrinting/cups#1772 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 88/100
snowballstem/snowball#311 ·
-
tech-debt
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100