etwen/Blanton_TTL_Script
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 18 Wiki Activity

18 Releases 18 Tags

RSS Feed
  • V1.1.8 eacb218da8
    Compare

    v1.1.8 — The CPU stress no longer dies with your terminal Stable

    etwen released this 2026-09-06 17:31:37 +08:00 | 9 commits to main since this release

    ✨ New features

    mlucas now runs as a systemd unit, so it survives a lost session

    • The AMD CPU load is started as systemd-run --unit=mlucas-amm --property=Type=exec --property=Restart=always --property=RestartSec=2, instead of being backgrounded with & in the login shell. Script B and the thermal/safety macro (Script 4) both use it.
    • As a shell job it belonged to that one terminal: close Tera Term, drop the console, reconnect on a different session, and the load was gone — while jobs from the new session showed nothing to tell you. A multi-day soak could spend most of its length with an idle CPU and produce thermal numbers that looked fine because nothing was loading the part.
    • Restart=always brings it back if it exits on its own, and the log is appended (>>) inside the unit while being truncated (>) once before the unit starts, so a restart adds to the run rather than erasing it.
    • Script B now prints systemctl is-active mlucas-amm beside jobs, both in the one-shot check and in every pass of the monitor loop. One word — active — tells you the CPU is still loaded.

    The old & line is kept commented out directly above the new one, to fall back to if systemd-run is not available on a build.

    Script C stops the unit and brings its log home

    • systemctl stop mlucas-amm was added next to the existing kill $(jobs -p), and mlucas_amm_log is copied into /host/hw-eval/jobs/ with the other stress logs.
    • kill $(jobs -p) cannot reach a systemd unit, so without this the load would have run straight through the post-test snapshot and into the next test — every temperature and power reading taken at full load, with nothing in show interfaces status to reveal it.

    EN_timestamp — turn the per-line log timestamp on or off from config.ttl

    • Script A's logopen takes its 5th argument from the new flag: logopen filename 0 1 1 EN_timestamp. The argument order (<file> <binary> <append> <PlainText> <timestamp>) is now spelled out above the call.

    BMC_USB_RUNTIME — the BMC USB ping duration is a knob, not a constant

    • It was hard-coded to -w 14400 (4 hours), which no longer matched the soak lengths the SSD and USB knobs were being set to. The shipped default is 172800 (2 days).

    The shipped stress defaults are now one hour

    • SSD_RUNTIME and USB_RUNTIME go from 600 to 3600. v1.1.7 shipped a 10 minute stress by default.

    🐛 Bug fixes

    publish.sh produced a different bundle depending on whose machine it ran on

    • rsync copied whatever sat in src/Script_ABC_Blanton/, so a developer with the hammer/ mlucas binaries in their working tree shipped a ~100 MB zip while a fresh clone shipped ~200 KB. hammer/ is now excluded from the bundle and ignored by git.
    • publish.sh -h also printed the first lines of code along with the usage text, and would have truncated the usage block as the header grew. It now reads the header up to the first line of code.

    📦 Downloads

    File Contents
    Script_ABC_Blanton_V1.1.8.zip The full Tera Term working directory, including Blanton_Script/ to copy onto the DUT

    After copying to the DUT:

    chmod +x ~/Blanton_Script/*.sh      # see below
grep -rlU $'\r' ~/Blanton_Script    # expect no output
ls ~/hammer/tools/amd/mlucas-avx2   # must already be there - see below

    blanton_ber.sh, nfc_polling.sh, blanton_tr518.sh, blanton_multiphase_margin.sh, pwr_brick.sh and the two TH6_SWB*_power_readback.sh are invoked through ./ or ~/, so they need the execute bit along with bmc_monitor.sh and usb_target.sh — neither git nor a Windows/USB copy carries it reliably.

    ⚠️ Before you run

    • Replace config.ttl along with the macros. EN_timestamp and BMC_USB_RUNTIME are new, and Tera Term aborts the macro on an undefined variable rather than treating it as 0 — keeping an old config.ttl stops Script A at the logopen line.
    • hammer/ is not in the bundle. The ~99 MB of mlucas binaries comes with the DUT image, not from this repo. If ~/hammer/tools/amd/mlucas-avx2 is missing, Script B does not stop — it starts a unit that fails and is restarted every 2 seconds. Check for the file before you start.
    • The timestamp format is not in the macro. EN_timestamp only decides whether there is one; the format lives in Tera Term's Setup → Additional settings → Log, stored in that PC's TERATERM.INI. Two benches running the same macro can produce differently stamped logs.
    • The three stress durations are deliberately different: SSD and USB at 1 hour, the BMC USB ping at 2 days. Set each to match the soak you are actually running.
    • --runtime is the job's overall limit, not a per-pass one. qfx5252-stress-* stops after RUNTIME seconds whatever --passes says. For a 24 hour soak set RUNTIME to 86400.
    • mlucas-amm has not been run on hardware yet. The unit resolves ~ through bash's fallback to the passwd entry, because systemd does not set HOME for a system service without User=. It should land on /root/hammer, the same path the interactive shell uses — confirm it on the bench, or change both paths to an absolute /root/hammer/....
    • Script 4 uses the same unit but has no teardown. The thermal/safety macro now starts mlucas-amm the same way Script B does, and it still ends at while 1 — so stopping it means blanton_tr518.sh stop and systemctl stop mlucas-amm. Closing Tera Term does not stop the CPU load any more.
    • Script 5 (reboot cycle) is still unverified on hardware, still has no exit condition, and wait "Booting in blind mode" still has no timeout guard.
    • blanton_multiphase_margin.sh save is permanent, and must not be mixed with margin.sh — same rails, two access paths, no interlock.
    • READ_VIN and READ_IIN are still not in the ADPM12200 coefficient table.
    • The BMC USB service log only exists on the USB stick.
    • These three cannot share the switch: blanton_ber.sh, blanton_tr518.sh, blanton_traffic_linespeed.
    • FAN_SPEED is 100.
    • Still unverified from v1.1.0: the ce0 ingress mirror, the 120 s settle in blanton_tr518.sh, and test mode nr=no on stop.

    🔗 Links

    Full changelog: V1.1.7...V1.1.8

    Downloads