Power off on 15.2

[schmalgausen]

Hi,

I switch off my power socket at the end of working day and got 50/50 correct sleep or hard power off (with system message "REBOOTED? WHY???") in the morning. I got it after update to MacOS 15, it was correct on MacOS 14. Battery is near full and no reason to power off. PMSET to default didn't help. MacBook Pro 16" 2019, hibernatemode is 3.

Any ideas?

 

[Bigwaff]

Hi,

I switch off my power socket at the end of working day and got 50/50 correct sleep or hard power off (with system message "REBOOTED? WHY???") in the morning. I got it after update to MacOS 15, it was correct on MacOS 14. Battery is near full and no reason to power off. PMSET to default didn't help. MacBook Pro 16" 2019, hibernatemode is 3.

Any ideas?

What is "50/50 correct sleep or hard power off" ? Sounds like your MBP is having a kernel panic. Have you tried not switching off the power socket?

 

[ThrowerGB]

If you want to turn the machine off, do a shutdown, not just cutting of power. The system has to do some cleanup stuff when it's turned off. Switching off at the wall socket prevents the clean shutdown and will eventually cause problems. When you turn the power back on, and if you have the Setting to restart after a power failure turned on, you'll probably see the notifications to that effect. In macOS 15, Apple seems to have added a lot of notifications which might be why you hadn't seen that before.
Years ago, shutting own at night was potentially more harm than good because the sudden application of power and the sudden demand for power by all that needs to happen at startup stresses the hardware. I remember from maybe 15-20 years ago the el-techs where I worked demanded shutdowns at the end of each day to save power. and not stress the A/C next morning in summer when the A/C was. timed to start up. Then a few years later, they reversed and required everyone to leave machines turned on at night so they could distribute software updates. Apple mitigates the dilemma by allowing things like programmed low power, lock screen, sleep modes, wake for network access, sleep after a period of inaction, etc.

 

[Honza1]

Hi,

I switch off my power socket at the end of working day and got 50/50 correct sleep or hard power off (with system message "REBOOTED? WHY???") in the morning. I got it after update to MacOS 15, it was correct on MacOS 14. Battery is near full and no reason to power off. PMSET to default didn't help. MacBook Pro 16" 2019, hibernatemode is 3.

Any ideas?

Not normal or usual - not related to power settings.
Try unplugging the MBP instead of powering down socket. If the power supply does something weird during loss of power, it can cause kernel issues to MBP, potentially even destroy the computer. I had something burn my charging chip on 2017 MBP which required replacement of mainboard. Suspect it might have been some power supply issue as I have few times plugged the power supply in mains power and there was spark when plugging in. Suspicious - looking after the fact on it. Threw the power supply out.
Simply unplugging USB-C from the computer before switching off the power to the power supply might be gentler.

Or try using different power supply...

 

[schmalgausen]

What is "50/50 correct sleep or hard power off" ? Sounds like your MBP is having a kernel panic. Have you tried not switching off the power socket?

After sleep I have fast wake up with fingertip login, it is usual and preferable scensrio, battery is 70-80% or so. After power off I have cold boot with password login and message about unexpectable reboot, battery is 99%.

I've tried not switching off but I can't do it everyday bacause of another equipment connected with the same pilot.

 

[gonpostal]

If you want to turn the machine off, do a shutdown, not just cutting of power. The system has to do some cleanup stuff when it's turned off. Switching off at the wall socket prevents the clean shutdown and will eventually cause problems. When you turn the power back on, and if you have the Setting to restart after a power failure turned on, you'll probably see the notifications to that effect. In macOS 15, Apple seems to have added a lot of notifications which might be why you hadn't seen that before.
Years ago, shutting own at night was potentially more harm than good because the sudden application of power and the sudden demand for power by all that needs to happen at startup stresses the hardware. I remember from maybe 15-20 years ago the el-techs where I worked demanded shutdowns at the end of each day to save power. and not stress the A/C next morning in summer when the A/C was. timed to start up. Then a few years later, they reversed and required everyone to leave machines turned on at night so they could distribute software updates. Apple mitigates the dilemma by allowing things like programmed low power, lock screen, sleep modes, wake for network access, sleep after a period of inaction, etc.

I’m having a similar issue since upgrading to 15. Only, mine happens when I disconnect the USB-C charger. All power is completely lost, and very difficult to start back up; in fact I thought it was a goner. I was able to get it to boot up, then properly shut down, and did a SMC RESET. Unfortunately this did not solve the problem, which still exists. 2018 intel I-5 2.3ghz, touchbar. Also, I’ve tried 3 times to update to 15.2 and even though it claims to have been successful, it still wants to do a software update in its entirety.

 

[schmalgausen]

I applied SMC and NVRAM reset and maybe it helped, not sure.

As for update from 15 to 15.2 I heard same story from my colleague. As for me I did clean OS reinstall.

 

[schmalgausen]

Many OS updates were applied but still have the same issue. And yes, it is kernel panic. I have no devices connected to the laptop, only charger and 3.5 cable.

 

[Bigwaff]

Many OS updates were applied but still have the same issue. And yes, it is kernel panic. I have no devices connected to the laptop, only charger and 3.5 cable.

I’m a little confused. Your initial post says the problem is with 2019 Intel MBP, but this kernel panic screenshot is from an Apple Silicon Mac.

 

[schmalgausen]

Maybe they have common modules for power?

 

[Bigwaff]

No. The kernel panic screenshot literally has Darwin ARM64 and iBoot version. And now your latest screenshots literally have iBridge version info. Why you troll, man?

 

[schmalgausen]

Sorry, I don't have another Mac. All screenshot are from mine. I think this week I will catch another one.

 

[schmalgausen]

Just found a log in System Info app the same RELEASE_ARM64_T8010:



Panic (system crashes) log:





Source: /Library/Logs/DiagnosticReports/.contents.panic


Size: 3 KB (2 904 bytes)


Last Modified: 17.03.25, 09:00


Recent Contents: {"files_to_attach":["\/Library\/Logs\/DiagnosticReports\/ProxiedDevice-Bridge\/panic-full-2025-03-15-120803.0003.ips"],"component_id":"923030","log_path":"\/Library\/Logs\/DiagnosticReports\/ProxiedDevice-Bridge\/panic-full-2025-03-15-120803.0003.ips","panic_string":"panic(cpu 0 caller 0xfffffff02315e4a0): Sleep\/Wake hang detected @IOPMrootDomain.cpp:12937\nDebugger message: panic\nMemory ID: 0x6\nOS release type: User\nOS version: 22P3060\nmacOS version: 24D81\nKernel version: Darwin Kernel Version 24.3.0: Thu Jan 2 20:06:28 PST 2025; root:xnu-11215.81.4~2\/RELEASE_ARM64_T8010\nKernelCache UUID: 3BB39ACE95BF51BF1B31787925CD59D2\nKernel UUID: 5E0311EE-A5B2-37BF-A7AE-F303066BB6B6\nBoot session UUID: FE0C0B95-5F1F-4230-B99A-DD0F05F41EF4\niBoot version: iBoot-11881.81.2\nsecure boot?: YES\nroots installed: 0\nx86 EFI Boot State: 0xd\nx86 System State: 0x2\nx86 Power State: 0x5\nx86 Shutdown Cause: 0x5\nx86 Previous Power Transitions: 0x50400030405\nPCIeUp link state: not available\nmacOS kernel slide: 0x1ca00000\nPaniclog version: 14\nKernel slide: 0x000000001b944000\nKernel text base: 0xfffffff022948000\nmach_absolute_time: 0x418b246b31e\nEpoch Time: sec usec\n Boot : 0x67d2746b 0x0008122e\n Sleep : 0x67d56d6d 0x0002e8b5\n Wake : 0x67d56d6d 0x0008b2f0\n Calendar: 0x67d56d97 0x000d3e86\n\nZone info:\n Zone map: 0xffffffdc090ac000 - 0xffffffe2090ac000\n . VM : 0xffffffdc090ac000 - 0xffffffdcef710000\n . RO : 0xffffffdcef710000 - 0xffffffdd3c3dc000\n . GEN0 : 0xffffffdd3c3dc000 - 0xffffffde22a40000\n . GEN1 : 0xffffffde22a40000 - 0xffffffdf090a4000\n . GEN2 : 0xffffffdf090a4000 - 0xffffffdfef70c000\n . GEN3 : 0xffffffdfef70c000 - 0xffffffe0d5d74000\n . DATA : 0xffffffe0d5d74000 - 0xffffffe2090ac000\n Metadata: 0xffffffeff86d4000 - 0xffffffeff9ed4000\n Bitmaps : 0xffffffeff9ed4000 - 0xffffffeff9ff0000\n Extra : 0 - 0\n\nTPIDRx_ELy = {1: 0xffffffdf095feb90 0: 0x0000000000000000 0ro: 0x0000000000000000 }\nCORE 0 is the one that panicked. Check the full backtrace for details.\nCORE 1: PC=0xfffffff022c92a64, LR=0xfffffff022c92a60, FP=0xffffffefe8e5fe60\nCompressor Info: 0% of compressed pages limit (OK) and 0% of segments limit (OK) with 0 swapfiles and OK swap space\nPanicked task 0xffffffdf08f13780: 0 pages, 237 threads: pid 0: kernel_task\nPanicked thread: 0xffffffdf095feb90, backtrace: 0xffffffefe8c73820, tid: 1246792\n\t\t lr: 0xfffffff022b56020 fp: 0xffffffefe8c73890\n\t\t lr: 0xfffffff022c908fc fp: 0xffffffefe8c73900\n\t\t lr: 0xfffffff022c8f9f0 fp: 0xffffffefe8c739f0\n\t\t lr: 0xfffffff022b156bc fp: 0xffffffefe8c73a00\n\t\t lr: 0xfffffff022b55a60 fp: 0xffffffefe8c73dd0\n\t\t lr: 0xfffffff0232453a0 fp: 0xffffffefe8c73df0\n\t\t lr: 0xfffffff02315e4a0 fp: 0xffffffefe8c73e30\n\t\t lr: 0xfffffff022bb1980 fp: 0xffffffefe8c73f20\n\t\t lr: 0xfffffff022b206c4 fp: 0x0000000000000000\n\n"}

 

[schmalgausen]

The same event today.