Files
MobileGL/docs/Disaggregated/notes/p7/device-window-1/00-session/README.md
T
swung0x48 4f2d4c4e83 [MG_Remote, docs] (P7): CONTRACT-P7 carries wave 0's numbers, and device window #1a is on record
CONTRACT-P7: the lane counts (magma-split 73 / spawn 52 / tcp 54; full-suite 510 x 3
with one StreamLink x Magma red), the census baseline (79 abort sites over 20 files,
43 family words, 0 unmarked), the ratchet baseline (186 = p7-magma 101 / espryt 14 /
both 60 / core 11; espryt's clearable count is 9) and the @P7 count (15 sites / 4
files) replace the 待填 markers.

Device window #1a (Redmi 2f7cbe2e, APK p7w1-d260f110, reboot-clean): E0a monolith
39/39 deterministic, three below threshold on monolith itself (create-indirect,
1.21.11 main-menu, iris-photon - Adreno refuses its pipelines with VK_ERROR_UNKNOWN);
E0a inproc: OpenRA 0.976494 (run-ahead) / E1 lockstep 0.988998 - both historical
numbers were OpenRA, and its client log shows a TextureResources verb answered from
caps generation 0 (package F1); 26.3 / create-* SIGSEGV in the replayer's memcpy on
BOTH backends and with the persistent-map push off (package X1); iterationt x2 die
by name on Magma:mipmap-shader-format-or-shape (package B); bsl-esc-menu hits
scudo OOM under inproc. Gate 3's denominator is 36; run-ahead and present credit
are off the suspect list.
2026-09-22 14:49:42 -04:00

30 lines
2.5 KiB
Markdown
Executable File
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# 设备窗口 #1 · 会话记录(Redmi `2f7cbe2e`,2026-09-22)
按 [`../../device-window-1-runbook.md`](../../device-window-1-runbook.md) 执行。本窗口分两段:**1a**(E0–E3,只需 APK,不需要主机制品)在 wave 0 合并中途跑;**1b**(P6.5 残余 39 例 TCP 矩阵 + CTS `$BASE`)等 wave 0 全部合入、两端同 stamp 后跑。
## reboot-clean
- `boot-id-before.txt` = `7e6c6e9f-1894-4916-bf39-cce48c9abd37`(这是 P6 门 7 第二会话结束时的 boot id)
- `boot-id-after.txt` = `18d8d589-1b96-4cf1-b655-16d5b8d198ba` → **确实重启了**
- 唤醒 + `svc power stayon usb`;`deviceidle get deep` = `ACTIVE`;本包不在 Doze 白名单(`deviceidle-whitelist-before.txt` 为空)
## 钉频:VERDICT = DRIFT,如实记录,原因已定位
`pin_device.sh 2f7cbe2e pin` / `check` 都报 **DRIFT**:`gpu pinned to pwrlevel 0 but gpuclk=1100000000 (expected 1050000000)`。原始 kgsl 读数(root):
```
gpuclk=1100000000 max_gpuclk=1100000000 min_pwrlevel=0 max_pwrlevel=0 thermal_pwrlevel=0 default_pwrlevel=12
devfreq/max_freq=1050000000
available: 1100000000 1050000000 967000000 ... 160000000
```
也就是说:**这次重启后板子不再被 `thermal_pwrlevel=1` 闩住**(P6 记为「永久闩死、写 0 读回 1」,`pin_device.sh:85-97`),GPU 真的钉在 pwrlevel 0 = **1100 MHz**,与 `35d0befa` 那块板一样;DRIFT 是脚本对本板的期望值(1050 MHz)过期,不是钉频失败。判读:
- 对 **1a(E0–E3)**:实验量的是像素与重复确定性,频率不是变量,两臂同会话同频;本段照常进行,臂前后的 `check` 仍逐次记录(都会是同一条 DRIFT 行)。
- 对任何**逐线程 CPU 时间**的读数(本窗口没有):1100 MHz 会话与 P6 的 1050 MHz 会话绝对值不可比——这与 P6 原本的口径一致(`pin_device.sh:92-93`)。
- 后续小件(wave 2-E):`pin_device.sh` 的 `2f7cbe2e` 条目改成「pwrlevel 0 且 gpuclk ∈ {1100, 1050} MHz 都算 PINNED,并把实际值写进 check 输出」,理由在此。
## APK 身份
见 `apk.sha256` / `apk-install.txt`(安装后写入)。构建:`~/w7/pipe@d260f110`,`assembleTraceRelease -Pmobilegl.buildDisaggregated=ON -Pmobilegl.buildDisaggregatedInproc=ON -Pmobilegl.pipePush=ON -Pmobilegl.debuggableRelease=true -Pmobilegl.applicationIdSuffix=.p7w1 -Pmobilegl.apkSuffix=p7w1`,显式 `MOBILEGL_BUILD_STAMP=p7w1-d260f110`,debug keystore 签名,并排安装为 `top.mobilegl.plugin.p7w1.trace`。