Re: [PATCH v6 5/6] alpha: decode Clipper environmental events and retain console logs

[Matt Turner]

> +     if (header->code != 0x206 ||
> +         clipper_process_environment(header, 0) != MCHK_DISPOSITION_DISMISS) {

clipper_process_environment() returns MCHK_DISPOSITION_REPORT for any
valid frame and UNKNOWN_ERROR for a truncated one. It never returns
DISMISS, so this condition is always true. The silent first pass can
go, and the body can lose a level of indentation.

> +     status |= CLIPPER_BITS(CLIPPER_EnvQW1SMIR, frame->smir, 0x15);

Your cover letter says SMIR bit 0 stayed set in all three reports,
including the one after the supply was reconnected and its own failure
bit had cleared. With this mask that last report prints "System Power
Supply failure detected" for a recovery. Bit 0 looks latched, or
inverted like the halt and reset bits. I would treat it as raw context
(mask 0x14) until we know. Could you post the dmesg from that test?

> +             if (packet->type == EL_TYPE__REGATTA__PROCESSOR_ERROR_FRAME ||

Minor: Titan prints by_type.regatta_frame.cpuid for these. It would be
useful here as well.