IOKit

Gain user-space access to hardware devices and drivers using IOKit.

IOKit Documentation

Posts under IOKit tag

60 results found
Post marked as unsolved
467 Views

M1 Mac does not support DDC/CI

The DDC/CI application can work well on MacbookPro/Mac Pro (Big Sur), but it doesn't work on M1 Mac (both macOS 11.0.1 and 11.1). M1’s graphics card is Apple, not Intel or AMD. Does this incompatible issue relate with new graphics card or kernel change? Any alternative solution for M1?
Asked
Last updated .
Post marked as unsolved
309 Views

Debugging universal kext panic on 11.2.1 Apple Silicon + KDK11.3

I'm running into problems trying to get symbols loaded into an lldb session debugging a panic of a custom, universal kext. The panic happens when LogicX closes a MIDI port implemented by a MIDIplugin and serviced by the kext. When the KP happens, I am able to attach the debugger, but running: command script import "/Library/Developer/KDKs/KDK_11.3_20E5186d.kdk/System/Library/Kernels/kernel.release.t8101.dSYM/Contents/Resources/Python/kernel_release.py" results in this: (lldb) kdp-remote 192.168.1.96 Version: Darwin Kernel Version 20.3.0: Thu Jan 21 00:06:51 PST 2021; root:xnu-7195.81.3~1/RELEASE_ARM64_T8101; UUID=9FE8C0DA-8ED0-381C-9CEC-2A779F3E1503; stext=0xfffffe00142b4000 Kernel UUID: 9FE8C0DA-8ED0-381C-9CEC-2A779F3E1503 Load Address: 0xfffffe00142b4000 WARNING: Unable to locate kernel binary on the debugger system. Target arch: arm64e Traceback (most recent call last): File "/Library/Developer/KDKs/KDK_11.3_20E5186d.kdk/System/Library/Kernels/kernel.release.t8101.dSYM/Contents/Resources/Python/lldbmacros/core/operating_system.py", line 704, in __init__ self.register_set = Armv8_RegisterSet() File "/Library/Developer/KDKs/KDK_11.3_20E5186d.kdk/System/Library/Kernels/kernel.release.t8101.dSYM/Contents/Resources/Python/lldbmacros/core/operating_system.py", line 63, in __init__ self.switch_context_address = osplugin_target_obj.FindSymbols('Switch_context')[0].GetSymbol().GetStartAddress().GetLoadAddress(osplugin_target_obj) File "/Users/wdawson/Downloads/Xcode-beta.app/Contents/SharedFrameworks/LLDB.framework/Resources/Python/lldb/__init__.py", line 10450, in __getitem__ raise IndexError IndexError Target arch: arm64e Traceback (most recent call last): File "/Library/Developer/KDKs/KDK_11.3_20E5186d.kdk/System/Library/Kernels/kernel.release.t8101.dSYM/Contents/Resources/Python/lldbmacros/core/operating_system.py", line 704, in __init__ self.register_set = Armv8_RegisterSet() File "/Library/Developer/KDKs/KDK_11.3_20E5186d.kdk/System/Library/Kernels/kernel.release.t8101.dSYM/Contents/Resources/Python/lldbmacros/core/operating_system.py", line 63, in __init__ self.switch_context_address = osplugin_target_obj.FindSymbols('Switch_context')[0].GetSymbol().GetStartAddress().GetLoadAddress(osplugin_target_obj) File "/Users/wdawson/Downloads/Xcode-beta.app/Contents/SharedFrameworks/LLDB.framework/Resources/Python/lldb/__init__.py", line 10450, in __getitem__ raise IndexError IndexError Process 1 stopped thread #1, stop reason = signal SIGSTOP frame #0: 0xffffffe0143c9770 error: kdp read memory failed Target 0: (No executable module.) stopped. (lldb) Things I've tried: Multiple permutations of Xcode 12.4 - 12.5b2 and KDKs, though only KDK11.3 seems to have the release T8101 kernel binary. On Intel (because the KDK says you can't do it on M1), where the KP does NOT happen, running the DEVELOPMENT and KASAN kernels hoping they might assert on something bad the kext is doing. Loading a panic coredump into lldb. (Same result as "live" debugging the panic. Can anyone shed any light or at least validate that I should be able to symbolicate in an lldb session using the KDKs? Thanks in advance for any pointers or help! Wade
Asked
Last updated .
Post marked as unsolved
111 Views

Issue loading a KEXT on M1 MacBook Pro

I am working on porting an existing KEXT to run on M1 on MacOS 11.2.3. It currently works fine on Intel Based Macs. I have the KEXT currently signed to "Run Locally". It loads OK on Intel. On my M1 MBP I adjust the Security Policy to allow the KEXT to load and also disabled SIP. When I attempt to load the KEXT the first time, I get the warning to allow it to load. I allow it and restart. Then after the reboot, I attempt to load the kext, it complains that "A program has updated system extension(s) signed by .... that will be incompatible with a future version of macOS, etc." I approve the load in the system preference and reboot. I then attempt to load the kext and I am presented with the same message. If I re-approve and reboot, the message comes up again. I am stuck in this loop. The following is the output of sqlite3… tom@Toms-MBP Extensions % sudo sqlite3 /var/db/SystemPolicyConfiguration/KextPolicy .dump Password: PRAGMA foreign_keys=OFF; BEGIN TRANSACTION; CREATE TABLE settings ( name TEXT, value TEXT, PRIMARY KEY (name) ); INSERT INTO settings VALUES('cdhashColumnAdded','YES'); INSERT INTO settings VALUES('databaseSchemaVersion','2'); INSERT INTO settings VALUES('migrationPerformed','YES'); INSERT INTO settings VALUES('cdhashMigrationPerformed','YES'); CREATE TABLE kext_load_history_v3 ( path TEXT PRIMARY KEY, team_id TEXT, bundle_id TEXT, boot_uuid TEXT, created_at TEXT, last_seen TEXT, flags INTEGER , cdhash TEXT); INSERT INTO kext_load_history_v3 VALUES('/Library/Extensions/xxxx3.kext','6DVCB76QJW','com.chelsio.driver.xxxx3','A42D5D10-B32A-43ED-9F95-E5543B9427AD','2021-02-27 22:45:42','2021-02-27 22:45:42',16,'9caae0349b2ff008eefff2b5c9697f59a63d07c5'); INSERT INTO kext_load_history_v3 VALUES('/Library/Extensions/xxxx.kext',NULL,'com.chelsio.driver.xxxx','A42D5D10-B32A-43ED-9F95-E5543B9427AD','2021-02-27 22:45:42','2021-03-30 18:56:26',16,'ad48778b5256d450f5bca1ae28f128986ab00f6c'); INSERT INTO kext_load_history_v3 VALUES('/Users/tom/Desktop/xxxx 2021-03-29 15-22-04/Products/Library/Extensions/xxxx.kext',NULL,'com.chelsio.driver.xxxx','351D5A51-13FB-4639-ABB5-EBC1DE31E824','2021-03-29 19:29:47','2021-03-29 19:29:47',16,'556209210cadf8aa74af150670c8330586ea7de2'); INSERT INTO kext_load_history_v3 VALUES('/Users/tom/Desktop/xxxx 2021-03-29 16-04-02/Products/Library/Extensions/xxxx.kext',NULL,'com.chelsio.driver.xxxx','526DAE0D-6DAB-42D1-9F94-0A43DDCE9E47','2021-03-29 20:21:14','2021-03-30 18:46:17',16,'ad48778b5256d450f5bca1ae28f128986ab00f6c'); INSERT INTO kext_load_history_v3 VALUES('/Users/tom/Desktop/xxxx 2021-03-30 16-20-04/Products/Library/Extensions/xxxx.kext',NULL,'com.chelsio.driver.xxxx','6F5549C8-A11D-45E0-B254-47B4B484CC00','2021-03-30 20:21:01','2021-04-06 16:02:28',16,'e1878e5e83fe35d0ea2ac2f0f695f12508ee116b'); INSERT INTO kext_load_history_v3 VALUES('/Library/Apple/System/Library/Extensions/RemoteVirtualInterface.kext','Apple Software','com.apple.nke.rvi','DA2E6D0F-7FC1-48A0-A69E-1FA0A950EFBA','2021-03-30 20:22:45','2021-04-09 16:44:42',16,'60e4eb4425a37cf2fb3de93b58f4c590dca2a02c'); INSERT INTO kext_load_history_v3 VALUES('/Users/tom/Desktop/xxxx 2021-04-07 12-33-31/Products/Library/Extensions/xxxx.kext',NULL,'com.chelsio.driver.xxxx','3D688DEE-CFBE-4FCE-8950-22074CB567C8','2021-04-07 17:23:25','2021-04-09 16:48:57',272,'ad48778b5256d450f5bca1ae28f128986ab00f6c'); CREATE TABLE kext_policy ( team_id TEXT, bundle_id TEXT, allowed BOOLEAN, developer_name TEXT, flags INTEGER, PRIMARY KEY (team_id, bundle_id) ); INSERT INTO kext_policy VALUES(NULL,'com.chelsio.driver.xxxx',1,'Unidentified - xxxx',4); INSERT INTO kext_policy VALUES('Apple Software','com.apple.nke.rvi',1,'Apple Inc.',0); CREATE TABLE kext_policy_mdm ( team_id TEXT, bundle_id TEXT, allowed BOOLEAN, payload_uuid TEXT, PRIMARY KEY (team_id, bundle_id) ); CREATE TABLE deprecation_alert_history ( developer_name TEXT PRIMARY KEY, created_at TEXT, last_alert TEXT ); INSERT INTO deprecation_alert_history VALUES('Unidentified - xxxx','2021-03-29 20:21:14','2021-04-09 16:48:57'); COMMIT; tom@Toms-MBP Extensions %  I am working on getting this kext working as a stop-gap so I can get recreate the driver with DriverKit. Any advice as to what I can do to get this kext loaded on the M1?
Asked
by TomReu.
Last updated .
Post marked as unsolved
64 Views

M1 Mac doesn't support IODisplayCreateInfoDictionary API

I used IODisplayCreateInfoDictionary , IODisplayConnect api for monitor control with Intel mac machine. But it doesn't work with M1 Silicon machine. So I have questions. Will these api not be supported by M1 Silicon anymore? Now we changed "IODisplayCreateInfoDictionary" to "IORegistryEntryCreateCFProperties" API for M1 machine. I heard that Apple will release M2 machine. Does this api maintain? Can we use IORegistryEntryCreateCFProperties API with M2?
Asked
by hjung.
Last updated .
Post marked as unsolved
101 Views

how to know if the macOS device is battery-less

Hi, I am writing a c++ application where there is a requirement to know if the MacOS device has battery installed or not. I didn't find any standard way to do so. One option I found was to use pmset -g rawbatt, but pmset docs doesn't say anything about rawbatt option. Is it deprecated? Moreover, the output which I get on running this command is : pmset -g rawbatt output: 04/01/21 18:13:30 Couldn't read battery status; error = 010000003 what does this error code mean? Does it mean that its a battery-less machine. Thanks!
Asked
by sweta_96.
Last updated .
Post marked as unsolved
207 Views

Catalina macOS 10.15 - How to write audio applications?

Hi. I need a way to create something like vb-audio cable for Mac. So in other words, I need to be able to "capture" audio from application A (which I have no control over. could be quick time or any application that plays audio) and channel that into my own Mac application. (application B) I found an abandoned open source project called Soundflower that also does exactly what I need - it can be found here: https://github.com/mattingalls/Soundflower/tree/master/SoundflowerBed The main application Soundflower seems to create the virtual audio device?? And then the Soundflowerbed app seems to be the wrapper that has all the business logic to control the device. I tested using the installer - and it seems to work. It creates a virtual audio device on my machine. I am able to set sound flower as the default output device ... turn on the music / sound in application A... and then I can set the input device on application B to be the Soundflower device and voila. I can hear sound from application A inside app B. I started off by trying to just compile Soundflower kext on macos 10.15 ... and I managed to get it working (I'm not a Mac or c programmer) And now I was about to try to get Soundflowerbed also compiled. But I'm wondering if this is the right approach. Should I just reuse the kext and try to create a new application that wraps it? what SDK's / frameworks should I be using if I want to target macOS 10.15? there's a lot of good info on the developer site but I just don't know where to start reading. do I need IOKit? should I be reading avfoundations? Just a few pointers would be appreciated.
Asked
by codebrews.
Last updated .
Post marked as unsolved
94 Views

Early iBook G4 Power Management Documentation?

Is there any source of documentation for power management hardware of the early iBook G4's( ie PowerBook6,3 and PowerBook6,5)? I've got OS 9.2.2 installed( unsupported ), but would like to figure how to get the system to sleep or hibernate. I know that hibernation to disk was never really supported under OS X on Powerbooks/iBooks, but there is a few hacks you can toss in that makes it work. Hibernate to disk was removed from the classic Mac OS between OS 9.0 and OS 9.0.4 due to disk corruption in low memory situations, but I'd like to see if I could reenable it.
Asked
by nvflash.
Last updated .
Post marked as unsolved
280 Views

IOServiceGetMatchingServices not returning graphics model data

I want graphics card details using objective c. used IOServiceGetMatchingServices api for it, its working fine in Intel processor machine, but not returning model info for M1 machine. here is the code I was using    CFMutableDictionaryRef matchDict = IOServiceMatching("IOPCIDevice");        io_iterator_t iterator;        if (IOServiceGetMatchingServices(kIOMasterPortDefault,matchDict,                    &iterator) == kIOReturnSuccess)   {      io_registry_entry_t regEntry;            while ((regEntry = IOIteratorNext(iterator))) {        CFMutableDictionaryRef serviceDictionary;        if (IORegistryEntryCreateCFProperties(regEntry,                          &serviceDictionary,                           kCFAllocatorDefault,                           kNilOptions) != kIOReturnSuccess)       {          IOObjectRelease(regEntry);          continue;       }        const void *GPUModel = CFDictionaryGetValue(serviceDictionary, @"model");                if (GPUModel != nil) {          if (CFGetTypeID(GPUModel) == CFDataGetTypeID()) {            NSString *modelName = [[NSString alloc] initWithData:                       (NSData *)GPUModel encoding:NSASCIIStringEncoding];                        NSLog(@"GPU Model: %@", modelName);           [modelName release];         }       }        CFRelease(serviceDictionary);        IOObjectRelease(regEntry);     }      IOObjectRelease(iterator);   }
Asked
Last updated .
Post marked as unsolved
276 Views

Reading EDID data on Apple M1 devices

Is there any way to read EDID data in new Apple M1 devices since the below code snippet does not work in M1 machines however it works in Intel based Mac. io_object_t object = -1;       io_iterator_t iterator;     CFMutableDictionaryRef matching = IOServiceMatching("IODisplayConnect");     kern_return_t kernResult = IOServiceGetMatchingServices(kIOMasterPortDefault, matching, &iterator);       if (KERN_SUCCESS == kernResult && iterator != 0) {           object = IOIteratorNext(iterator);           while (object != 0) {               CFDictionaryRef dict = IODisplayCreateInfoDictionary(object, kIODisplayOnlyPreferredName);       /*        process data here        */               object = IOIteratorNext(iterator);     }     IOObjectRelease(iterator);   } Also tried replacing "IODisplayConnect" by "IODPDevice" but still get an empty iterator.
Asked
Last updated .
Post marked as unsolved
465 Views

IOServiceGetMatchingServices returning empty iterator

The following code sequence works on Catalina and on Intel Big Sur devices, it does not work on the new Apple M1 devices running Big Sur. CFMutableDictionaryRef matching = IOServiceMatching("IODisplayConnect"); io_iterator_t iter = 99; kern_return_t err = IOServiceGetMatchingServices( kIOMasterPortDefault, matching, &iter ); The "matching" variable seems valid: matching CFMutableDictionaryRef 1 key/value pair [0] "IOProviderClass" : "IODisplayConnect" 		key __NSCFConstantString * "IOProviderClass" 		value __NSCFString * "IODisplayConnect" The call to "IOServiceGetMatchingServices" sets the "iter" value to 0. If I use another class name in the "IOServiceMatching" call, say "IOMediaBSDClient", "IOServiceGetMatchingServices" returns a valid iterator. Would Big Sur on Apple M1 devices need additional calls, or has this service class been deprecated? Using "IODisplayConnect" allows me to get display information via "IODisplayCreateInfoDictionary". Suggestions...
Asked
Last updated .
Post marked as unsolved
240 Views

USB current overlimit warnings

I am trying to get to the bottom of "USB ACCESSORIES DISABLED Unplug the accessory using too much power to re-enable USB devices" notifications I get on my 2014 iMac. These pop ups occur irrespective of: (1) which USB cables I use (2) whether the devices are directly connected to the iMac or through a powered hub (3) whether one ore more devices are connected to the powered hub. The devices in question are Seagate Backup+Hub external drives, which are themselves also self-powered. System Information app shows the devices with no indication of over limit problems (e.g., a drive may show requires 500ma using 100ma). dmesg: [ 838.878907]: 000838.878906 AppleUSB20HubPort@14114300: AppleUSBHostPort::interruptOccurred: overcurrent detected with port status 0x0, localSimulatedInterrupts = 0x1 [ 843.894384]: 000843.894382 AppleUSB30HubPort@14814300: AppleUSBHostPort::interruptOccurred: overcurrent detected with port status 0x4000, localSimulatedInterrupts = 0x1 [ 843.980643]: 000843.980642 AppleUSB20HubPort@14114300: AppleUSBHostPort::interruptOccurred: overcurrent detected with port status 0x0, localSimulatedInterrupts = 0x1 I get absolutely no discernible data errors or corruption on the drives, and the messages seem to have no effect on the volume mounts or filesystem operations. Several Seagate drives exhibit the issue. Seagate blames Apple. So, I've resorted to capturing XHC20 traffic with Wireshark to see if I can figure out the bus messages that cause the warnings. However, I have no idea what to look for as I've never done low level USB work. Any hints? Given the lack of actual problems, I would certainly love to at least be able to squelch the on screen notifications. Any hints?
Asked
Last updated .
Post marked as unsolved
3.4k Views

Capturing USB traffic with Wireshark (Catalina)

A related thread in this forum shows that the USB hubs are exposed as interfaces that can be brought up and down with the ifconfig utility. However, it seems that these interfaces are no longer available in Catalina.Has something fundamentally changed with Catalina that would break USB captures? Is there another known method for enabling these interfaces in such a way that Wireshark will recognize them? Maybe a new system policy setting ... ?
Asked
Last updated .
Post marked as unsolved
331 Views

Virtual Audio Device with Driver kit

We have a product which has remote desktop functionality, where users can connect to their remote machines and do their work seems-less. Along with that we are providing extra support to hear system sounds, for that we had an existing solution with KEXT using IOKit. Where we are using IOAudioStream and supporting API classes for input and Output audio sounds. Since System Extension is introduced from macOS 10.15, Apple is recommending transition from KEXT to DEXT. In recent releases our sound KEXT is unable to load in Kernel because of recent OS updates, now we are planning to migrate to System Extension approach. As part of this we went through Driver Kit APIs, then we found IOKit APIs are not part of Driver Kit framework. These are the classes which has majority APIs to transfer the System sounds with the help of IOAudioStream. The below thread tells, https://developer.apple.com/forums/thread/133318 we can implement audio drivers if the device is of USB, but in our case it is Virtual Network device. We are struck at this part, how to create a Network Audio Device in the new approach. Kindly help us how to achieve this in the current environment or Are there any plans to include IOKit APIs in Driver Kit framework soon! Thanks in Advance, Regards, Venkata.
Asked
Last updated .
Post marked as unsolved
407 Views

Apple Silicon M1 crashing with IOPCIFamily based custom KEXT

We have developed an IOPCIFamily based custom KEXT to communicate with Thunderbolt interface storage device. This KEXT is working fine with Apple machines with Intel CPUs in all types of machines (iMac, iMac Pro and MacBooks). We tested this KEXT with Apple Silicon M1 machine where we are observing crash for the very first command we send to the Thunderbolt device. We observed that there is difference in number of bits in Physical Address we use for preparing command PRPs. In Intel machines we get 28-Bit Physical Address whereas in M1 we are getting 36-Bit address used for PRPs. We use inTaskWithPhysicalMask api to allocate memory buffer we use for preparing command PRPs. Below are the options we have used for this: options: kIOMemoryPhysicallyContiguous | kIODirectionInOut capacity: 16kb physicalMask: 0xFFFFF000UL (We want 4kb aligned memory) According to below documentation, we have to use inTaskWithPhysicalMask api to get memory below 4gb. https://developer.apple.com/library/archive/documentation/Darwin/Conceptual/64bitPorting/KernelExtensionsandDrivers/KernelExtensionsandDrivers.html#//apple_ref/doc/uid/TP40001064-CH227-SW1 Some devices can only handle physical addresses that fit into 32 bits. To the extent that it is possible to use 64-bit addresses you should do so, but for these devices, you can either use IODMACommand or the initWithPhysicalMask method of IOBufferMemoryDescriptor to allocate a bounce buffer within the bottom 4 GB of physical memory. So just want to know what's the difference between Intel and ARM64 architecture with respect to physical memory access. Is there any difference between byte order for physical memory address..?? Crash log is given below: panic(cpu 0 caller 0xfffffe0016e08cd8): "apciec[0:pcic0-bridge]::handleInterrupt: Request address is greater than 32 bits linksts=0x99000001 pcielint=0x00020000 linkcdmsts=0x00000800 (ltssm 0x11=L0)\n" Debugger message: panic Memory ID: 0x6 OS release type: User OS version: 20C69 Kernel version: Darwin Kernel Version 20.2.0: Wed Dec 2 20:40:21 PST 2020; root:xnu-7195.60.75~1/RELEASEARM64T8101 Fileset Kernelcache UUID: 3E6AA74DF723BCB886499A5AAB34FA34 Kernel UUID: 48F71DB3-6C91-3E62-9576-3A1DCEF2B536 iBoot version: iBoot-6723.61.3 secure boot?: YES Paniclog version: 13 KernelCache slide: 0x000000000dbfc000 KernelCache base: 0xfffffe0014c00000 Kernel slide: 0x000000000e73c000 Kernel text base: 0xfffffe0015740000 Kernel text exec base: 0xfffffe0015808000 machabsolutetime: 0x12643a9c5 Epoch Time: sec usec Boot : 0x5fe06736 0x0009afbc Sleep : 0x00000000 0x00000000 Wake : 0x00000000 0x00000000 Calendar: 0x5fe067fd 0x0006569d CORE 0 recently retired instr at 0xfffffe0015971798 CORE 1 recently retired instr at 0xfffffe0015972c5c CORE 2 recently retired instr at 0xfffffe0015972c5c CORE 3 recently retired instr at 0xfffffe0015972c5c CORE 4 recently retired instr at 0xfffffe0015972c60 CORE 5 recently retired instr at 0xfffffe0015972c60 CORE 6 recently retired instr at 0xfffffe0015972c60 CORE 7 recently retired instr at 0xfffffe0015972c60 Panicked task 0xfffffe166ce9e550: 75145 pages, 462 threads: pid 0: kernel_task Panicked thread: 0xfffffe166d053918, backtrace: 0xfffffe306cb4b6d0, tid: 141 lr: 0xfffffe0015855f8c fp: 0xfffffe306cb4b740 lr: 0xfffffe0015855d58 fp: 0xfffffe306cb4b7b0 lr: 0xfffffe0015977f5c fp: 0xfffffe306cb4b7d0 lr: 0xfffffe0015969914 fp: 0xfffffe306cb4b880 lr: 0xfffffe001580f7e8 fp: 0xfffffe306cb4b890 lr: 0xfffffe00158559e8 fp: 0xfffffe306cb4bc20 lr: 0xfffffe00158559e8 fp: 0xfffffe306cb4bc90 lr: 0xfffffe0015ff03f8 fp: 0xfffffe306cb4bcb0 lr: 0xfffffe0016e08cd8 fp: 0xfffffe306cb4bd60 lr: 0xfffffe00166bc778 fp: 0xfffffe306cb4be30 lr: 0xfffffe0015f2226c fp: 0xfffffe306cb4be80 lr: 0xfffffe0015f1e2f4 fp: 0xfffffe306cb4bec0 lr: 0xfffffe0015f1f050 fp: 0xfffffe306cb4bf00 lr: 0xfffffe0015818c14 fp: 0x0000000000000000 Kernel Extensions in backtrace: com.apple.driver.AppleEmbeddedPCIE(1.0)[4F37F34B-EE1B-3282-BD8B-00009B954483]@0xfffffe00166b4000->0xfffffe00166c7fff dependency: com.apple.driver.AppleARMPlatform(1.0.2)[5CBA9CD0-E248-38E3-94E5-4CC5EAB96DE1]@0xfffffe0016148000->0xfffffe0016193fff dependency: com.apple.driver.IODARTFamily(1)[88B19766-4B19-3106-8ACE-EC29201F00A3]@0xfffffe0017890000->0xfffffe00178a3fff dependency: com.apple.iokit.IOPCIFamily(2.9)[5187699D-1DDC-3763-934C-1C4896310225]@0xfffffe0017c48000->0xfffffe0017c63fff dependency: com.apple.iokit.IOReportFamily(47)[93EC9828-1413-3458-A6B2-DBB3E24540AE]@0xfffffe0017c64000->0xfffffe0017c67fff com.apple.driver.AppleT8103PCIeC(1.0)[35AEB73B-D51E-3339-AB5B-50AC78740FB8]@0xfffffe0016e04000->0xfffffe0016e13fff dependency: com.apple.driver.AppleARMPlatform(1.0.2)[5CBA9CD0-E248-38E3-94E5-4CC5EAB96DE1]@0xfffffe0016148000->0xfffffe0016193fff dependency: com.apple.driver.AppleEmbeddedPCIE(1)[4F37F34B-EE1B-3282-BD8B-00009B954483]@0xfffffe00166b4000->0xfffffe00166c7fff dependency: com.apple.driver.ApplePIODMA(1)[A8EFA5BD-B11D-3A84-ACBD-6DB25DBCD817]@0xfffffe0016b0c000->0xfffffe0016b13fff dependency: com.apple.iokit.IOPCIFamily(2.9)[5187699D-1DDC-3763-934C-1C4896310225]@0xfffffe0017c48000->0xfffffe0017c63fff dependency: com.apple.iokit.IOReportFamily(47)[93EC9828-1413-3458-A6B2-DBB3E24540AE]@0xfffffe0017c64000->0xfffffe0017c67fff dependency: com.apple.iokit.IOThunderboltFamily(9.3.2)[11617399-2987-322D-85B6-EF2F1AD4A794]@0xfffffe0017d80000->0xfffffe0017e93fff Stackshot Succeeded Bytes Traced 277390 (Uncompressed 703968) ** System Information: Apple Silicon M1 BigSur 11.1 Model: Macmini9,1 Any help or suggestion is really appreciated. Thanks
Asked
by anshu1102.
Last updated .