-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CpuTscSync Monterey kernel panic on wake up #1900
Comments
yeh, I meet the situation the same as above problem. And, it happened randomly when pc workeded without attaching AC after wake. On BigSur it worked fine too. So, buddy, have you figure out what cause it ? Please |
"panic_string":"panic(cpu 2 caller 0xffffff7fa645715b): assertmsg @AppleIntelController.cpp:29033\nPanicked task 0xffffff95008b3670: 163 threads: pid 0: kernel_task\nBacktrace (CPU 2), panicked thread: 0xffffff8b6842f000, Frame : Return Address\n0xffffffd07b9fb9d0 : 0xffffff800dc87ddd \n0xffffffd07b9fba20 : 0xffffff800dde7d15 \n0xffffffd07b9fba60 : 0xffffff800ddd74e3 \n0xffffffd07b9fbab0 : 0xffffff800dc27a60 \n0xffffffd07b9fbad0 : 0xffffff800dc881ad \n0xffffffd07b9fbbf0 : 0xffffff800dc87966 \n0xffffffd07b9fbc50 : 0xffffff800e5160b9 \n0xffffffd07b9fbcc0 : 0xffffff7fa645715b \n0xffffffd07b9fbcd0 : 0xffffff7fa63fac66 \n0xffffffd07b9fbd40 : 0xffffff7fa63f6f7d \n0xffffffd07b9fbdd0 : 0xffffff800e42ec2a \n0xffffffd07b9fbe30 : 0xffffff800e42e795 \n0xffffffd07b9fbef0 : 0xffffff800e42d790 \n0xffffffd07b9fbf50 : 0xffffff800e430839 \n0xffffffd07b9fbfa0 : 0xffffff800dc2718e \n Kernel Extensions in backtrace:\n com.apple.driver.AppleIntelKBLGraphicsFramebuffer(18.0.3)[6C440BD5-E542-3F44-A61E-C6932DE02575]@0xffffff7fa63c4000->0xffffff7fa6487fff\n dependency: com.apple.AppleGraphicsDeviceControl(6.4.9)[C44DDD30-1C5B-35EA-99C2-5130D1B59B9A]@0xffffff7fa5589000->0xffffff7fa558cfff\n dependency: com.apple.iokit.IOACPIFamily(1.4)[B750EC9D-D224-309C-8C32-3F32C6257F1E]@0xffffff801033f000->0xffffff8010340fff\n dependency: com.apple.iokit.IOAcceleratorFamily2(462.4.1)[73899B24-CF1D-3468-AF75-F6E62058E2A4]@0xffffff7fa6c1e000->0xffffff7fa6c87fff\n dependency: com.apple.iokit.IOGraphicsFamily(593)[A327B1FD-1BF3-3D02-A4E5-20A37ED0493E]@0xffffff7fa6dab000->0xffffff7fa6dd9fff\n dependency: com.apple.iokit.IOPCIFamily(2.9)[023CD3FF-4EFC-3455-89C2-FF8BD98013EB]@0xffffff80107e6000->0xffffff8010810fff\n dependency: com.apple.iokit.IOReportFamily(47)[097D0056-1E44-3A97-8AD8-8D0F6B76113E]@0xffffff8010822000->0xffffff8010824fff\n\nProcess name corresponding to current thread (0xffffff8b6842f000): kernel_task\nBoot args: chunklist-security-epoch=0 -chunklist-no-rev2-dev\n\nMac OS version:\n21C52\n\nKernel version:\nDarwin Kernel Version 21.2.0: Sun Nov 28 20:28:54 PST 2021; root:xnu-8019.61.5~1/RELEASE_X86_64\nKernel UUID: E32C293C-7D8B-327C-A335-6AAD250A4881\nKernelCache slide: 0x000000000da00000\nKernelCache base: 0xffffff800dc00000\nKernel slide: 0x000000000da10000\nKernel text base: 0xffffff800dc10000\n__HIB text base: 0xffffff800db00000\nSystem model name: MacBookPro14,2 (Mac-CAD6701F7CEA0921)\nSystem shutdown begun: NO\nPanic diags file available: YES (0x0)\nHibernation exit count: 0\n\nSystem uptime in nanoseconds: 34992180804\nLast Sleep: absolute base_tsc base_nano\n Uptime : 0x0000000825b252ef\n Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000\n Wake : 0x0000000000000000 0x0000000c79e871c8 0x0000000000000000\nZone info:\nForeign : 0xffffff801b41e000 - 0xffffff801b42b000\nNative : 0xffffff8033c83000 - 0xffffffa033c83000\nReadonly : 0xffffff850094f000 - 0xffffff869a2e3000\nMetadata : 0xffffffd68b70e000 - 0xffffffd6ab897000\nBitmaps : 0xffffffd6ab897000 - 0xffffffd6b1897000\nlast started kext at 34990743390: >!A!IKBLGraphics\t18.0.3 (addr 0xffffff7fa62b7000, size 843776)\nloaded kexts:\nme.kishorprins.VoodooInput\t1.1.3\nas.acidanthera.voodoo.driver.PS2Mouse\t2.2.7\nas.acidanthera.voodoo.driver.PS2Trackpad\t2.2.7\nas.acidanthera.voodoo.driver.PS2Keyboard\t2.2.7\nru.joedm.SMCSuperIO\t1.2.8\nas.acidanthera.mieze.!IMausi\t1.0.7\nas.lvs1974.RTCMemoryFixup\t1.0.7\nas.acidanthera.voodoo.driver.PS2!C\t2.2.7\nas.vit9696.SMCProcessor\t1.2.8\nas.acidanthera.BrightnessKeys\t1.0.3\nas.lvs1974.HibernationFixup\t1.4.5\norg.acidanthera.NVMeFix\t1.0.9\norg.vanilla.driver.CPUFriend\t1.2.4\nas.vit9696.!AALC\t1.6.7\nas.vit9696.WhateverGreen\t1.5.5\nru.usrsse2.SMCBatteryManager\t1.2.8\nas.vit9696.VirtualSMC\t1.2.8\nas.vit9696.Lilu\t1.5.8\n>!A!IKBLGraphics\t18.0.3\n>AGDCBacklightControl\t6.4.9\n>!ABacklight\t180.4\n>!AMCCSControl\t1.14\n@AGDCPluginDisplayMetrics\t6.4.9\n>ACPI_SMC_PlatformPlugin\t1.0.0\n>pmtelemetry\t1\n|IOUserEthernet\t1.0.1\n>usb.!UUserHCI\t1\n>!AHV\t1\n>!ADiskImages2\t126.60.3\n>!A!IKBLGraphicsFramebuffer\t18.0.3\n>!A!ISlowAdaptiveClocking\t4.0.0\n>!AGFXHDA\t100.1.434\n@UVCService\t1\n>!ASMCLMU\t212\n>!A!IPCHPMC\t2.0.1\n>!AFIVRDriver\t4.1.0\n>!ATopCaseHIDEventDriver\t5020.1\n>!AFileSystemDriver\t3.0.1\[email protected]\t1\[email protected]\t1\[email protected]\t582.60.2\n@BootCache\t40\n@!AFSCompression.!AFSCompressionTypeZlib\t1.0.0\n@!AFSCompression.!AFSCompressionTypeDataless\t1.0.0d1\n>!ASmartBatteryManager\t161.0.0\[email protected]\t1933.61.1\[email protected]\t1.0\n>AirPort.BrcmNIC\t1400.1.1\n>!ARTC\t2.0.1\n>!AHPET\t1.8\n>!AACPIButtons\t6.1\n>!ASMBIOS\t2.1\n>!AACPIEC\t6.1\n>!AAPIC\t1.7\n@!ASystemPolicy\t2.0.0\[email protected]\t402\n|IOKitRegistryCompatibility\t1\n|EndpointSecurity\t1\n@Dont_Steal_Mac_OS_X\t7.0.0\n@kec.!AEncryptedArchive\t1\n>!ABacklightExpert\t1.1.0\n>!ASMBus!C\t1.0.18d1\n>IOPlatformPluginLegacy\t1.0.0\n>X86PlatformPlugin\t1.0.0\n|IO!BSerialManager\t9.0.0\n|IO!BPacketLogger\t9.0.0\n|IO!BHost!CUSBTransport\t9.0.0\n|IO!BHost!CUARTTransport\t9.0.0\n|IO!BHost!CTransport\t9.0.0\n>IO!BHost!CPCIeTransport\t9.0.0\n|IOAVB!F\t1010.2\[email protected]\t1000.11\n|IOEthernetAVB!C\t1.1.0\n|CSR!BHost!CUSBTransport\t9.0.0\n|Broadcom!BHost!CUSBTransport\t9.0.0\n|Broadcom!B20703USBTransport\t9.0.0\n>!AIPAppender\t1.0\n|IOAccelerator!F2\t462.4.1\n@!AGPUWrangler\t6.4.9\n@!AGraphicsDeviceControl\t6.4.9\n|IOSlowAdaptiveClocking!F\t1.0.0\n>!AHDA!C\t283.15\n|IOHDA!F\t283.15\n|IONDRVSupport\t593\n>!UAudio\t413.5\n|IOAudio!F\t300.10\[email protected]\t1.2.0\n>!AAudioClockLibs\t100.9.1\n|IOGraphics!F\t593\n>IOPlatformPlugin!F\t6.0.0d8\n>!AActuatorDriver\t5430.1\n>!AMultitouchDriver\t5430.1\n>!AInputDeviceSupport\t5400.30\n>!AHS!BDriver\t5020.1\n>IO!BHIDDriver\t9.0.0\n>usb.IOUSBHostHIDDevice\t1.2\n>usb.cdc\t5.0.0\n>usb.networking\t5.0.0\n>usb.!UHostCompositeDevice\t1.2\n>usb.!UHub\t1.2\n>!UMergeNub\t900.4.2\n>!ABSDKextStarter\t3\n|IOSurface\t302.9\[email protected]\t1\n>usb.!UHostPacketFilter\t1.0\n|IOUSB!F\t900.4.2\n>!AXsanScheme\t3\n|IONVMe!F\t2.1.0\n|IO80211!FLegacy\t1200.12.2b1\n|IOSkywalk!F\t1.0\n>mDNSOffloadUserClient\t1.0.1b8\n>corecapture\t1.0.4\n>!A!ILpssGspi\t3.0.60\n>usb.!UXHCIPCI\t1.2\n>usb.!UXHCI\t1.2\n>!AEFINVRAM\t2.1\n>!AEFIRuntime\t2.1\n|IOHID!F\t2.0.0\n|IOSMBus!F\t1.1\n|IOTimeSync!F\t1000.11\n|IONetworking!F\t3.4\n>DiskImages\t493.0.0\n|IO!B!F\t9.0.0\n|IOReport!F\t47\n$quarantine\t4\n$sandbox\t300.0\n@kext.!AMatch\t1.0.0d1\n|CoreAnalytics!F\t1\n>!ASSE\t1.0\n>!AKeyStore\t2\n>!UTDM\t532.40.7\n|IOUSBMass!SDriver\t209.40.6\n|IOSCSIBlockCommandsDevice\t452.60.2\n|IO!S!F\t2.1\n|IOSCSIArchitectureModel!F\t452.60.2\n>!AMobileFileIntegrity\t1.0.5\n$!AImage4\t4.2.0\[email protected]\t1\n>!AFDEKeyStore\t28.30\n>!AEffaceable!S\t1.0\n>!ACredentialManager\t1.0\n>KernelRelayHost\t1\n|IOUSBHost!F\t1.2\n>!UHostMergeProperties\t1.2\n>usb.!UCommon\t1.0\n>!ABusPower!C\t1.0\n>!ASEPManager\t1.0.1\n>IOSlaveProcessor\t1\n>!AACPIPlatform\t6.1\n>!ASMC\t3.1.9\n|IOPCI!F\t2.9\n|IOACPI!F\t1.4\n>watchdog\t1\[email protected]\t1\[email protected]\t1\[email protected]\t12.0\n\n\n"} |
Hi @vit9696 can you check this please ? |
@HeartAndSoul001 @gulios, please redo kernel panic with keepsyms=1 in boot arguments. it is not clear what is going on in this one. CC @lvs1974 |
ok, i'll let you know when occur KP DVMT in BIOS is set to 64M This is my OC folder/config |
thanks a lot, I have modified the Framebuffer value. And the point is I met the problem again when I use my laptop without AC attaching just now. @gulios hi, please, I wonder if your problem also happened when your laptop powered with just battery(without ac attached).I mean this may be the common feature of our problem. |
@HeartAndSoul001 have to test it with and without AC. It's random thing so hard to debug it. |
@vit9696 my laptop is Thinkpad x1 carbon 2017(cpu:i7 7600U GPU:HD 620, this is my laptop information: https://github.com/HeartAndSoul001/my-EFI-for-x1-carbon-5th). the situation I met is: my trackpad and keyboard had no response(like offline), screen displayed a static content and had no feedback. just figure out it by hard reset. |
@gulios our laptop has the same GPU platform ID. May be, you can pay attention to power method(ac or battery) when the panic happen again. Mackintosh is so fascinated isn't it? haha, have a nice day buddy! I gonna to sleep, bye! |
Hi @vit9696 Got it today
doesn't really matter AC or battery |
@gulios: could you give a try to attached version, please? |
ok, testing |
got KP
|
@gulios: can you add "-cputsdbg" into boot-args and get a boot log after restart? |
@lvs1974 i've added kext and boot arg
but no see any debug info in logs vie console.app or
log show too
|
@gulios: for dmesg you can try to add kext DebugEnhancer or add boot arg msgbuf=1048576. |
@lvs1974 ok, i set DebugEnhancer with bootargs
and got KP on boot like on screen
|
@gulios: in your KP log I see line "reset tsc adjust" (wrmsr64(MSR_IA32_TSC_ADJUST, 0)). CC @vit9696 |
I also encounter the same kernel panic in Monterey. It happened randomly
|
I have the same issue ,when wake up. panic(cpu 0 caller 0xffffff80108b34e3): Non-monotonic time: invoke at 0x1fe1634e32bf, runnable at 0x1fe1b76b18c7 @sched_prim.c:2865 Process name corresponding to current thread (0xffffff9573c95aa0): kernel_task Mac OS version: Kernel version: System uptime in nanoseconds: 35052894813008
|
so,is there a solution to this issue? |
do this quirk work? set property kernel-->Quirks-->ProvideCurrentCpuInfo to "TRUE"? My laptop had been degraded to Big Sur because of frequently hard resetting after panic(😭).So, I can not test it. |
Will try this and report back. Thanks man |
Although I haven't tested it, but I believe this doesn't work |
I have tested it, but this doesn't work |
unfortunatly, the problem still happened, I have no idea |
Hi everybody, can somebody try the kext from my post wth boot-arg TSC_sync_margin=0? |
testing |
it works.thanks |
Wow, sound pleasing. Will try this
sushilei ***@***.***>于2022年1月29日 周六20:28写道:
… Hi everybody, can somebody try the kext from my post
<#1900 (comment)>
wth boot-arg *TSC_sync_margin=0*?
it works.thanks
—
Reply to this email directly, view it on GitHub
<#1900 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AXFDSHIP65GXW4X3SDOGOILUYPMOBANCNFSM5KOMBSGA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you commented.Message ID:
***@***.***>
|
ok it should be ready/loaded
…________________
Steve Blencowe
0423 654 786
On 29 Jan 2022, at 10:51 pm, JunqiK ***@***.***> wrote:
Wow, sound pleasing. Will try this
sushilei ***@***.***>于2022年1月29日 周六20:28写道:
> Hi everybody, can somebody try the kext from my post
> <#1900 (comment)>
> wth boot-arg *TSC_sync_margin=0*?
>
> it works.thanks
>
> —
> Reply to this email directly, view it on GitHub
> <#1900 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AXFDSHIP65GXW4X3SDOGOILUYPMOBANCNFSM5KOMBSGA>
> .
> Triage notifications on the go with GitHub Mobile for iOS
> <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
> or Android
> <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
>
> You are receiving this because you commented.Message ID:
> ***@***.***>
>
—
Reply to this email directly, view it on GitHub <#1900 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHCAA5LGWRIPUDU5AZOSQ53UYPPGTANCNFSM5KOMBSGA>.
Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you are subscribed to this thread.
|
wow! what happened to the boot-arg TSC_sync_margin=0? It looks like the panic disappeared |
ok, so far so good ;) 2 days without KP ;o) |
Everybody who has success with boot-arg TSC_sync_margin=0: And would be great if more people could test it! |
testing, thx! |
oh,NO! KP! |
@sushilei: have you seen the same KP as for previous versions of CpuTscSync? |
@lvs1974 |
@sushilei: in that case it means TSC_sync_margin=0 has to be set in boot-args. Probably, when CpuTscSync sets TSC_sync_margin to zero - it is too late. |
ok, so it looks like everything is fine. No KP with that version. Thank you!!! I think we can close that issue. |
This issue might be fixed in version 1.0.6. |
Yes, I had this problem on my LEGION Y7000-2019 laptop and it bothered me a lot ,but now it seems to be solved by adding boot-args: TSC_sync_margin=0 and CpuTscSync1.0.6, (now tested for 1 day of intense use without sleep crash). However, when I remove SSDT-AWAC and change the ACPI time and alarm device to Legacy RTC in BIOS advanced settings, this KP (Non-monotonic time) often appears. However, with SSDT-AWAC enabled, this KP rarely occurs, and I think it has only occurred once in my memory. I didn't know that this KP (Non-monotonic time) could be solved with TSC_sync_margin=0. And I only unlocked the BIOS advanced settings on 29 Nov 2021, I thought I could enable legacy RTC by modifying the advanced settings, but in fact it would often sleep crash, I was using Monterey instead of Big Sur at the time, so I don't know if this is normal on Big Sur. So I thought for a long time that this had something to do with my SSDT-AWAC (as I tested it a lot). |
Hello everybody! |
testing |
Thanks, I'm using my laptop to test |
I'm on an ASRock X299 system so... pretty niche... and I was getting similar kernel panics in trying to update OpenCore for a working Catalina install (and then update that to Monterey). The 1.0.7 got me past the KP but when I'd get to the login screen, all my USB devices lost power (despite having a proper USB map and being initialized before the screen). Same thing when booting into an external Monterey installer; the system wasn't hung as there was animation on the screen telling me to connect a keyboard and trackpad. Switching to 1.0.6 and using the boot arg, however, allowed me to boot with USB working. |
@jamescobalt: it sounds quite strange, since I have not heard that TSC sync can impact on USB devices. |
1.0.7 debug version, I tested it for a day, everything is fine in my laptop so far, no boot-args: "TSC_sync_margin=0" added, no "SSDT-AWAC ". The computer wakes up from sleep normally, I think it works and I will keep testing it. |
yes, 1.0.7 works fine ! |
@jamescobalt: I implemented fallback to the old way of syncing, try this: |
Hey can someone give me step by step guide on how I can resolve this issue. |
Asus UX430AU i7-7500U
macOS 12.1 (21C52)
Open Core 0.7.7
CpuTscSync 1.0.5
On BigSur it worked fine. After Monterey getting random KP on wake up(black screen, fans spining. Only hard reset to boot again)
All kexts are up2date.
The text was updated successfully, but these errors were encountered: