Jump to content

[pre-release] macOS Monterey 12.3


fantomas
 Share

214 posts in this topic

Recommended Posts

2 hours ago, Slice said:

There is a patch against the issue.

Screenshot 2022-02-18 at 22.12.57.png

Didn't seem to do the trick. Implemented it via my opencore config, but still getting wakes. Will have to test longer term.

 

Oddly, wake reason is:

2022-02-18 16:15:50 -0500 Assertions          	PID 259(mDNSResponder) Created MaintenanceWake "mDNSResponder:maintenance" 00:00:00  id:0x0xd00008475 [System: PrevIdle DeclUser BGTask SRPrevSleep IntPrevDisp kCPU kDisp]
2022-02-18 16:15:50 -0500 Assertions          	PID 259(mDNSResponder) Released MaintenanceWake "mDNSResponder:maintenance" 00:00:00  id:0x0xd00008475 [System: PrevIdle DeclUser BGTask IntPrevDisp kDisp]
2022-02-18 16:15:53 -0500 DarkWake            	DarkWake from Normal Sleep [CDN] : due to XDCI/ Using AC (Charge:0%) 5 secs
2022-02-18 16:15:53 -0500 WakeTime            	WakeTime: 3.934 sec
2022-02-18 16:15:53 -0500 Kernel Client Acks  	Delays to Wake notifications: [en0 driver is slow(msg: DidChangeState to 1)(686 ms)] [AirPort_BrcmNIC driver is slow(msg: SetState to 2)(830 ms)] [SS01 driver is slow(msg: WillChangeState to 3)(394 ms)] [PRT5 driver is slow(msg: SetState to 2)(1179 ms)] [PRT4 driver is slow(msg: SetState to 2)(1180 ms)] [PRT3 driver is slow(msg: SetState to 2)(3031 ms)]
2022-02-18 16:15:58 -0500 Wake                	DarkWake to FullWake from Normal Sleep [CDNVA] : due to UserActivity Assertion Using AC (Charge:0%)
2022-02-18 16:15:58 -0500 WakeTime            	WakeTime: 1.462 sec

 

Link to comment
Share on other sites

10 hours ago, Skyfallkavu said:

Didn't seem to do the trick. Implemented it via my opencore config, but still getting wakes. Will have to test longer term.

 

Oddly, wake reason is:

2022-02-18 16:15:50 -0500 Assertions          	PID 259(mDNSResponder) Created MaintenanceWake "mDNSResponder:maintenance" 00:00:00  id:0x0xd00008475 [System: PrevIdle DeclUser BGTask SRPrevSleep IntPrevDisp kCPU kDisp]
2022-02-18 16:15:50 -0500 Assertions          	PID 259(mDNSResponder) Released MaintenanceWake "mDNSResponder:maintenance" 00:00:00  id:0x0xd00008475 [System: PrevIdle DeclUser BGTask IntPrevDisp kDisp]
2022-02-18 16:15:53 -0500 DarkWake            	DarkWake from Normal Sleep [CDN] : due to XDCI/ Using AC (Charge:0%) 5 secs
2022-02-18 16:15:53 -0500 WakeTime            	WakeTime: 3.934 sec
2022-02-18 16:15:53 -0500 Kernel Client Acks  	Delays to Wake notifications: [en0 driver is slow(msg: DidChangeState to 1)(686 ms)] [AirPort_BrcmNIC driver is slow(msg: SetState to 2)(830 ms)] [SS01 driver is slow(msg: WillChangeState to 3)(394 ms)] [PRT5 driver is slow(msg: SetState to 2)(1179 ms)] [PRT4 driver is slow(msg: SetState to 2)(1180 ms)] [PRT3 driver is slow(msg: SetState to 2)(3031 ms)]
2022-02-18 16:15:58 -0500 Wake                	DarkWake to FullWake from Normal Sleep [CDNVA] : due to UserActivity Assertion Using AC (Charge:0%)
2022-02-18 16:15:58 -0500 WakeTime            	WakeTime: 1.462 sec

 

You asked about kernel panic after wake. Now I see the wake is successful?

 

Link to comment
Share on other sites

Hi guys, good morning,

OC: Setting NVRAM 4D1FDA02-38C7-4A6A-9C06-4BCCABB30102:boot-path = PciRoot(0x0)/Pci(0x1B,0x4)/Pci(0x0,0x0)/NVMe(0x1,D1-FB-SB-46-4A-44-1B-00)/HD(1,GPT,EC61B213-1AC1-4941-9027-986BE34A48B5,0x28,0x64000)/EFI\OC\OpenCore.efi - Invalid Parameter

Do anyone of you knows what this is?

Thanks

  • Like 1
  • Sad 1
Link to comment
Share on other sites

1 hour ago, antuneddu said:

Maybe you haven't replaced all the files? (OpenCore.efi)

Golden rule - When updating OC to a released version whether Nightly or Official Released, one should update all files in the OC Folder pertaining to that particular version.

Note on mine using Pre-released (Nightly) version, everything Green and Clean.:thumbsup_anim:

Spoiler

893765691_Screenshot2022-02-21at1_35_46pm.thumb.png.829526166dc494041299734224943d61.png

 

Edited by eSaF
  • Like 4
Link to comment
Share on other sites

1 hour ago, eSaF said:

Golden rule - When updating OC to a released version whether Nightly or Official Released, one should update all files in the OC Folder pertaining to that particular version.

Note on mine using Pre-released (Nightly) version, everything Green and Clean.:thumbsup_anim:

  Reveal hidden contents

893765691_Screenshot2022-02-21at1_35_46pm.thumb.png.829526166dc494041299734224943d61.png

 

Hi @eSaF Tell me what is that utility in the screenshot? Please.

Link to comment
Share on other sites

12 minutes ago, Matgen84 said:

Hi @eSaF Tell me what is that utility in the screenshot? Please.

It is OCAT - an app to update all files in the EFI Folder as well as Kexts plus OCvalidate to check all is well within the config.plist. I have attached the latest version for you.

OCAT_Mac.dmg.zip

  • Like 2
  • Thanks 1
Link to comment
Share on other sites

I've also been using OCAT for the last few OC updates. The fastest way to update OC in my opinion. ( Takes less than a minute ). Huzzah for this !

I still read however, the infos pertaining to the changes.

Edited by Ellybz
  • Like 6
Link to comment
Share on other sites

On 2/19/2022 at 2:09 PM, Slice said:

The patch needs the SSDT to define new method

SSDT-DBG.aml.zip 588 B · 11 downloads

I still have to go about implementing this part, but even with just the rename it seems to be working okay after letting it bake. I don't get alerts about windowserver kernel panicking at boot anymore, and automatic sleep has been functioning fine the last few days. Will use this SSDT just for posterity.

 

I'm curious though, it looks to be some sort of debug function for uefi. Did Apple recently change something related to this? I'm not sure if its meant to show up in IORegistry, but I wasn't able to find a reference to it before or after rename.

Link to comment
Share on other sites

18 hours ago, Skyfallkavu said:

I still have to go about implementing this part, but even with just the rename it seems to be working okay after letting it bake. I don't get alerts about windowserver kernel panicking at boot anymore, and automatic sleep has been functioning fine the last few days. Will use this SSDT just for posterity.

 

I'm curious though, it looks to be some sort of debug function for uefi. Did Apple recently change something related to this? I'm not sure if its meant to show up in IORegistry, but I wasn't able to find a reference to it before or after rename.

I spoke too soon. Here's my panic information for posterity. I still need to implement the SSDT before reporting anything else.

 

{"timestamp":"2022-02-22 10:48:16.00 -0500","bug_type":"210","os_version":"macOS 12.3 (21E5212f)","incident_id":"FD00C442-CFF3-4100-B7B3-D6FC4C6BFE87"}
{"macOSProcessedStackshotData":"bm8gb24gZGlzayBwYW5pYyBzdGFja3Nob3QgZm91bmQgaW4gY29yZWZpbGU=","macOSPanicString":"panic(cpu 0 caller 0xffffff7fa2a2cff5): \"virtual bool AMD9500Controller::detectPowerDown(): GPU is not found. PCI config access fails!!!\n\" @ATIController.cpp:3143\nPanicked task 0xffffff86c793f670: 261 threads: pid 0: kernel_task\nBacktrace (CPU 0), panicked thread: 0xffffff86c8842aa8, Frame : Return Address\n0xffffffd0dba93420 : 0xffffff800b483f2d \n0xffffffd0dba93470 : 0xffffff800b5e3e16 \n0xffffffd0dba934b0 : 0xffffff800b5d366d \n0xffffffd0dba93500 : 0xffffff800b423a60 \n0xffffffd0dba93520 : 0xffffff800b4842fd \n0xffffffd0dba93640 : 0xffffff800b483ab6 \n0xffffffd0dba936a0 : 0xffffff800bd15f1f \n0xffffffd0dba93790 : 0xffffff7fa2a2cff5 \n0xffffffd0dba93a90 : 0xffffff7f8c1b42cc \n0xffffffd0dba93ad0 : 0xffffff7f8c20d411 \n0xffffffd0dba93b40 : 0xffffff7f8c20dec6 \n0xffffffd0dba93b70 : 0xffffff7f8c20d2fe \n0xffffffd0dba93ba0 : 0xffffff7f8c20cfb4 \n0xffffffd0dba93bd0 : 0xffffff7f8c2052b5 \n0xffffffd0dba93c90 : 0xffffff7f8c2060ee \n0xffffffd0dba93d50 : 0xffffff7fa454621b \n0xffffffd0dba93df0 : 0xffffff7fa4545f80 \n0xffffffd0dba93e20 : 0xffffff7fa454d09c \n0xffffffd0dba93ed0 : 0xffffff800bc46f64 \n0xffffffd0dba93f20 : 0xffffff800bc4581e \n0xffffffd0dba93f60 : 0xffffff800bc44e47 \n0xffffffd0dba93fa0 : 0xffffff800b42318e \n      Kernel Extensions in backtrace:\n         com.apple.iokit.IOGraphicsFamily(594.0)[0563F2E0-24F9-345A-8423-877BF944B173]@0xffffff7fa453a000->0xffffff7fa4568fff\n            dependency: com.apple.iokit.IOPCIFamily(2.9)[9B4C95AB-1D92-3150-A499-588207511C75]@0xffffff800e004000->0xffffff800e02ffff\n         com.apple.kext.AMDSupport(4.0.8)[CE7B66DF-26E1-3EA1-9964-E9AFD5C34BB9]@0xffffff7fa2a28000->0xffffff7fa2aedfff\n            dependency: com.apple.AppleGraphicsDeviceControl(6.5.3)[60F819F4-F646-3F0C-B2A1-5794E8046825]@0xffffff7fa2d2c000->0xffffff7fa2d2ffff\n            dependency: com.apple.iokit.IOACPIFamily(1.4)[2F039002-8470-3420-91F6-17487A38C4CA]@0xffffff800db61000->0xffffff800db62fff\n            dependency: com.apple.iokit.IOGraphicsFamily(594)[0563F2E0-24F9-345A-8423-877BF944B173]@0xffffff7fa453a000->0xffffff7fa4568fff\n            dependency: com.apple.iokit.IOPCIFamily(2.9)[9B4C95AB-1D92-3150-A499-588207511C75]@0xffffff800e004000->0xffffff800e02ffff\n         com.apple.kext.AMD9500Controller(4.0.8)[01A9BB31-1092-35FE-9146-D340F60CBA6A]@0xffffff7f8c17f000->0xffffff7f8c1e3fff\n            dependency: com.apple.AppleGraphicsDeviceControl(6.5.3)[60F819F4-F646-3F0C-B2A1-5794E8046825]@0xffffff7fa2d2c000->0xffffff7fa2d2ffff\n            dependency: com.apple.iokit.IOACPIFamily(1.4)[2F039002-8470-3420-91F6-17487A38C4CA]@0xffffff800db61000->0xffffff800db62fff\n            dependency: com.apple.iokit.IOGraphicsFamily(594)[0563F2E0-24F9-345A-8423-877BF944B173]@0xffffff7fa453a000->0xffffff7fa4568fff\n            dependency: com.apple.iokit.IOPCIFamily(2.9)[9B4C95AB-1D92-3150-A499-588207511C75]@0xffffff800e004000->0xffffff800e02ffff\n            dependency: com.apple.kext.AMDSupport(4.0.8)[CE7B66DF-26E1-3EA1-9964-E9AFD5C34BB9]@0xffffff7fa2a28000->0xffffff7fa2aedfff\n         com.apple.kext.AMDFramebuffer(4.0.8)[C35DE19A-64CE-34D3-9764-32FE21CA5019]@0xffffff7f8c1fb000->0xffffff7f8c21ffff\n            dependency: com.apple.iokit.IOACPIFamily(1.4)[2F039002-8470-3420-91F6-17487A38C4CA]@0xffffff800db61000->0xffffff800db62fff\n            dependency: com.apple.iokit.IOGraphicsFamily(594)[0563F2E0-24F9-345A-8423-877BF944B173]@0xffffff7fa453a000->0xffffff7fa4568fff\n            dependency: com.apple.iokit.IOPCIFamily(2.9)[9B4C95AB-1D92-3150-A499-588207511C75]@0xffffff800e004000->0xffffff800e02ffff\n            dependency: com.apple.kext.AMDSupport(4.0.8)[CE7B66DF-26E1-3EA1-9964-E9AFD5C34BB9]@0xffffff7fa2a28000->0xffffff7fa2aedfff\n\nProcess name corresponding to current thread (0xffffff86c8842aa8): kernel_task\nBoot args: alcid=3 -lilubetaall chunklist-security-epoch=0 -chunklist-no-rev2-dev chunklist-security-epoch=0 -chunklist-no-rev2-dev\n\nMac OS version:\n21E5212f\n\nKernel version:\nDarwin Kernel Version 21.4.0: Mon Feb  7 21:32:27 PST 2022; root:xnu-8020.100.429.131.1~2\/RELEASE_X86_64\nKernel UUID: 6A53580A-5361-308C-9B08-8B8F298DF670\nKernelCache slide: 0x000000000b200000\nKernelCache base:  0xffffff800b400000\nKernel slide:      0x000000000b210000\nKernel text base:  0xffffff800b410000\n__HIB  text base: 0xffffff800b300000\nSystem model name: iMacPro1,1 (Mac-7BA5B2D9E42DDD94)\nSystem shutdown begun: NO\nPanic diags file available: YES (0x0)\nHibernation exit count: 0\n\nSystem uptime in nanoseconds: 44815136095045\nLast Sleep:           absolute           base_tsc          base_nano\n  Uptime  : 0x000028c25644858d\n  Sleep   : 0x000028bfbc2debab 0x0000000133cfd07e 0x0000280d058425b0\n  Wake    : 0x000028bfbf3d29a9 0x000000020538ddf8 0x000028bfbd9184c1\nCompressor Info: 0% of compressed pages limit (OK) and 0% of segments limit (OK) with 0 swapfiles and OK swap space\nZone info:\n  Foreign : 0xffffff8010aed000 - 0xffffff8010afb000\n  Native  : 0xffffff8061250000 - 0xffffffa061250000\n  Readonly: 0xffffff852df1c000 - 0xffffff86c78b5000\n  Metadata: 0xffffffd0f097c000 - 0xffffffd110e84000\n  Bitmaps : 0xffffffd110e84000 - 0xffffffd122e84000\n\n\n\n"}

 

Link to comment
Share on other sites

Updated to 12.3 Beta 4, everything works 100% except for playing videos in Chrome. It sometimes freezes the picture on my monitor, and after a while it kernel panics and logs out the user automatically. Before that happens the picture is frozen and the sound and everything else goes on for a while. If I avoid using Chrome then everything is fine, have not tried Firefox yet.

  • Like 3
Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

×
×
  • Create New...