system profiler IOCreate IOCreatePlugInInterfaceForService failed 0xe00002be

[lackdaz]

Hi, I'm on 10.14.16 (Mojave) and I've been getting these errors of late on the first line, I'm on a 13" MBP:

2019-11-05 15:41: 55.196 system_profiler[3880:8668137] SPUSBDevice: IOCreatePlugInInterfaceForService failed 0xe00002be

Any idea what might be causing it?

[feurig]

Mohave

[tomtastic]

Same issue on Catalina

system_profiler[18758:392265] SPUSBDevice: IOCreatePlugInInterfaceForService failed 0xe00002be

https://github.com/jlhonora/lsusb/pull/16

[laclouis5]

I have a similar issue on Monterey 12.6.2.

Output of lsusb:

2022-12-14 09:52:43.317 system_profiler[4736:43910] SPUSBDevice: IOCreatePlugInInterfaceForService failed 0xe00002be
2022-12-14 09:52:43.327 system_profiler[4736:43910] SPUSBDevice: IOCreatePlugInInterfaceForService failed 0xe00002be
/usr/local/bin/lsusb: line 89: 16#14
14: syntax error in expression (error token is "14")
Bus 000 Device 000: ID 0a5c
05ac:4500
828f Broadcom Corp.
Apple Inc. BRCM20702 Hub 
Bus 000 Device 001: ID 1d6b:IWPT Linux Foundation USB 3.0 Bus 

There is no error when using lsusb -v appart from the two warnings:

2022-12-14 09:53:29.578 system_profiler[4878:44431] SPUSBDevice: IOCreatePlugInInterfaceForService failed 0xe00002be
2022-12-14 09:53:29.587 system_profiler[4878:44431] SPUSBDevice: IOCreatePlugInInterfaceForService failed 0xe00002be
USB:

    USB 3.0 Bus:

      Host Controller Driver: AppleUSBXHCIWPT
      PCI Device ID: 0x9cb1 
      PCI Revision ID: 0x0003 
      PCI Vendor ID: 0x8086 

        BRCM20702 Hub:

          Product ID: 0x4500
          Vendor ID: 0x0a5c  (Broadcom Corp.)
          Version: 1.00
          Manufacturer: Apple Inc.
          Location ID: 0x14300000

            Bluetooth USB Host Controller:

              Product ID: 0x828f
              Vendor ID: 0x05ac (Apple Inc.)
              Version: 1.50
              Manufacturer: Apple Inc.
              Location ID: 0x14330000

There is a similar discussion on the Homebrew repo.

[phuclv90]

This is the issue of system_profiler SPUSBDataType which can simply be fixed by redirecting to null. It has nothing to do with lsusb

verbose () { system_profiler SPUSBDataType 2>/dev/null; }

@laclouis5 that parsing issue is entirely different from this and I've fixed it in https://github.com/jlhonora/lsusb/pull/23