Skip to main content
How Can We Help?
< All Topics
Print

Experiment: Thread Delete-Lifecycle Status Difference

Posted
Updated
ByJstar269

Experiment ID: EXP-THREAD-DELETE-LIFECYCLE-20260805-A · State: ACCEPTANCE ELIGIBLE · Classification: DIFFERENCE retained for follow-up

Question

Does the source-owned thread-delete lifecycle expose the same status aggregate on Nakagawa and PSP hardware?

Observation

All recorded scalar fields matched except one aggregate: Nakagawa reported 0x00001fff, while PSP-3001/6.61-ARK reported 0x00001fdf. The difference mask is 0x00000020.

Interpretation

This is a bounded lifecycle difference, not proof of a complete delete contract. The differing bit may reflect a flag, a sampled lifecycle instant, or CFW/PSPLink influence. The exact field origin remains open.

Claims not supported

  • No mapping of bit 0x20 to a documented status flag yet.
  • No claim that ordinary non-delete WaitThreadEnd behavior is affected.
  • No cross-model/cross-firmware result.

Next discriminating experiment

Extend the source-owned probe to emit each documented status field and query it before, during, and after delete/dormant transitions; repeat with UID reuse and another model/firmware. Do not publish opaque kernel memory dumps.

Related: CONFLICT-THREAD-DELETE-STATUS-001 · CONFLICT-THREAD-DELETE-STATUS-001 · ThreadMan reference.

Publication safety: public scalar aggregate only; private fixture withheld. Last reviewed: 2026-08-11.

Current source anchor — Wave 4

The lifecycle comparison was checked against src/rt/sched.c at main 04daf156. The exact-head link anchors implementation context; the status difference remains a bounded hardware observation.

Table of Contents