Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

macOS Ventura 13.2 - Bug Fixes, Changes, and more

Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
As, I reported on another MacRumors thread 'macOS Ventura 13.2 Beta 2 - Bug Fixes, Changes and More!

My SD cards/readers can now be seen in Finder, along with my thumb drives.

Go to Library/Extensions and find the file jmPeripheralDevice.kext. I renamed the file to xjmPeripheralDevice.kext. Rebooted and now my mbp can now read theses cards and thumb drives.

I was hesitant to go to Terminal. This way is easier, but it is the same fix to this problem.

And I am soooooo happy, now!!!!!! BTW - Thanks for nothing to Apple support. It is useless in this regard. I found this fix on Reddit.com.
 
MerryLegs said:
Screenshot 2023-02-12 at 23.39.31.png
As, I reported on another MacRumors thread 'macOS Ventura 13.2 Beta 2 - Bug Fixes, Changes and More!

My SD cards/readers can now be seen in Finder, along with my thumb drives.

Go to Library/Extensions and find the file jmPeripheralDevice.kext. I renamed the file to xjmPeripheralDevice.kext. Rebooted and now my mbp can now read theses cards and thumb drives.

I was hesitant to go to Terminal. This way is easier, but it is the same fix to this problem.

And I am soooooo happy, now!!!!!! BTW - Thanks for nothing to Apple support. It is useless in this regard. I found this fix on Reddit.com.
Click to expand...
jmPeripheralDevice.kext. I don't have this.
 
euwcetus said:
jmPeripheralDevice.kext. I don't have this.
Click to expand...
In case you're curious, I also don't have the jmPeripheralDevice kext. I also just tested this "add x to the filename" method to all three of the kexts that you listed in your post. The optical media is still not recognized by Ventura 13.2.
 
  • Sad
Reactions: MerryLegs
asebg said:
In case you're curious, I also don't have the jmPeripheralDevice kext. I also just tested this "add x to the filename" method to all three of the kexts that you listed in your post. The optical media is still not recognized by Ventura 13.2.
Click to expand...
Thanks. I think there is nothing I need to do for this problem. I have to wait for the next update :(
 
  • Sad
Reactions: MerryLegs
asebg said:
The optical media is still not recognized by Ventura 13.2.
Click to expand...

Yup - Depending on who's doing the talking - Apple says it's a Pioneer problem and Pioneer says it's Apple's, but my understanding is that Pioneer is working the issue. I have an Asus burner and it works fine in 13.2.

Lou
 
flowrider said:
Yup - Depending on who's doing the talking - Apple says it's a Pioneer problem and Pioneer says it's Apple's, but my understanding is that Pioneer is working the issue. I have an Asus burner and it works fine in 13.2.

Lou
Click to expand...
Yep - Pioneer is clearly trying to fix the issue. Hard to say what Apple is doing but I wouldn’t be surprised if we got a stealth fix snuck into the next update bc of the bad press they got.
 
  • Like
Reactions: MerryLegs
euwcetus said:
jmPeripheralDevice.kext. I don't have this.
Click to expand...
Are you having the problem with the SD cards and thumb drives, or the Pioneer? Or, all three? I have an external Apple CD/DVD player/burner and it never had a problem with 13.2. My Samsung external SSDs never had a problem with 13.2 either.

Thank heavens, we have a work around to fix the SD card/thumb drive problem. Otherwise, I would still be totally fked. Good job, apple, good job. :(

Still waiting for the official fix........
 
Last edited:
13.2.1 released today. Does it fix the USB problems? Some report it seems to. Fingers crossed.
 
I just upgraded to Ventura 13.2.1 on my 2017 iMac Pro. Happy to report that my Pioneer Blu-Ray USB drive is now showing up. Thank goodness.
 
  • Like
Reactions: osplo
pshufd said:
Sometimes it's useful to read through the stack trace to get an idea as to the area of macOS that's failing.
Click to expand...
I haven't been able to make sense of the panic logs. There are generally two flavors:

Code: 
panic(cpu 0 caller 0xffffff80078f8a3a): AppleUSBHostLegacyClient::setPowerState(0xffffff8694238aa0 : 0xffffff800a006c96, 2 -> 1) timed out after 10179 ms @IOServicePM.cpp:5547
Panicked task 0xffffff99c5f05208: 408 threads: pid 0: kernel_task
Backtrace (CPU 0), panicked thread: 0xffffff8b5f3cd0c8, Frame : Return Address
0xffffffaa894c7a90 : 0xffffff80071eb38d 
0xffffffaa894c7ae0 : 0xffffff8007358ed6 
0xffffffaa894c7b20 : 0xffffff8007348120 
0xffffffaa894c7b70 : 0xffffff8007185951 
0xffffffaa894c7b90 : 0xffffff80071eb66d 
0xffffffaa894c7c80 : 0xffffff80071ead19 
0xffffffaa894c7ce0 : 0xffffff80079e072b 
0xffffffaa894c7dd0 : 0xffffff80078f8a3a 
0xffffffaa894c7e30 : 0xffffff80078f82f9 
0xffffffaa894c7e40 : 0xffffff8007912c5e 
0xffffffaa894c7e80 : 0xffffff80078f7118 
0xffffffaa894c7ea0 : 0xffffff8007244c98 
0xffffffaa894c7ee0 : 0xffffff8007245d4b 
0xffffffaa894c7fa0 : 0xffffff800718519e 

Process name corresponding to current thread (0xffffff8b5f3cd0c8): kernel_task

Code: 
panic(cpu 10 caller 0xffffff801ff31941): userspace watchdog timeout: no successful checkins from WindowServer in 120 seconds
WindowServer has not exited since first loaded
service: logd, total successful checkins in 36134 seconds: 3614, last successful checkin: 0 seconds ago
service: WindowServer, total successful checkins in 36100 seconds: 3598, last successful checkin: 120 seconds ago
service: remoted, total successful checkins in 36134 seconds: 3612, last successful checkin: 0 seconds ago
service: opendirectoryd, total successful checkins in 36134 seconds: 3613, last successful checkin: 0 seconds ago
service: configd, total successful checkins in 36134 seconds: 3613, last successful checkin: 0 seconds ago

Panicked task 0xffffff9ade2f19d8: 3 threads: pid 129: watchdogd
Backtrace (CPU 10), panicked thread: 0xffffff96118310c8, Frame : Return Address
0xffffffd0a319b590 : 0xffffff801cbeb38d 
0xffffffd0a319b5e0 : 0xffffff801cd58ed6 
0xffffffd0a319b620 : 0xffffff801cd48120 
0xffffffd0a319b670 : 0xffffff801cb85951 
0xffffffd0a319b690 : 0xffffff801cbeb66d 
0xffffffd0a319b780 : 0xffffff801cbead19 
0xffffffd0a319b7e0 : 0xffffff801d3e07f3 
0xffffffd0a319b8d0 : 0xffffff801ff31941 
0xffffffd0a319b8e0 : 0xffffff801ff315e0 
0xffffffd0a319b900 : 0xffffff801ff306c9 
0xffffffd0a319ba30 : 0xffffff801d353d4a 
0xffffffd0a319bb90 : 0xffffff801ccffb29 
0xffffffd0a319bca0 : 0xffffff801cbc2c99 
0xffffffd0a319bd50 : 0xffffff801cbdbbd2 
0xffffffd0a319bdc0 : 0xffffff801cbdc2da 
0xffffffd0a319bef0 : 0xffffff801cd2a71a 
0xffffffd0a319bfa0 : 0xffffff801cb85db6 
      Kernel Extensions in backtrace:
         com.apple.driver.watchdog(1.0)[A0D45B98-9CEC-33FB-8E19-3AEBEC002241]@0xffffff801ff2f000->0xffffff801ff31fff

Process name corresponding to current thread (0xffffff96118310c8): watchdogd
 
beefstew said:
I haven't been able to make sense of the panic logs. There are generally two flavors:

Code: 
panic(cpu 0 caller 0xffffff80078f8a3a): AppleUSBHostLegacyClient::setPowerState(0xffffff8694238aa0 : 0xffffff800a006c96, 2 -> 1) timed out after 10179 ms @IOServicePM.cpp:5547
Panicked task 0xffffff99c5f05208: 408 threads: pid 0: kernel_task
Backtrace (CPU 0), panicked thread: 0xffffff8b5f3cd0c8, Frame : Return Address
0xffffffaa894c7a90 : 0xffffff80071eb38d
0xffffffaa894c7ae0 : 0xffffff8007358ed6
0xffffffaa894c7b20 : 0xffffff8007348120
0xffffffaa894c7b70 : 0xffffff8007185951
0xffffffaa894c7b90 : 0xffffff80071eb66d
0xffffffaa894c7c80 : 0xffffff80071ead19
0xffffffaa894c7ce0 : 0xffffff80079e072b
0xffffffaa894c7dd0 : 0xffffff80078f8a3a
0xffffffaa894c7e30 : 0xffffff80078f82f9
0xffffffaa894c7e40 : 0xffffff8007912c5e
0xffffffaa894c7e80 : 0xffffff80078f7118
0xffffffaa894c7ea0 : 0xffffff8007244c98
0xffffffaa894c7ee0 : 0xffffff8007245d4b
0xffffffaa894c7fa0 : 0xffffff800718519e

Process name corresponding to current thread (0xffffff8b5f3cd0c8): kernel_task

Code: 
panic(cpu 10 caller 0xffffff801ff31941): userspace watchdog timeout: no successful checkins from WindowServer in 120 seconds
WindowServer has not exited since first loaded
service: logd, total successful checkins in 36134 seconds: 3614, last successful checkin: 0 seconds ago
service: WindowServer, total successful checkins in 36100 seconds: 3598, last successful checkin: 120 seconds ago
service: remoted, total successful checkins in 36134 seconds: 3612, last successful checkin: 0 seconds ago
service: opendirectoryd, total successful checkins in 36134 seconds: 3613, last successful checkin: 0 seconds ago
service: configd, total successful checkins in 36134 seconds: 3613, last successful checkin: 0 seconds ago

Panicked task 0xffffff9ade2f19d8: 3 threads: pid 129: watchdogd
Backtrace (CPU 10), panicked thread: 0xffffff96118310c8, Frame : Return Address
0xffffffd0a319b590 : 0xffffff801cbeb38d
0xffffffd0a319b5e0 : 0xffffff801cd58ed6
0xffffffd0a319b620 : 0xffffff801cd48120
0xffffffd0a319b670 : 0xffffff801cb85951
0xffffffd0a319b690 : 0xffffff801cbeb66d
0xffffffd0a319b780 : 0xffffff801cbead19
0xffffffd0a319b7e0 : 0xffffff801d3e07f3
0xffffffd0a319b8d0 : 0xffffff801ff31941
0xffffffd0a319b8e0 : 0xffffff801ff315e0
0xffffffd0a319b900 : 0xffffff801ff306c9
0xffffffd0a319ba30 : 0xffffff801d353d4a
0xffffffd0a319bb90 : 0xffffff801ccffb29
0xffffffd0a319bca0 : 0xffffff801cbc2c99
0xffffffd0a319bd50 : 0xffffff801cbdbbd2
0xffffffd0a319bdc0 : 0xffffff801cbdc2da
0xffffffd0a319bef0 : 0xffffff801cd2a71a
0xffffffd0a319bfa0 : 0xffffff801cb85db6
      Kernel Extensions in backtrace:
         com.apple.driver.watchdog(1.0)[A0D45B98-9CEC-33FB-8E19-3AEBEC002241]@0xffffff801ff2f000->0xffffff801ff31fff

Process name corresponding to current thread (0xffffff96118310c8): watchdogd
Click to expand...

Well, WindowServer and USB power. Are you using a USB dock or hub?

I usually see stack traces with the routine names in them; not just the addresses.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back