fix(kernel): the block chain's fast RAM is cleared on the v3 path

Browse Source

It came from kmalloc, which does not clear what it hands out; only the
ramdrive beside it was cleared.  A VM's BLOCK on blocks 0 to 2047 read
whatever had been in the kernel's heap.  The v4 path already cleared its
own.

Accepted on the v3 configuration: amd64, aarch64 and riscv64 reach the
zuse prompt, no UNKNOWN WORD, PARITY:M7.1a hash 0x08873e0f44b7cb2a on all
three, as before.  logs/20261007-140609, -140735, -140946.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

...

This commit is contained in:

rajames

2026-10-07 14:10:49 -04:00

co-authored by Claude Opus 5.5

parent 193523d873

commit a425f738a4

5 changed files with 27458 additions and 3 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

logs/20261007-140609/amd64/qemu-amd64-20261007-140609.log

+9143

File diff suppressed because it is too large Load Diff

logs/20261007-140735/aarch64/qemu-aarch64-20261007-140735.log

+9115

File diff suppressed because it is too large Load Diff

logs/20261007-140946/riscv64/qemu-riscv64-20261007-140946.log

+9187

File diff suppressed because it is too large Load Diff