chore: 导入旧记忆备份供恢复
This commit is contained in:
+20
@@ -0,0 +1,20 @@
|
||||
---
|
||||
title: Checkpoint 2026-09-16 14:50:11 UTC [79f944246a]
|
||||
type: checkpoint
|
||||
permalink: main/projects/6f47523e-e22e-4cdd-bd18-76e5e474ee0c/checkpoint-2026-09-16-14-50-11-utc-79f944246a
|
||||
stable_id: f74c51ae-9e95-4c54-8506-02699cf691bc
|
||||
scope: project
|
||||
memory_type: checkpoint
|
||||
project_id: 6f47523e-e22e-4cdd-bd18-76e5e474ee0c
|
||||
usage_profile_id: 7aee455b-24cc-4008-bdaf-443721e6f939
|
||||
status: active
|
||||
revision: 1
|
||||
request_id: ax9000-20260916-224513-crash-checkpoint-01
|
||||
created_at: '2026-09-16T14:50:11.270208+00:00'
|
||||
updated_at: '2026-09-16T14:50:11.270208+00:00'
|
||||
---
|
||||
|
||||
## 已完成
|
||||
2026-09-16用户再次报告刚刚闪断。22:47:51 CST SSH检查uptime仅2分钟,22:48:45 /proc/uptime195.97,证明刚刚整机重启。持久日志system.log第1118-1130行保存22:45:13内核异常:Unable to handle kernel paging request at virtual address ffffff80002a5b86;运行时间[4726.189543];ESR 0x96000006、EC0x25 DABT(current EL)、FSC0x06 level2 translation fault、WnR0。紧接新一轮启动日志(墙钟暂恢复为22:22:15,联网校时后跳22:46,不能误判22:22再次重启)。实机panic_on_oops=1、panic=3,与内核异常触发快速重启机制吻合;无scheduled-reboot日志,cron仍仅周一10:00,故本次周三22:45不是计划任务触发。日志未保存PC/LR/Call trace,不能归因ath11k/NSS/OAF或硬件。/sys/fs/pstore不存在,/proc/filesystems无pstore,未找到pstore/ramoops已载入或可用模块,虽DT预留ramoops和名为pstore的MTD分区,不代表当前有可读取转储。已保存事故快照到路由器/root/router-logs/incident-20260916-224513/system.log及dmesg-after-reboot.txt;不是MemRelay文件仓储文件。当前3个AP恢复。已异步询问用户这次是否手动重启/断电,尚待答复。此次仅读取与备份现场,未改网络或内核参数。
|
||||
## 下一步与给下个会话
|
||||
优先确认用户是否主动重启;无论是否主动,22:45:13内核异常已是实证。需要完整内核调用栈才能定位具体模块,可后续研究匹配当前固件的pstore/ramoops或网络内核日志采集方案;不要直接安装不匹配内核ABI的包,不要用地址单独猜模块或盲目禁用NSS。本次已保存截断事故快照,避免轮转覆盖。此前持久日志和周一重启计划仍有效,当前无线恢复。不要把联网校时前22:22开机日志当作计划重启触发时间。项目源码未修改。
|
||||
Reference in New Issue
Block a user