2018 Retina Macbook Air - Sleep wake failure and Kernel panic issues

[moral-hazard]

I have a 2018 Macbook Air (i5 / 16Gb / Running Catalina); recently around the 3 year mark of ownership I'm getting a ton of these sleep wake failure issues (when I close the lid it just never starts up again) and more recently this kernel panic error. Both require a hard restart.

Is anyone aware of what might fix this? Have seen several threads online from owners with similar problems but no helpful resolutions. Thanks!

Sleep Wake failure in EFI

Failure code:: 0x01110600 0x0000001f

Please IGNORE the below stackshot

================================================================
Date/Time:        2021-10-28 07:35:55 -0700
OS Version:       ??? ??? (Build ???)
Architecture:     x86_64
Report Version:   29

Data Source:      Stackshots
Shared Cache:     0x8e73000 805527F1-FEEC-31FB-B02E-B6D73897F048

Event:            Sleep Wake Failure
Duration:         0.00s
Steps:            1

Boot args:        chunklist-security-epoch=0 -chunklist-no-rev2-dev chunklist-security-epoch=0 -chunklist-no-rev2-dev

Time Awake Since Boot: 25s



Process:          swd [322]
Architecture:     x86_64
Footprint:        392 KB
Start time:       2021-10-28 07:35:55 -0700
End time:         2021-10-28 07:35:55 -0700
Num samples:      1 (1)

  Thread 0x934    1 sample (1)    priority 2 (base 4)
  <thread QoS background (requested background), thread darwinbg, process darwinbg, IO tier 2>
  1  start + 1 (libdyld.dylib + 109769) [0x7fff70081cc9] 1
    1  ??? [0x1047bf454] 1
      1  ??? [0x1047bf1dd] 1
        1  __stack_snapshot_with_config + 10 (libsystem_kernel.dylib + 135862) [0x7fff701e32b6] 1
         *1  ??? [0xffffff80002c3206] 1
           *1  ??? [0xffffff8000983cd7] 1
             *1  ??? [0xffffff800089c7f1] 1
               *1  ??? [0xffffff80002e69e7] (running) 1

  Binary Images:
        0x7fff70067000 -     0x7fff7009dfff  libdyld.dylib (750.7)                <AB99C9EE-7127-3451-89AB-339F8F2CEE61>  /usr/lib/system/libdyld.dylib
        0x7fff701c2000 -     0x7fff701eefff  libsystem_kernel.dylib (6153.141.35) <FDF91BB8-B353-3B7F-8644-3BA7AFBC2309>  /usr/lib/system/libsystem_kernel.dylib
Model: MacBookAir8,1, BootROM 1554.140.20.0.0 (iBridge: 18.16.14759.0.1,0), 2 processors, Dual-Core Intel Core i5, 1.6 GHz, 16 GB, SMC
Graphics: kHW_IntelUHDGraphics617Item, Intel UHD Graphics 617, spdisplays_builtin
Memory Module: BANK 0/DIMM0, 8 GB, LPDDR3, 2133 MHz, 0x80AD, 0x483943434E4E4E4641474D4C4C522D4E5644
Memory Module: BANK 1/DIMM0, 8 GB, LPDDR3, 2133 MHz, 0x80AD, 0x483943434E4E4E4641474D4C4C522D4E5644
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x843), wl0: Oct 27 2020 17:15:52 version 9.30.357.42.32.5.43 FWID 01-b9d21b73
Bluetooth: Version 7.0.6f8, 3 services, 27 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
USB Device: USB 3.0 Bus
USB Device: Apple T2 Bus
USB Device: Apple Internal Keyboard / Trackpad
USB Device: Headset
USB Device: Ambient Light Sensor
USB Device: FaceTime HD Camera (Built-in)
USB Device: Apple T2 Controller
Thunderbolt Bus: MacBook Air, Apple Inc., 47.4

x86 global reset detected:

panic(cpu 0 caller 0xfffffff00a96e024): x86 global reset detected
Debugger message: panic
Memory ID: 0x6
OS release type: User
OS version: 19P548
macOS version: Not set
Kernel version: Darwin Kernel Version 21.1.0: Wed Oct 13 18:09:06 PDT 2021; root:xnu-8019.41.5~2/RELEASE_ARM64_T8010
Kernel UUID: 1E11E6BE-3CB3-3E5F-8079-1FD3E9135C30
iBoot version: iBoot-7429.41.4
secure boot?: YES
x86 EFI Boot State: 0xb
x86 System State: 0x0
x86 Power State: 0x0
x86 Shutdown Cause: 0xc5
x86 Previous Power Transitions: 0x70707060400
PCIeUp link state: 0x1614
Paniclog version: 13
Kernel slide:      0x00000000028e0000
Kernel text base:  0xfffffff0098e4000
mach_absolute_time: 0x13a2f2c9
Epoch Time:        sec       usec
  Boot    : 0x618d16ae 0x000a68fb
  Sleep   : 0x00000000 0x00000000
  Wake    : 0x00000000 0x00000000
  Calendar: 0x618d16b8 0x0006ba30

Zone info:
Foreign   : 0xfffffff07a1bc000 - 0xfffffff07a1cc000
Native    : 0xffffffe000068000 - 0xffffffe600068000
Readonly  : 0 - 0
Metadata  : 0xffffffeb00778000 - 0xffffffeb04964000
Bitmaps   : 0xffffffeb01f78000 - 0xffffffeb021f4000
CORE 0 is the one that panicked. Check the full backtrace for details.
CORE 1: PC=0xfffffff00a20643c, LR=0xfffffff00a206438, FP=0xffffffeb0f28be90
Panicked task 0xffffffe0f290c658: 0 pages, 200 threads: pid 0: kernel_task
Panicked thread: 0xffffffe0f2e02db0, backtrace: 0xffffffeb0f3eb670, tid: 372
          lr: 0xfffffff00a0cb388  fp: 0xffffffeb0f3eb6b0
          lr: 0xfffffff00a0cb118  fp: 0xffffffeb0f3eb720
          lr: 0xfffffff00a203eac  fp: 0xffffffeb0f3eb7a0
          lr: 0xfffffff00a20303c  fp: 0xffffffeb0f3eb850
          lr: 0xfffffff00a72d5fc  fp: 0xffffffeb0f3eb860
          lr: 0xfffffff00a0cae2c  fp: 0xffffffeb0f3ebbf0
          lr: 0xfffffff00a0cae2c  fp: 0xffffffeb0f3ebc50
          lr: 0xfffffff00b21f488  fp: 0xffffffeb0f3ebc70
          lr: 0xfffffff00a96e024  fp: 0xffffffeb0f3ebca0
          lr: 0xfffffff00a95af5c  fp: 0xffffffeb0f3ebd00
          lr: 0xfffffff00a961410  fp: 0xffffffeb0f3ebd50
          lr: 0xfffffff00a95ce48  fp: 0xffffffeb0f3ebdf0
          lr: 0xfffffff00a95a640  fp: 0xffffffeb0f3ebe70
          lr: 0xfffffff00a80cdb4  fp: 0xffffffeb0f3ebea0
          lr: 0xfffffff00a6733a4  fp: 0xffffffeb0f3ebee0
          lr: 0xfffffff00a672bb4  fp: 0xffffffeb0f3ebf20
          lr: 0xfffffff00a7385a0  fp: 0x0000000000000000

 

[Ray2]

Probably won't make you feel any better. I had these with my 2018 mini. Every boot under Mojave. Sleep was a disaster so I set the mini to never sleep. I was also getting frequent disks improperly ejected messages even though no externals had been ejected. Crash logs similar to yours. Catalina was better but still problematic. Never went beyond Catalina.

I took it down to my local Apple store 4, maybe 5, times. Copies of screenshots in hand. Apple was basically intransigent until I finally started bitching about wanting a full refund. Finally replaced the motherboard and all was well including the improper ejection messages. Also was fine under Mojave which I rolled back to. Seems to be hardware and when its all soldered together it only reduces cost (and increases executive comp) when it works or, it doesn't work but doesn't get fixed.

Having been a customer for over 35 years, a supplier to Apple and a corporate buyer, this one caused me enough grief that I have a different view of Apple “support” these days. The mini has been relegated to a storage cube to be used as a trade-in for a purchase I seem to have difficulty making.

 

[moral-hazard]

Probably won't make you feel any better. I had these with my 2018 mini. Every boot under Mojave. Sleep was a disaster so I set the mini to never sleep. I was also getting frequent disks improperly ejected messages even though no externals had been ejected. Crash logs similar to yours. Catalina was better but still problematic. Never went beyond Catalina.

I took it down to my local Apple store 4, maybe 5, times. Copies of screenshots in hand. Apple was basically intransigent until I finally started bitching about wanting a full refund. Finally replaced the motherboard and all was well including the improper ejection messages. Also was fine under Mojave which I rolled back to. Seems to be hardware and when its all soldered together it only reduces cost (and increases executive comp) when it works or, it doesn't work but doesn't get fixed.

Having been a customer for over 35 years, a supplier to Apple and a corporate buyer, this one caused me enough grief that I have a different view of Apple “support” these days. The mini has been relegated to a storage cube to be used as a trade-in for a purchase I seem to have difficulty making.

thank you! did they replace this even outside the standard warranty? i'm long out of warranty at this point.
Ordered a new 14" pro but would like to get the air fixed if possible.

 

[Ray2]

It was within Applecare coverage. But again, twice they took the machine in and handed it back with nothing but a reinstall. That was their “solution”. So so much for the value of warranty coverage. Basically, if its been doing this since day one and you can document it (I could), its time to raise your voice level, irrespective of its warranty status. It strikes me they have a problem with T2 Macs that they don't want to deal with. You and I are not the only ones with this issue. The good side, at least with mine and others I've read about, was after it had its brief tantrum, it always worked fine and I never lost a bit of data. My GF has the same machine you have, runs Mojave, perfect. Its hardware. Soldering it all together has its pitfalls when it comes to repair. So they hope we go away.

 

[GreyM]

Yes. Similar issue. Resetting SMC and NVRAM will not help. Reinstalling the OS does not help. Eliminating all 3rd party software and apps does not help. Nothing helps.

The problem with sleep/wake functions was a sudden problem 100% due to Monterey OS for me. All other OS upgrades have been reliable over the lifetime of this computer.

I can no longer wake my computer if the lid is shut for more than 60 seconds (I timed it). This triggers a kernel panic. A restart is now always required if I shut my lid.

Additional issue: If the screensaver stays on too long the sleep/standby function also kicks in and shuts down the computer such that a complete restart is necessary.

Per your observation, the shutdown does not allow for a consistent restart without holding the power button for variable lengths of time, multiple times. Key strokes will not wake it up. It eventually restarts, but not predictably.

Changing various PMSET codes (standby, hibernate, sleep, etc.) did not resolve the problem for me.

I contacted Apple IT support. IT completed a full erase, OS Monterey re-installation and file reinstallation from icloud. This took an entire day. Unfortunately, the issue persisted.

Bottom line: There is no resolution at this time. Will need to wait for the next OS update. In the meantime I can't shut my computer lid without a full restart.

I've a adapted to the problem by:

1. Completing a shutdown every time you are done your work.
2. When I open the lid after a commanded shutdown an automatic restart is detected.
3. Bluetooth does not allow for my apple watch to restart the computer; admin PWD is always required at restart.

NOTE: An automatic restart is NOT detected if the computer shuts itself down through standby or sleep modes, which requires a hard reboot (using the power button, and which is not reliable).

Model Identifier: MacBookPro16,1
Processor Name: 8-Core Intel Core i9
Processor Speed: 2.4 GHz

 

[moral-hazard]

Closing the loop on this one. It was time for me to upgrade my Mac anyway and my new M1 pro machine arrived, so I wiped it, reinstalled, and did the apple trade-in program and returned the old MacBook Air to apple. I am unclear if the reinstall fixed the issue or not, but they paid the full quoted price for a good condition working machine. I'd recommend this route for anyone like me who has this issue (a) doesn't have time to battle apple and (b) doesn't have applecare.

 

[GreyM]

Yeah, I hear you. I just installed the new update but the problems continue. I think that's going to be my solution. My glimmer of hope just disappeared.

 

[GreyM]

IMPORTANT NEWS! Software Update 12.2.1 (21D62) was released on February 10. I downloaded it yesterday. It has fully resolved the sleep/crash problems I've had since installing Monterey OS. What a relief!