![]() Panicked task 0xffffff8bb39ec700: 4 threads: pid 131: watchdogdīacktrace (CPU 12), panicked thread: 0xffffff9a14354540, Frame : Return Address Service: opendirectoryd, total successful checkins since load (142132 seconds ago): 14213, last successful checkin: 0 seconds ago Service: WindowServer, total successful checkins since load (142102 seconds ago): 14198, last successful checkin: 120 seconds ago Service: logd, total successful checkins since load (142132 seconds ago): 14202, last successful checkin: 120 seconds ago Service returned not alive with context : unresponsive dispatch queue(s): -wl Panic(cpu 12 caller 0xffffff8019b7999f): userspace watchdog timeout: no successful checkins from logd in 120 seconds When I just downloaded the Mojave six gigger, it did this right t the end: To do that, what? Format and copy the app onto a thumbable? Something else?Īnyone who answers this question correctly I will owe a $million. That mojave installer bootable app needs to be on a thumb drive. All that is documented so I should be good.īut, there is a last step. So, I have this right, there are three commands to run through terminal to make this 6+G of mojave into an installer app on my cheese grater, thanks to the miracle that is Critical Core. So, I downloaded the 6+G verstion of the Mojave installer from Apple. ![]() I heard a rumor that having bootable thumb of Mohave is basic a survival gear for members of the cheese grating league. At this time, I would like to take this opportunity to thank each and every one of you. PatcDude was my savior as were many of his thousands of goodly apostles. I got through it, but it is not like I a contender for a medal in this event. The last time I installed an OS on my cheese grater was Catalina 15.4. The question is: do I have what I need to make the right kind of mojave bootable for my cheese grater? I think I know the answer, but the RISK LEVEL means I have to make sure. I hate to ask, so I am going to tell some jokes. I tried quitting the AMPDeviceDiscoveryAgent, which naturally stopped the messages, but still had the login screen issue afterwards, so it's probably irrelevant. The system log contains regular AMPDeviceDiscoveryAgent 'AMMuxedDeviceDisconnected' notices (about every 5 seconds). Usually there's a crash report afterwards that references the WindowServer, but it doesn't seem to identify any particular process as having caused the WS to crash. ![]() but the pauses seems to affect all the running applications.Īlso, the login screen after waking from sleep frequently locks up after I've entered a couple of characters of my password, requiring a reboot. The Finder isn't locked up - windows can be moved around etc. CPU activity during the freezes is low - it's like it's waiting for something. ![]() ![]() Things that should be instant, like opening a browser tab, can take 30 seconds (though often works normally). I've been getting random freezes (beach balls) at times over the past two weeks. System uptime in nanoseconds: 575287174961 System model name: MacPro5,1 (Mac-7BA5B2D9E42DDD94) Kernel Extensions in name corresponding to current thread: watchdogdīoot args: -lilubetaall -wegbeta agdpmod=pikera enable-gva-support shikigva=80 unfairgva=1 mbasd=1 -wegtree -no_compat_check no32exec=0ĭarwin Kernel Version 20.4.0: Thu Apr 22 21:46: root:xnu-7195.101.2~1/RELEASE_X86_64 Service:, total successful checkins since load (540 seconds ago): 42, last successful checkin: 120 seconds agoīacktrace (CPU 14), Frame : Return Address Service:, total successful checkins since load (570 seconds ago): 58, last successful checkin: 0 seconds ago Panic(cpu 14 caller 0xffffff80187eba25): userspace watchdog timeout: no successful checkins from in 120 seconds Getting black screen and the following report on reboot, any clues here? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |