We attempted to run a burn-in test while connected to our MacBook Pro M4 Max, but this crashed about 10 minutes into testing.

We attempted to run a burn-in test while connected to our MacBook Pro M4 Max, but this crashed about 10 minutes into testing. We tried to run a 2-hour burn-in on the M4 Max host while charging the battery from below 5%, running six bus-powered drives (via ATTO/Black Magic/IOmeter), hitting the RJ45 port for 2.5Gbps (via JPerf), and streaming at least 4K60Hz video content to two displays; however, the M4 Max crashed in 20minutes.

If you haven't already, please file a bug on this and post the bug number back here. In the bug, please attach full panic logs as well as a sysdiagnose from the machine that panic-ed.

One comment on the log picture you posted. That particular panic message ("Halt/Restart Timed Out") comes from a very specific point, which you can actually see here:

xnu/iokit/Kernel/IOPlatformExpert.cpp:
...
IOShutdownNotificationsTimedOut(
	thread_call_param_t p0,
	thread_call_param_t p1)
{
#if !defined(__x86_64__)
	/* 30 seconds has elapsed - panic */
	panic("Halt/Restart Timed Out");
...

Critically, that can't really happen on a "normally" running machine. The "shutdown" here isn't simply "the user selecting shutdown" but is actually happening much later in the shutdown process as the kernel itself is preparing for final power off. This is either a different panic or something else actually initiated this process.

__
Kevin Elliott
DTS Engineer, CoreOS/Hardware

We update OS to 26.2 this week and the M4 max crashed issue has been gone. May we know is there any fixed solution phoased in to the new OS version ?

Many thanks for your supporting.

cheers, carrie

We update OS to 26.2 this week, and the M4 max crashed issue has been gone. May we know if there is any fixed solution phased into the new OS version?

There isn't really any way to answer that with the information you've provided. There are too many changes in any given release to easily review, and it's often the case that the change that resolves a given issue wasn't actually specific to that particular issue. If you upload the panic log to a bug and post the bug number back here, I might be able to say more, but without that, I can't really determine anything.

__
Kevin Elliott
DTS Engineer, CoreOS/Hardware