[BUG] SMP bringup reaches the silence watchdog before the first EriX marker #84

Open
opened 2026-09-24 14:41:24 +02:00 by erikinkinen · 0 comments
Owner

Summary

One original trampoline SMP bringup execution reached the maintained 45-second silence watchdog before any EriX Bootloader or Kernel serial marker. The cause and first affected revision remain unknown.

Reproduction

The original subsystem-kernel-smp-bringup-positive scenario uses four CPUs, the release profile, real SMP and the 16-bit trampoline. Its original 60-second hard and 45-second silence limits are retained. Preserve this original failed execution; no unchanged-input acceptance retry has been performed.

Expected and actual behavior

Expected: reach firmware-to-Kernel entry, bring APs online and complete the existing SMP markers with the expected emulator exit. Actual: no EriX serial marker appears before the silence watchdog. A separate read-only QMP diagnostic of the retained image completes before its first scheduled CPU snapshot, so it captures no CPU state and supplies no acceptance credit or failure attribution. Bringup passes later on the changed controller/scheduler graph; that is distinct evidence and does not explain or repair the original stall.

Environment and identity

Original Integration 6e91da8147, Kernel 88e4ff4c65bbc12c89d054e52e045bd6c952346f and Bootloader ec00005c324ae05dc6f2faf57c496185d297726b. Native x86-64 QEMU 10.2.2, KVM, OVMF and four CPUs. The retained 166,400-byte Bootloader has SHA-256 5afac2047e89179f3312b6d6c980194dd36692f7f75bbccb8ad07142ee59c566 and matches the passing allocator-profile Bootloader.

Evidence and prior checks

Seven principal files and 229 original producer artifacts are retained with exact source signatures and packaged Kernel identity verified. QEMU stderr is empty; image builds contain no warnings. Firmware, binary and image identities and QMP diagnostic arguments are retained. The separate long-mode GLOBAL_RUNQ failure has an attributed correction; it is not a cause claim for this pre-entry silence.

Tracking

Keep this original failure open for evidence-driven diagnosis through Integration validation, PR 12 and Phase 6 completion. Preserve original timing and output contracts; a passing neighboring input or diagnostic does not close it.

## Summary One original trampoline SMP bringup execution reached the maintained 45-second silence watchdog before any EriX Bootloader or Kernel serial marker. The cause and first affected revision remain unknown. ## Reproduction The original subsystem-kernel-smp-bringup-positive scenario uses four CPUs, the release profile, real SMP and the 16-bit trampoline. Its original 60-second hard and 45-second silence limits are retained. Preserve this original failed execution; no unchanged-input acceptance retry has been performed. ## Expected and actual behavior Expected: reach firmware-to-Kernel entry, bring APs online and complete the existing SMP markers with the expected emulator exit. Actual: no EriX serial marker appears before the silence watchdog. A separate read-only QMP diagnostic of the retained image completes before its first scheduled CPU snapshot, so it captures no CPU state and supplies no acceptance credit or failure attribution. Bringup passes later on the changed controller/scheduler graph; that is distinct evidence and does not explain or repair the original stall. ## Environment and identity Original Integration 6e91da8147f02f8bbd0d5c0dd87fda8dd98e94a1, Kernel 88e4ff4c65bbc12c89d054e52e045bd6c952346f and Bootloader ec00005c324ae05dc6f2faf57c496185d297726b. Native x86-64 QEMU 10.2.2, KVM, OVMF and four CPUs. The retained 166,400-byte Bootloader has SHA-256 5afac2047e89179f3312b6d6c980194dd36692f7f75bbccb8ad07142ee59c566 and matches the passing allocator-profile Bootloader. ## Evidence and prior checks Seven principal files and 229 original producer artifacts are retained with exact source signatures and packaged Kernel identity verified. QEMU stderr is empty; image builds contain no warnings. Firmware, binary and image identities and QMP diagnostic arguments are retained. The separate long-mode GLOBAL_RUNQ failure has an attributed correction; it is not a cause claim for this pre-entry silence. ## Tracking Keep this original failure open for evidence-driven diagnosis through [Integration validation](https://git.erikinkinen.fi/erix/integration/issues/3), [PR 12](https://git.erikinkinen.fi/erix/integration/pulls/12) and [Phase 6 completion](https://git.erikinkinen.fi/erix/integration/issues/65). Preserve original timing and output contracts; a passing neighboring input or diagnostic does not close it.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:39:20 +01:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
erix/integration#84
No description provided.