8814A retry carve-out bench: blocked on rig 8814AU health (3081 fw-boot dead)
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 25/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 冷清
- 技术栈
- c, linux
- 领域
- embedded-iot, testing
调研方向
The remaining work is a hardware A/B on a healthy 8814A, using tests/kestrel_retry_witness.sh with the command and limits listed in the issue; tests/adapter_doctor_cold.sh is the formal grading pass. First restore or access a healthy bench rig, then measure both arms. Done means obtaining the stated modal copies without TX-wedge, then following the issue’s pass/fail outcome; the issue is blocked by unavailable hardware.
由索引模型根据 Issue 内容生成。
描述
The last open item from #365 (step 5), split out so the parent could close on its measured results.
State: branch 8814a-retry-audit carries the audited change — write DATA_RETRY_LIMIT from cfg on the 8814A like every other die. The carve-out it removes traces to byte-matching 88XXau's monitor-injection descriptor during the #50 silence hunt (the kernel leaves the field 0 because its injection path never retries), not to a die erratum: RETRY_LIMIT_ENABLE=1 in both drivers, and the OWN/DISQSELSEQ + GID skips — which DO encode real 8814A field-meaning differences — stay.
The blocker: the bench 8814AU's 3081 MCU no longer boots — _Fwdl8814_KernelPath: RSVD-page ack failed + CPU_DL_READY never asserted across two real VBUS cold cycles (including an 8 s drain) at hub 3-2.3 port 2. Dead host TX with or without the change, so neither arm of the A/B is measurable. tests/adapter_doctor_cold.sh is the formal grading pass when someone is at the bench.
The bench (ready to run on a healthy 8814A):
sudo TX_PID=0x8813 WIT_PID=0xc812 LIMITS="0 2 8" SECS=8 bash tests/kestrel_retry_witness.sh
Pass = limit-obedient modal copies {1,3,9} (the field counts retries on 11ac dies) and no TX-wedge (rc=-7 patterns). Then: merge the branch, flip tx_retry_limit_ok for CHIP_8814A, update the truth tables. Fail = keep the carve-out, but documented as measured rather than inherited — the acceptable outcome #365 named.
Refs: #365 (parent), #374/#375 (the sibling steps that closed it), branch 8814a-retry-audit.
- 主要语言
- C
- 星标
- 56
- 派生
- 29
- 平均合并
- 3 小时 43 分钟
- 30 天内合并 PR
- 75
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
OpenIPC/devourer 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
Follow-ups left open by the 8822B fast bandwidth toggle fix (#584)可能已有人在做 @josephnef 今天认领。 未关闭enhancement
难度 4/5 3-5 天 新手友好度 42/100
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 12/100
OpenIPC/devourer#579 · 1 条评论 ·
维护者通常 1 天内回复
-
enhancement
难度 5/5 一周以上 新手友好度 12/100
维护者通常 1 天内回复
-
enhancement
难度 5/5 一周以上 新手友好度 8/100
维护者通常 1 天内回复
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
Needs-Triage
难度 2/5 1-3 小时 新手友好度 66/100
维护者通常 2 天内回复
-
issue: bug report
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 2 天内回复
-
cross-platform fix-now
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 1 天内回复
-
feature:index kind:crash status:confirmed triaged
难度 2/5 1-3 小时 新手友好度 77/100
维护者通常 1 天内回复