Panic message on Mac Studio after sleep mode

Question

Level 1

5 points

Panic message on Mac Studio after sleep mode

Hi, I have a mac studio with M1 Max often I have this message of panic: "panic (cpu 0 caller 0xfffffefefefefefefefefefe0025f2bd20): ioscsitargetdevice :: setpoWerstate (0xfffffefeffeFe2804d1c2f0: 0xfffffefefefefefeFe0027d0bd04, 1 -> 0) Timed Out After 101351 ms @ioservicepm.cppm: 5 604"

The MAC HW diagnostics (CMD+D) does not find any problems, however, often when it goes into standby (sleep mode) I find it restarted with the above message. Anyone having the same problem as me? and did you solve it? Greetings thanks

Mac Studio

Posted on Aug 12, 2023 9:37 AM

Reply

Answer 1

Tesserax

Level 10

160,224 points

Aug 12, 2023 9:56 AM in response to mausaba

There are, at least, three common reasons for a kernel panic:

hardware/firmware failure or error
kernel extensions
a conflict with a peripheral

I see that you have already run Diagnostics, but did you do so with only essential peripherals (keyboard, mouse, & display) attached? Should the panic be caused by a peripheral, like a USB hub, you can verify this by not having it connected and the panics no longer occur.

... and when you ran Diagnostics, did you do so from booting up your Mac in Diagnostics Mode, i.e., pressing and holding down the power button until the display shows Loading Startup Options. Then holding down the Command & D keys until the Mac restarts with the Diagnostics Loader menu?

Is your Mac running in "Full Security" or "Reduced Security" mode?

To further troubleshoot this panic, we would need a bit more information from the Mac's diagnostics logs.

Reply

Answer 2

Tesserax

Level 10

160,224 points

Aug 12, 2023 1:46 PM in response to mausaba

Ok, with a successful run of Diagnostics with the peripherals removed, would indicate that there doesn't appear to be anything amiss with either your Mac's hardware or firmware ... unless the panics return in this configuration.

How long did you use your Mac, w/o the additional peripherals, to see if the panics re-occur? 24hrs, 48hrs, or longer? I would run it for at least 24hrs to be sure. Once that period has ended, I would re-attach those peripherals to see if the panics come back. Again 24hrs should be sufficient. I'm just trying to eliminate any hardware-related issues ... whether with your Mac or with any of the peripherals that you use with it.

Then moving on to kernel extensions. Again, are you running your Mac in "Full Security" or "Reduced Security" mode? The latter would allow you to use 3rd-party kernel extensions with your Mac. I would expect any being used would appear in the kext list in the report. You limited the amount shown, but third party ones typically appear early in the list, so I have to guess that your Mac is running in Full Security mode.

Lastly, looking at the part of the report the panic was initiated by CPU core 0, and looks like it is indicating that there is an issue with the Mac sleeping or awakening from sleep. This, unfortunately, is not as rare as we would like. One thing to test, is to temporarily disabling sleep mode altogether. Then use your Mac for a few days to see if the panics stop.

One last thing. How many recent panics have been recorded, especially related to your Mac sleeping/waking from sleep, over the last 30 days? If just this one, then this may not be a issue. However, if there are a number of them, this would need to be further investigated to find the cause.

Reply

Answer 3

Tesserax

Level 10

160,224 points

Aug 15, 2023 8:51 AM in response to mausaba

Ok, when I get a chance I will review the report. For future reference, use the "Additional Text" tool (looks like a single page of paper) from the ASC editor's tool bar to include these reports ... instead of spreading across multiple replies.

With a quick look, it appears to be an issue with Sleep Mode. I suggest that you completely disable it and see if the panics continue.

Reply

Answer 4

mausaba Author

Level 1

5 points

Aug 12, 2023 11:13 AM in response to Tesserax

Yes, I ran the diagnostic by turning on my MAC and holding down the power button, when Loading startup option appeared I pressed and holding down the Command & D keys until the Diagnostic Loader menu appeared. Before executing it I removed all the peripherals and then I re-executed it with the connected peripherals but the diagnostic result hasn't changed: "APD000".

This is complete Log:

panic(cpu 0 caller 0xfffffe0025f2bd20): IOSCSITargetDevice::setPowerState(0xfffffe2804d1c2f0 : 0xfffffe0027d0bd04, 1 -> 0) timed out after 101351 ms @IOServicePM.cpp:5604

Debugger message: panic

Memory ID: 0x6

OS release type: User

OS version: 22G74

Kernel version: Darwin Kernel Version 22.6.0: Wed Jul 5 22:22:05 PDT 2023; root:xnu-8796.141.3~6/RELEASE_ARM64_T6000

Fileset Kernelcache UUID: 2B1987A4F4C4DBE41241F23B69A1D0AD

Kernel UUID: E88B0B04-7B4D-3E52-8980-A19ED82304F7

Boot session UUID: 5BA55905-B797-4F51-A2D8-F0B8B86BB1FB

iBoot version: iBoot-8422.141.2

secure boot?: YES

roots installed: 0

Paniclog version: 14

KernelCache slide: 0x000000001d488000

KernelCache base: 0xfffffe002448c000

Kernel slide: 0x000000001d490000

Kernel text base: 0xfffffe0024494000

Kernel text exec slide: 0x000000001e868000

Kernel text exec base: 0xfffffe002586c000

mach_absolute_time: 0x4bfccc8d6

Epoch Time: sec usec

Boot : 0x64d79f9b 0x0000dcc6

Sleep : 0x64d7a250 0x00072eaa

Wake : 0x64d7a250 0x000e4dc2

Calendar: 0x64d7a2e7 0x0000f063

Zone info:

Zone map: 0xfffffe1803eec000 - 0xfffffe3803eec000

. VM : 0xfffffe1803eec000 - 0xfffffe1cd0bb8000

. RO : 0xfffffe1cd0bb8000 - 0xfffffe1e6a550000

. GEN0 : 0xfffffe1e6a550000 - 0xfffffe233721c000

. GEN1 : 0xfffffe233721c000 - 0xfffffe2803ee8000

. GEN2 : 0xfffffe2803ee8000 - 0xfffffe2cd0bb4000

. GEN3 : 0xfffffe2cd0bb4000 - 0xfffffe319d880000

. DATA : 0xfffffe319d880000 - 0xfffffe3803eec000

Metadata: 0xfffffe5fce868000 - 0xfffffe5fd6868000

Bitmaps : 0xfffffe5fd6868000 - 0xfffffe5fe25ac000

Extra : 0 - 0

TPIDRx_ELy = {1: 0xfffffe2335481828 0: 0x0000000000000000 0ro: 0x0000000000000000 }

CORE 0 PVH locks held: None

CORE 1 PVH locks held: None

CORE 2 PVH locks held: None

CORE 3 PVH locks held: None

CORE 4 PVH locks held: None

CORE 5 PVH locks held: None

CORE 6 PVH locks held: None

CORE 7 PVH locks held: None

CORE 8 PVH locks held: None

CORE 9 PVH locks held: None

CORE 0 is the one that panicked. Check the full backtrace for details.

CORE 1: PC=0xfffffe00258fa308, LR=0xfffffe00258fa308, FP=0xfffffe8818e83ef0

CORE 2: PC=0xfffffe00258fa308, LR=0xfffffe00258fa308, FP=0xfffffe8818ed7ef0

CORE 3: PC=0xfffffe00258fa308, LR=0xfffffe00258fa308, FP=0xfffffe881941bef0

CORE 4: PC=0xfffffe00258fa308, LR=0xfffffe00258fa308, FP=0xfffffe88178abef0

CORE 5: PC=0xfffffe00258fa308, LR=0xfffffe00258fa308, FP=0xfffffe8818cf7ef0

CORE 6: PC=0xfffffe00258fa308, LR=0xfffffe00258fa308, FP=0xfffffe88193c7ef0

CORE 7: PC=0xfffffe00258fa308, LR=0xfffffe00258fa308, FP=0xfffffe881826bef0

CORE 8: PC=0xfffffe00258fa308, LR=0xfffffe00258fa308, FP=0xfffffe88191ffef0

CORE 9: PC=0xfffffe00258fa308, LR=0xfffffe00258fa308, FP=0xfffffe881781bef0

Compressor Info: 0% of compressed pages limit (OK) and 0% of segments limit (OK) with 0 swapfiles and OK swap space

Panicked task 0xfffffe2803d9e738: 0 pages, 642 threads: pid 0: kernel_task

Panicked thread: 0xfffffe2335481828, backtrace: 0xfffffe8818d03720, tid: 16639

lr: 0xfffffe00258c2620 fp: 0xfffffe8818d037a0

lr: 0xfffffe0025a03338 fp: 0xfffffe8818d037c0

lr: 0xfffffe00259f45a4 fp: 0xfffffe8818d03830

lr: 0xfffffe00259f2c70 fp: 0xfffffe8818d038f0

lr: 0xfffffe00258737f8 fp: 0xfffffe8818d03900

lr: 0xfffffe00258c1f04 fp: 0xfffffe8818d03cb0

lr: 0xfffffe002603f8a0 fp: 0xfffffe8818d03cd0

lr: 0xfffffe0025f2bd20 fp: 0xfffffe8818d03d70

lr: 0xfffffe0025f2b284 fp: 0xfffffe8818d03d80

lr: 0xfffffe0025f4e8dc fp: 0xfffffe8818d03dd0

lr: 0xfffffe0025f2b230 fp: 0xfffffe8818d03df0

lr: 0xfffffe002591a524 fp: 0xfffffe8818d03e30

lr: 0xfffffe002591b510 fp: 0xfffffe8818d03f20

lr: 0xfffffe002587ce98 fp: 0x0000000000000000

last started kext at 2794708009: com.apple.filesystems.smbfs 5.0 (addr 0xfffffe0024de3d10, size 78767)

loaded kexts:

com.apple.filesystems.smbfs 5.0

com.apple.driver.AppleTopCaseHIDEventDriver 6440.7

com.apple.driver.usb.realtek8153patcher 5.0.0

com.apple.filesystems.autofs 3.0

com.apple.iokit.SCSITaskUserClient 482.120.2

...and more

Thanks.

Reply

Answer 5

mausaba Author

Level 1

5 points

Aug 15, 2023 8:31 AM in response to Tesserax

hello, the MAC runs in "full security". it all started right after purchase, i brought it back but the tech guy told me the diagnostic didn't find anything, so i ran the home diagnostic again and found that the thunderbolt 3/2 converter didn't like it, so the I removed. Now it no longer gives any HW or FW errors but it keeps panicking. I ran it for 24h letting it go to sleep mode by itself, every hour I woke it up and let it go back to sleep mode. today, I tried again to do the same test but after 7h he panicked. the only element connected to the usb is the "loupedeck" with always updated SW driver. I put the result below divided into two or three due to the character limit:

panic(cpu 2 caller 0xfffffe00140afd20): IOSCSITargetDevice::setPowerState(0xfffffe24cc6c07f0 : 0xfffffe0015e8fd04, 1 -> 0) timed out after 100841 ms @IOServicePM.cpp:5604

Debugger message: panic

Memory ID: 0x6

OS release type: User

OS version: 22G74

Kernel version: Darwin Kernel Version 22.6.0: Wed Jul 5 22:22:05 PDT 2023; root:xnu-8796.141.3~6/RELEASE_ARM64_T6000

Fileset Kernelcache UUID: 2B1987A4F4C4DBE41241F23B69A1D0AD

Kernel UUID: E88B0B04-7B4D-3E52-8980-A19ED82304F7

Boot session UUID: 76AA839B-2F6F-4F5B-B192-108BE5CEC513

iBoot version: iBoot-8422.141.2

secure boot?: YES

roots installed: 0

Paniclog version: 14

KernelCache slide: 0x000000000b60c000

KernelCache base: 0xfffffe0012610000

Kernel slide: 0x000000000b614000

Kernel text base: 0xfffffe0012618000

Kernel text exec slide: 0x000000000c9ec000

Kernel text exec base: 0xfffffe00139f0000

mach_absolute_time: 0x4c47df5acf

Epoch Time: sec usec

Boot : 0x64db5e3e 0x0007d880

Sleep : 0x64db92f1 0x00021414

Wake : 0x64db92f1 0x00092dde

Calendar: 0x64db938c 0x00031064

Zone info:

Zone map: 0xfffffe10007f8000 - 0xfffffe30007f8000

. VM : 0xfffffe10007f8000 - 0xfffffe14cd4c4000

. RO : 0xfffffe14cd4c4000 - 0xfffffe1666e5c000

. GEN0 : 0xfffffe1666e5c000 - 0xfffffe1b33b28000

. GEN1 : 0xfffffe1b33b28000 - 0xfffffe20007f4000

. GEN2 : 0xfffffe20007f4000 - 0xfffffe24cd4c0000

. GEN3 : 0xfffffe24cd4c0000 - 0xfffffe299a18c000

. DATA : 0xfffffe299a18c000 - 0xfffffe30007f8000

Metadata: 0xfffffe77eccf0000 - 0xfffffe77f4cf0000

Bitmaps : 0xfffffe77f4cf0000 - 0xfffffe7800a34000

Extra : 0 - 0

TPIDRx_ELy = {1: 0xfffffe1ff4aaf010 0: 0x0000000000000002 0ro: 0x0000000000000000 }

CORE 0 PVH locks held: None

CORE 1 PVH locks held: None

CORE 2 PVH locks held: None

CORE 3 PVH locks held: None

CORE 4 PVH locks held: None

CORE 5 PVH locks held: None

CORE 6 PVH locks held: None

CORE 7 PVH locks held: None

CORE 8 PVH locks held: None

CORE 9 PVH locks held: None

CORE 0: PC=0xfffffe0013a7e308, LR=0xfffffe0013a7e308, FP=0xfffffe881d8c3ef0

CORE 1: PC=0xfffffe0013a7e308, LR=0xfffffe0013a7e308, FP=0xfffffe881f8c3ef0

CORE 2 is the one that panicked. Check the full backtrace for details.

CORE 3: PC=0xfffffe0013b7bd6c, LR=0xfffffe0013a7e314, FP=0xfffffe881f5efe80

CORE 4: PC=0xfffffe0013b7bd6c, LR=0xfffffe0013a7e314, FP=0xfffffe881f3d7e80

CORE 5: PC=0xfffffe0013b7bd6c, LR=0xfffffe0013a7e314, FP=0xfffffe881f523e80

CORE 6: PC=0xfffffe0013b7bd6c, LR=0xfffffe0013a7e314, FP=0xfffffe881fa67e80

CORE 7: PC=0xfffffe0013b7bd6c, LR=0xfffffe0013a7e314, FP=0xfffffe881f34be80

CORE 8: PC=0xfffffe0013b7bd6c, LR=0xfffffe0013a7e314, FP=0xfffffe881f393e80

CORE 9: PC=0xfffffe0013b7bd6c, LR=0xfffffe0013a7e314, FP=0xfffffe881ed83e80

Compressor Info: 0% of compressed pages limit (OK) and 0% of segments limit (OK) with 0 swapfiles and OK swap space

Panicked task 0xfffffe24cd5839b8: 0 pages, 663 threads: pid 0: kernel_task

Panicked thread: 0xfffffe1ff4aaf010, backtrace: 0xfffffe881ed9b720, tid: 196531

lr: 0xfffffe0013a46620 fp: 0xfffffe881ed9b7a0

lr: 0xfffffe0013b87338 fp: 0xfffffe881ed9b7c0

lr: 0xfffffe0013b785a4 fp: 0xfffffe881ed9b830

lr: 0xfffffe0013b76c70 fp: 0xfffffe881ed9b8f0

lr: 0xfffffe00139f77f8 fp: 0xfffffe881ed9b900

lr: 0xfffffe0013a45f04 fp: 0xfffffe881ed9bcb0

lr: 0xfffffe00141c38a0 fp: 0xfffffe881ed9bcd0

lr: 0xfffffe00140afd20 fp: 0xfffffe881ed9bd70

lr: 0xfffffe00140af284 fp: 0xfffffe881ed9bd80

lr: 0xfffffe00140d28dc fp: 0xfffffe881ed9bdd0

lr: 0xfffffe00140af230 fp: 0xfffffe881ed9bdf0

lr: 0xfffffe0013a9e524 fp: 0xfffffe881ed9be30

lr: 0xfffffe0013a9f510 fp: 0xfffffe881ed9bf20

lr: 0xfffffe0013a00e98 fp: 0x0000000000000000

last started kext at 3097020569: com.apple.filesystems.smbfs 5.0 (addr 0xfffffe0012f67d10, size 78767)

loaded kexts:

com.apple.filesystems.smbfs 5.0

com.apple.iokit.SCSITaskUserClient 482.120.2

com.apple.driver.AppleTopCaseHIDEventDriver 6440.7

com.apple.driver.usb.realtek8153patcher 5.0.0

com.apple.driver.usb.AppleUSBHostBillboardDevice 1.0

com.apple.filesystems.autofs 3.0

Reply

Answer 6

mausaba Author

Level 1

5 points

Aug 12, 2023 11:19 AM in response to mausaba

Yes, I ran the diagnostic by turning on my MAC and holding down the power button, when Loading startup option appeared I pressed and holding down the Command & D keys until the Diagnostic Loader menu appeared. Before executing it I removed all the peripherals and then I re-executed it with the connected peripherals but the diagnostic result hasn't changed: "APD000".

This is initial part of Log: