Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

system_profiler SPPCIDataType crashes #2

Open
jamgold opened this issue Oct 21, 2014 · 7 comments
Open

system_profiler SPPCIDataType crashes #2

jamgold opened this issue Oct 21, 2014 · 7 comments

Comments

@jamgold
Copy link

jamgold commented Oct 21, 2014

I am using this boot loader on a MacPro1,1 and when /usr/sbin/system_profiler tries to list the SPPCIDataType data type, the program crashes. No idea if that is related to the bootloader or not ...

system_profiler SPPCIDataType
2014-10-20 21:10:08.670 system_profiler[10531:127437] Property list invalid for format: 200 (property list dictionaries may only have keys which are CFStrings, not 'CFNumber')
2014-10-20 21:10:08.672 system_profiler[10531:127437] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: 'data parameter is nil'
*** First throw call stack:
(
    0   CoreFoundation                      0x00007fff8c3e964c __exceptionPreprocess + 172
    1   libobjc.A.dylib                     0x00007fff8ba0c6de objc_exception_throw + 43
    2   CoreFoundation                      0x00007fff8c3e94fd +[NSException raise:format:] + 205
    3   Foundation                          0x00007fff82dfb21f +[NSPropertyListSerialization propertyListWithData:options:format:error:] + 67
    4   SPSupport                           0x000000010bce207a -[SPDocument _setReport:forDataType:] + 97
    5   SPSupport                           0x000000010bce243a -[SPDocument _reportFromBundlesForDataType:] + 690
    6   SPSupport                           0x000000010bce2a47 -[SPDocument reportForDataType:] + 180
    7   SPSupport                           0x000000010bce2d01 __34-[SPDocument reportsForDataTypes:]_block_invoke + 68
    8   libdispatch.dylib                   0x00007fff88c06344 _dispatch_client_callout2 + 8
    9   libdispatch.dylib                   0x00007fff88c06873 _dispatch_apply_serial + 42
    10  libdispatch.dylib                   0x00007fff88bfac13 _dispatch_client_callout + 8
    11  libdispatch.dylib                   0x00007fff88c059a1 _dispatch_sync_f_invoke + 39
    12  libdispatch.dylib                   0x00007fff88c05f60 dispatch_apply_f + 290
    13  SPSupport                           0x000000010bce2b55 -[SPDocument reportsForDataTypes:] + 234
    14  SPSupport                           0x000000010bce5d66 -[SPDocument xmlPropertyListRepresentationForDataTypes:] + 27
    15  system_profiler                     0x000000010bcd3865 system_profiler + 18533
    16  system_profiler                     0x000000010bcd3a6c system_profiler + 19052
    17  libdispatch.dylib                   0x00007fff88bff323 _dispatch_call_block_and_release + 12
    18  libdispatch.dylib                   0x00007fff88bfac13 _dispatch_client_callout + 8
    19  libdispatch.dylib                   0x00007fff88bfe365 _dispatch_queue_drain + 1100
    20  libdispatch.dylib                   0x00007fff88bffecc _dispatch_queue_invoke + 202
    21  libdispatch.dylib                   0x00007fff88bfd6b7 _dispatch_root_queue_drain + 463
    22  libdispatch.dylib                   0x00007fff88c0bfe4 _dispatch_worker_thread3 + 91
    23  libsystem_pthread.dylib             0x00007fff89c6d6cb _pthread_wqthread + 729
    24  libsystem_pthread.dylib             0x00007fff89c6b4a1 start_wqthread + 13
)
libc++abi.dylib: terminating with uncaught exception of type NSException
2014-10-20 21:10:13.877 system_profiler[10530:127420] Non-zero termination status from '/usr/sbin/system_profiler -nospawn -xml SPPCIDataType -detailLevel full', termination status: 6
@Piker-Alpha
Copy link
Owner

Uhm. You are the first person to report this, here, so I wonder why nobody else did before you. Perhaps something went wrong during the installation of Yosemite, and when I see errors like this, then I normally reinstall the OS.

Have you asked other people on macrumors.com if they are experiencing the same (kind of) error(s)?

@jamgold
Copy link
Author

jamgold commented Oct 24, 2014

I have posted it on macrumors, but nobody else seems to have seen it, or noticed it. I have a vanilla, new install of Yosemite on a USB disk done on a MacBook Pro, then changed the boot.efi, and the same thing happens when I boot my MacPro from there.

@MrZarniwoop
Copy link

I believe this error is normal with an unrecognized PCIe card in the system. Are you using a non-flashed PC graphics card?

@jamgold
Copy link
Author

jamgold commented Oct 26, 2014

Yes indeed, I am. An NVIDIA GForce GT 640

@MrZarniwoop
Copy link

Pretty sure that'll do it. To know for sure, if you have one replace with any EBC firmware Mac graphics card and I bet the error goes away and System Information will properly show PCI information. I think this is true even if there is no driver for the card, like an Nvidia 7300GT or ATI 1900XT.

@jamgold
Copy link
Author

jamgold commented Oct 26, 2014

I only have the original this 2006 MacPro came with. I thought it is not longer supported.

@MrZarniwoop
Copy link

Correct, it'll be awful because Yosemite will have no driver. But, the PCIe card should be recognized and then you'll know it's not because of a bug in the boot loader.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants