Is Kernel Panic caused by DVMT = 64MB?

[gatorback]

Optiplex 3090 i3-10105T HD630: NVMe SSD outfitted with Monterey https://www.tonymacx86.com/threads/...-boot-on-a-optiplex-mff-3090-i3-10105.321903/

A kernel panic is reported when I leave the machine on overnight. When running in DVMT=32MB: 2K-resolution with framebuffer patch, the machine was stable and never had this problem.

panic(cpu 2 caller 0xffffff8005b7999f): userspace watchdog timeout: no successful checkins from WindowServer in 120 seconds

DVMT was changed to 64MB and framebuffer patch was removed => 4K resolution.

What is the cause of the remedy so that a remedy can be identified? Can I turn the checkin / watchdog off?

panic(cpu 2 caller 0xffffff8005b7999f): userspace watchdog timeout: no successful checkins from WindowServer in 120 seconds
service: logd, total successful checkins since load (26010 seconds ago): 2602, last successful checkin: 0 seconds ago
service: WindowServer, total successful checkins since load (25980 seconds ago): 2582, last successful checkin: 120 seconds ago
service: opendirectoryd, total successful checkins since load (26010 seconds ago): 2601, last successful checkin: 0 seconds ago

Panicked task 0xffffff908e557350: 3 threads: pid 122: watchdogd
Backtrace (CPU 2), panicked thread: 0xffffff8bc12c0000, Frame : Return Address
0xffffffcb588d3690 : 0xffffff800267fdad mach_kernel : _handle_debugger_trap + 0x41d
0xffffffcb588d36e0 : 0xffffff80027e10d6 mach_kernel : _kdp_i386_trap + 0x116
0xffffffcb588d3720 : 0xffffff80027d0443 mach_kernel : _kernel_trap + 0x4d3
0xffffffcb588d3770 : 0xffffff800261fa70 mach_kernel : _return_from_trap + 0xe0
0xffffffcb588d3790 : 0xffffff800268017d mach_kernel : _DebuggerTrapWithState + 0xad
0xffffffcb588d38b0 : 0xffffff800267f936 mach_kernel : _panic_trap_to_debugger + 0x2b6
0xffffffcb588d3910 : 0xffffff8002f15153 mach_kernel : _panic_with_options + 0x89
0xffffffcb588d3a00 : 0xffffff8005b7999f com.apple.driver.watchdog : __ZN10IOWatchdog14userspacePanicEP8OSObjectPvP25IOExternalMethodArguments.cold.1 + 0x27
0xffffffcb588d3a10 : 0xffffff8005b795f2 com.apple.driver.watchdog : __ZN10IOWatchdog35userspaceDisableUserspaceMonitoringEP8OSObjectPvP25IOExternalMethodArguments
0xffffffcb588d3a30 : 0xffffff8005b78971 com.apple.driver.watchdog : __ZN20IOWatchdogUserClient14externalMethodEjP25IOExternalMethodArgumentsP24IOExternalMethodDispatchP8OSObjectPv + 0x7f
0xffffffcb588d3b60 : 0xffffff8002e838ec mach_kernel : _is_io_connect_method + 0x42c
0xffffffcb588d3cc0 : 0xffffff8002786dd6 mach_kernel : _iokit_server_routine + 0x4f56
0xffffffcb588d3dd0 : 0xffffff800265a9bb mach_kernel : _ipc_kmsg_send + 0x46b
0xffffffcb588d3e60 : 0xffffff80026711e9 mach_kernel : _mach_msg_overwrite_trap + 0x2c9
0xffffffcb588d3ef0 : 0xffffff80027b30aa mach_kernel : _mach_call_munger64 + 0x1ea
0xffffffcb588d3fa0 : 0xffffff8002620256 mach_kernel : _hndl_mach_scall64 + 0x16
Kernel Extensions in backtrace:
com.apple.driver.watchdog(1.0)[72F13DD7-D531-351F-8628-18318F125B22]@0xffffff8005b77000->0xffffff8005b79fff

Process name corresponding to current thread (0xffffff8bc12c0000): watchdogd
Boot args: keepsyms=1 vsmcgen=1 debug=0x100 -v e1000=0 chunklist-security-epoch=0 -chunklist-no-rev2-dev chunklist-security-epoch=0 -chunklist-no-rev2-dev

Mac OS version:
21G115

Kernel version:
Darwin Kernel Version 21.6.0: Mon Aug 22 20:17:10 PDT 2022; root:xnu-8020.140.49~2/RELEASE_X86_64
Kernel UUID: 06A10466-36D7-3A0B-9EE7-A9053A8991A3
KernelCache slide: 0x0000000002400000
KernelCache base: 0xffffff8002600000
Kernel slide: 0x0000000002410000
Kernel text base: 0xffffff8002610000
__HIB text base: 0xffffff8002500000
System model name: iMac20,1 (Mac-CFF7D910A743CAAF)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0

System uptime in nanoseconds: 26021014532509
Last Sleep: absolute base_tsc base_nano
Uptime : 0x000017aa7d53f492
Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000
Wake : 0x0000000000000000 0x0000000f06ac0792 0x0000000000000000
Compressor Info: 0% of compressed pages limit (OK) and 0% of segments limit (OK) with 0 swapfiles and OK swap space
Zone info:
Zone map: 0xffffff8089ff8000 - 0xffffffa089ff8000
. PGZ : 0xffffff8089ff8000 - 0xffffff8091ff9000
. VM : 0xffffff8091ff9000 - 0xffffff855d992000
. RO : 0xffffff855d992000 - 0xffffff86f6cc5000
. GEN0 : 0xffffff86f6cc5000 - 0xffffff8bc265e000
. GEN1 : 0xffffff8bc265e000 - 0xffffff908dff7000
. GEN2 : 0xffffff908dff7000 - 0xffffff9559990000
. GEN3 : 0xffffff9559990000 - 0xffffff9a2532a000
. DATA : 0xffffff9a2532a000 - 0xffffffa089ff8000
Metadata: 0xffffffa08a008000 - 0xffffffa0aa008000
Bitmaps : 0xffffffa0aa008000 - 0xffffffa0c2008000
=== 1/7/23 ===

 

[Feartech]

Optiplex 3090 i3-10105T HD630: https://www.tonymacx86.com/threads/...-boot-on-a-optiplex-mff-3090-i3-10105.321903/

A kernel panic is reported when I leave the machine on overnight. When running in DVMT=32MB: 2K-resolution with framebuffer patch, the machine was stable and never had this problem.




DVMT was changed to 64MB and framebuffer patch was removed => 4K resolution.

What is the cause of the remedy so that a remedy can be identified?

not sure you would need:
vsmcgen=1 boot argument

 

[gatorback]

not sure you would need:
vsmcgen=1 boot argument

Thank you Feartech. vsmcgen=1 removed from bootargs

 

[gatorback]

I am trying to confirm that DVMT is NOT the problem so that I can move along in the troubleshooting process. Insight from senior members is appreciated.

 

[Feartech]

I am trying to confirm that DVMT is NOT the problem so that I can move along in the troubleshooting process. Insight from senior members is appreciated.

still missing your EFI folder

 

[gatorback]

still missing your EFI folder

Thank you for responding. I look forward to your analysis / advice

 

[Feartech]

Thank you for responding. I look forward to your analysis / advice

remove:
_8.8_ReleaseFromScratch
_Optiplex_3090
_RMC
your EFI is not a "dumping ground" for random folders etc


SSDT-RHUB.aml is not required

CustomSMBIOSGuid should be enabled

UpdateSMBIOSMode should be set to custom

MinDate and MinVersion should be set to 0 if you are using Big Sur / Monterey / Ventura

try also testing ig-platform-id 00009B3E

also you will want to be doing this:

The New Beginner's Guide to USB Port Configuration

Important Update: June 2023 From Big Sur 11.3 on the built-in OpenCore XhciPortLimit quirk no-longer worked as described. This became a known "bug", though in reality it was Apple changing their internal code, making a simple "peek and poke" to keep it operating, a difficult task. However, with...

www.tonymacx86.com

 

[gatorback]

@Feartech Your suggestions were tested with the NVME Monterey SSDs. Unfortunately, the kernel panics continued.

A BigSur (SATA-SSD) was booted with the same OC-EFI (NVME Monterey SSD) and did not kernel panic after 6 hours.

Can we eliminate the OC configuration as the root cause of the problem?

 

[Feartech]

@Feartech Your suggestions were tested with the NVME Monterey SSDs. Unfortunately, the kernel panics continued.

A BigSur (SATA-SSD) was booted with the same OC-EFI (NVME Monterey SSD) and did not kernel panic after 6 hours.

Can we eliminate the OC configuration as the root cause of the problem?

what make and model drives do you have?

 

[gatorback]

NVMe = WD Blue SN570 1GB
SATA3 = WEBNCE0010PNC diskname=GLANCE

The NVMe drive did not throw the Windowserver error prior to setting DVMT=0x02=>64MB