It kinda is though. Iirc it received an interrupt it shouldn’t have received and doesn’t know how to resolve. It is not supposed to ignore it, but then the only other option is crashing at this point. Basically it continues in a dazed and confused state.
Of course the message could be clearer, but at least it also makes the message easily searchable.
Easily searchable yes, easy to find an answer no. I have run into this on older, possibly failing, hardware. I would love it if the message pointed me toward subsystems to check or a large technical deep-dive.
I hate those messages. Just be class clear about the failure.
OTOH, keep up the good fight little computer.
The first 2 are exactly that. The third one is just a funny status update.
I recently had GCC give me the error “returning to the gate for a mechanical issue”, fun stuff as well
It kinda is though. Iirc it received an interrupt it shouldn’t have received and doesn’t know how to resolve. It is not supposed to ignore it, but then the only other option is crashing at this point. Basically it continues in a dazed and confused state.
Of course the message could be clearer, but at least it also makes the message easily searchable.
Easily searchable yes, easy to find an answer no. I have run into this on older, possibly failing, hardware. I would love it if the message pointed me toward subsystems to check or a large technical deep-dive.