Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
M1 Mac SOCD report detected: (AP watchdog expired)
- Thread starter sunny5
- Start date
- Sort by reaction score
I've also seen it twice, but only recently, and since updating this M1 Mac mini to Big Sur 11.5.2. At the time I figured it was related to me leaving it on for 4+ days in a row. Either way, before a few weeks ago, not a single problem on this eight-month-old machine. I updated to 11.6, and all's been well, though I don't think I've left the Mac on for several days yet.
I have three USB 3.0 hubs on the USB-A ports, all powered, often low traffic. I connect a WD easystore 8TB HDD every Sunday night for Time Machine, then disconnect it when that's done. The reboots did not happen while it was mounted. Time Machine also reaches out to my Unraid NAS three times a week for backups (via TimeMachineEditor). Aside from that, the only external storage I always have mounted are an Unraid share for my iTunes library and a Blackmagic MultiDock 10G (on a USB-C port) with one Samsung and two SanDisk SSDs inside.
I have three USB 3.0 hubs on the USB-A ports, all powered, often low traffic. I connect a WD easystore 8TB HDD every Sunday night for Time Machine, then disconnect it when that's done. The reboots did not happen while it was mounted. Time Machine also reaches out to my Unraid NAS three times a week for backups (via TimeMachineEditor). Aside from that, the only external storage I always have mounted are an Unraid share for my iTunes library and a Blackmagic MultiDock 10G (on a USB-C port) with one Samsung and two SanDisk SSDs inside.
I also have a hub that periodically disconnects memory attached to it, and sometimes doesn't recognize memory added to it.
I just had this error for (I think) the first time. I've been running this M1 iMac with very few if any issues for a few months now and just today it spontaneously restarted while I was sitting here at my desk not using it. The article linked earlier said:
... and I have #1 and #3 in my setup.
Hoping there's some resolution here because spontaneous unexplained restarts are incredibly disruptive!
... and I have #1 and #3 in my setup.
Hoping there's some resolution here because spontaneous unexplained restarts are incredibly disruptive!
I wish I had bought a Thunderbolt hub. But I had ordered my iMac and knew I needed a hub, and I didn't have any Thunderbolt accessories. Thunderbolt hubs are significantly more expensive. Sometimes when I get the window saying my drive has been disconnected, I can still see it in finder. Sometimes I can unplug it & plug it in to see it. Sometimes I need to reboot to see it.
I've also had my iMac shut down once with a kernel panic.
I've also had my iMac shut down once with a kernel panic.
That's because you disconnected a drive before un-mounting plug in drives without un-mounting the drive from being used by a system connection! you'd switchers don't seem to understand in unix world you must mount and un-mount external drives all the time and in. OS X and even in the older PPC days of Mac Classic did that too!
I've had it disconnect while I'm away from my apartment. I'm not touching the drive nor the hub when it disconnects.
That said, just because Unix was designed to not safely allow devices to be disconnected doesn't mean Apple shouldn't fix that issue.
I just had it today for the first time with mac os 11.6, company computer (which don't allow me install any software).
Running on battery and having a microsoft teams meeting, I just got a reboot with the same error.
I have no idea why it happened while I was doing nothing but just an online meeting.
Running on battery and having a microsoft teams meeting, I just got a reboot with the same error.
I have no idea why it happened while I was doing nothing but just an online meeting.
I've encountered this error two times total; once shortly after getting my Apple Silicon M1 Mini (where it also exhibited the green flickering effect, alongside the onboard speakers making a popping noise beforehand), and once just a few minutes ago. Both times were using the same monitor (one of two I have depending on location), and afaik both occurred when a USB-C device of some sort was connected via a USB-A to USB-C cable, though in the latter case, the device was connected through an externally powered USB-A port dock, and was not sending data over the line (was only using the port to charge).
FYI for anyone who has this issue: yes, this is a Kernel Panic! The OS put multiple log files related to the crash in
Furthermore, according to this post on the Apple Support Fourms, the USB-A 3.0/2.1 dock I'm using may be at fault for the panic. If I had to guess, some part of however Apple Silicon chips handle USB 2.1 connections is faulty, and having both USB 3.0 and USB 2.1 connections going though the same USB-A port on the SOC caused a problem? This is just a guess, though. (As a note, the USB dock is a SABRENT HB-UMP3 dock, and I couldn't find any firmware updates for it on the manufacturer's website.)
FYI for anyone who has this issue: yes, this is a Kernel Panic! The OS put multiple log files related to the crash in
/Library/Logs (the global Library folder, not the userspace one), which were... not very helpful, but do confirm that the crash was a kernel panic, at least?Furthermore, according to this post on the Apple Support Fourms, the USB-A 3.0/2.1 dock I'm using may be at fault for the panic. If I had to guess, some part of however Apple Silicon chips handle USB 2.1 connections is faulty, and having both USB 3.0 and USB 2.1 connections going though the same USB-A port on the SOC caused a problem? This is just a guess, though. (As a note, the USB dock is a SABRENT HB-UMP3 dock, and I couldn't find any firmware updates for it on the manufacturer's website.)
happend to me today also for 1st time.
No HDD connected, only my mouse receiver , monitor on HDMI.
it's strange?
No HDD connected, only my mouse receiver , monitor on HDMI.
it's strange?
Happened to me, for the first time in a year, mb air M1 8gb, it works 24/24 7/7 as server (4 cam securityspy and plex, satechi usb3/ethernet and wd mybook), I suppose that Big Sur 11.6 has something to do with that.
Right, absolutely no rush, although a little strange I will monitor it and see (seems to me some firmware issue, monterey will update it)... for me is easy to see if the problem becomes worse because the air is (supposed to be) always on. If needed I will try first a full reinstall or, at worse, an ipsw recovery.
Thank you! now i'm relaxed!
hopefully it's something that new SW update can fix it (MacOS 12)
and it's not hw thing.
I always get this error together with a forced automatic reboot of our Mac Mini M1 (8GB/256GB) when I have the HiDPI 2560x1440 setting activated (the "More space" choice in the monitor preference pane).
The scaling to achieve said resolution via internal doubling to 5170x2880 and then downscaling seems to be memory starved or prone to bug(s).
When I have the "Standard for this display" setting activated (HiDPI 1920x1080) or the native resolution of the display - in our case that is 4K (3840x2160 pixels), nothing happens and the machine runs more or less infinitely 24/7.
The scaling to achieve said resolution via internal doubling to 5170x2880 and then downscaling seems to be memory starved or prone to bug(s).
When I have the "Standard for this display" setting activated (HiDPI 1920x1080) or the native resolution of the display - in our case that is 4K (3840x2160 pixels), nothing happens and the machine runs more or less infinitely 24/7.
Last edited:
The error is still present in the betas. Someone says apple replaced the logic board. But then had the problem again. So really, who knows
More and more report only a logic board replacement fixes this. Not looking good
I suffered through my first run-in with the AP watchdog expired followed by an immediate involuntary reboot. We took delivery of our 24-inch, M1, 2021, 16GB/1TB in mid-July. Aside from some display resolution issues, we have had nothing but a good time. Until today, that is. I will continue to monitor and update if this continues to occur.
With a M1 Pro/Max? Wow
No one is really sure if the problem is hardware or software at the moment
Ok. My current theory is that this occurs when connected to a USB-C PD device that does not fully comply with the USB-C PD spec. Occasionally, these devices may be sending weird power signals to the Mac disrupting sleep/wake cycles in unexpected ways leading to the issue. I cannot reproduce the SOCD report error at this time.
There is a long thread about Dell U3818W and U3419W monitors not following the spec as advertised leading to the sleep/wake power signal issue arising on Macs. The response from Dell on the matter is laughable.