remoted kernel panic on macOS 13.0 (Ventura Beta)

I upgraded my MacBook Pro to the Ventura beta and whenever the laptop starts, it would work for about 30 seconds then shoots the fan to max speed then restarts. I do not know what is causing this and I already contacted Apple support and since this beta just came out, they really didn't help much.

Thankfully I copied the crash log before the laptop crashed again and I have uploaded them to a text upload site which can be viewed here:

remoted (translated report):

-------------------------------------
Translated Report (Full Report Below)
-------------------------------------

Process:               remoted [-1]
Path:                  ???
Identifier:            remoted
Version:               ???
Code Type:             00000000 (Native)
Parent Process:        ??? [Unknown]
User ID:               

Date/Time:             2022-06-07 14:11:09.7644 -0600
OS Version:            macOS 13.0 (22A5266r)
Report Version:        12
Anonymous UUID:        [REMOVED]



System Integrity Protection: 

Notes:
resampled 135 of 1694 threads with truncated backtraces from 0 pids: 
resampled 0 of 17 images missing from 45 pids: 118,124,126,127,129,132,134,139,142,146,152,173,175,184,239,273,315,365,382,386,390,408,412,416,441,534,583,588,590,597,643,656,659,661,708,710,715,716,721,724,737,739,741,744,749
10 unindexed user-stack frames from 8 pids: 408,441,583,588,597,653,661,708
This is a watchdog-triggered termination event, and not expected to be well-represented in the legacy crash format

Crashed Thread:        Unknown

Exception Type:        

Termination Reason:    Namespace WATCHDOG, Code 1 monitoring timed out for service
(1 monitored services unresponsive): checkin with service: remoted returned not alive with context:
is_alive_func returned unhealthy : device not connected (code 0x2)
no successful checkins since 124 seconds ago, 60 seconds since last crashed by watchdogd,  (1 induced crashes)

Error Formulating Crash Report:
resampled 135 of 1694 threads with truncated backtraces from 0 pids: 
resampled 0 of 17 images missing from 45 pids: 118,124,126,127,129,132,134,139,142,146,152,173,175,184,239,273,315,365,382,386,390,408,412,416,441,534,583,588,590,597,643,656,659,661,708,710,715,716,721,724,737,739,741,744,749
10 unindexed user-stack frames from 8 pids: 408,441,583,588,597,653,661,708
This is a watchdog-triggered termination event, and not expected to be well-represented in the legacy crash format

Backtrace not available

No thread state (register information) available

Binary Images:
Binary images description not available


remoted (full report):

It does not allow me to attach URLs to other sites such as onedrive or Pastebin, so if these do not help please tell me and I will figure out how to attach the full log here.

Thank you!

Answered by Trifero in 718204022

I confirm Beta 2 installed like a charm in my Macbook Pro 16" Intel.

Exact same. 2019 16” MBP. This happened immediately on a fresh install - no Cisco, no Little Snitch. The system hasn’t been up long enough to install anything on it, so this is a completely stock installation.

Same here. Macbook Pro 16" Intel I9 2019, fresh installation.

Accepted Answer

I confirm Beta 2 installed like a charm in my Macbook Pro 16" Intel.

Removing Little Snitch solved the problem with remoted on my 27" iMac 2020 (Intel) Had failing ping in the background, and as soon as Little Snitch was moved to trash the ping succeeded

remoted kernel panic on macOS 13.0 (Ventura Beta)
 
 
Q