Unclear why there is a 1 second timeout at all.

Presumably the patch for that will be to make it an infinity timeout.

system management mode does a lot of stuff, some of which is time critical. If your system is overheating and one of the cores is stuck off in the weeds, it's probably better to get on with the thermal response rather than waiting forever.

Also, the System Management Interrupts are supposed to return to normal processing in some finite timespan; a timeout bounds the wait time.

▲

quotemstr 18 minutes ago | parent | next [-]

It could also react to hitting the timeout with a hard reset. Annoying perhaps, but at least safe. Ancient principle of system design is that when you must fail, it is better to fail safe than fail deadly even when it's annoying in the short term.

▲

PunchyHamster an hour ago | parent | prev [-]

If it is critical it should not be running on same cores

	▲	Geezus_42 39 minutes ago \| parent [-]
		Using the example above, if a CPU core is overheating, can you down clock that core using and instruction run on another core? I don't actually know that much about how the hardware actually works at that level, so I am genuinely asking.

▲

xxpor 4 hours ago | parent | prev | next [-]

Can this be patched? Is there a chance it's a hw watchdog that you can't fix in microcode?

▲

ramses0 3 hours ago | parent | prev [-]

Looks like it's ~4 billion (2^32) crossover counter?