Immediate Crash on MacBook Pro with Retina Display

P

prototype1010

Bit poster
I have a MacBook Pro with retina display and am trying to install parallels 8.0.18101.797180 and it is crashing immediately when I click the installer. The proportions of the icons when I double click the dmg are also way too big.

Crash Log:

Process: prl_installer [411]
Path: /Volumes/VOLUME/Parallels Desktop.app/Contents/MacOS/prl_installer
Identifier: com.parallels.desktop.console
Version: 8.0 (18101.797180)
Build Info: Parallels-18101.797180~8.0.18101.797180
Code Type: X86-64 (Native)
Parent Process: launchd [128]
User ID: 501

Date/Time: 2012-10-02 22:29:59.651 -0500
OS Version: Mac OS X 10.8.2 (12C54)
Report Version: 10

Interval Since Last Report: 19899 sec
Crashes Since Last Report: 7
Per-App Interval Since Last Report: 8 sec
Per-App Crashes Since Last Report: 6
Anonymous UUID: 2F4B9F65-AAAA-03E7-2705-DCB321BC9693

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000

VM Regions Near 0:
-->
__TEXT 0000000100000000-0000000103099000 [ 48.6M] r-x/rwx SM=COW /Volumes/VOLUME/Parallels Desktop.app/Contents/MacOS/prl_installer

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 ??? 000000000000000000 0 + 0
1 QtCorePrl 0x0000000105ea12d0 QFontLaoCodec::convertFromUnicode(QChar const*, int, QTextCodec::ConverterState*) const + 1968
2 QtCorePrl 0x0000000105ea2123 QFontLaoCodec::convertFromUnicode(QChar const*, int, QTextCodec::ConverterState*) const + 5635
3 QtCorePrl 0x0000000105e9a030 QTextCodec::fromUnicode(QString const&) const + 32
4 QtCorePrl 0x0000000105da8223 QString::toLocal8Bit() const + 51
5 QtCorePrl 0x0000000105d45957 qt_message_output(QtMsgType, char const*) + 535
6 QtCorePrl 0x0000000105d45d1a qWarning(char const*, ...) + 170
7 QtCorePrl 0x0000000105e8323e QSocketNotifier::QSocketNotifier(int, QSocketNotifier::Type, QObject*) + 126
8 QtNetworkPrl 0x00000001072e38cf QLocalSocket::connectToServer(QString const&, QFlags<QIODevice::OpenModeFlag>) + 4975
9 QtNetworkPrl 0x00000001072daf0b QLocalServer::listen(QString const&) + 267
10 prl_installer 0x0000000100843c21 xmlSaveFile + 428495
11 prl_installer 0x00000001001df4ff start + 1914111
12 prl_installer 0x00000001001dfdcb start + 1916363
13 prl_installer 0x0000000100099594 start + 578964
14 prl_installer 0x0000000100092acf start + 551631
15 prl_installer 0x000000010000c034 start + 52

Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x00007fff8ddd0d16 kevent + 10
1 libdispatch.dylib 0x00007fff8bde7dea _dispatch_mgr_invoke + 883
2 libdispatch.dylib 0x00007fff8bde79ee _dispatch_mgr_thread + 54

Thread 2:
0 libsystem_kernel.dylib 0x00007fff8ddd06d6 __workq_kernreturn + 10
1 libsystem_c.dylib 0x00007fff90bc1eec _pthread_workq_return + 25
2 libsystem_c.dylib 0x00007fff90bc1cb3 _pthread_wqthread + 412
3 libsystem_c.dylib 0x00007fff90bac171 start_wqthread + 13

Thread 3:
0 libsystem_kernel.dylib 0x00007fff8ddd06d6 __workq_kernreturn + 10
1 libsystem_c.dylib 0x00007fff90bc1eec _pthread_workq_return + 25
2 libsystem_c.dylib 0x00007fff90bc1cb3 _pthread_wqthread + 412
3 libsystem_c.dylib 0x00007fff90bac171 start_wqthread + 13

Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000105ffa282 rbx: 0x0000000000000000 rcx: 0x00007fff5fbff500 rdx: 0x00007fff7c68a3a8
rdi: 0x0000000105ed81da rsi: 0x0000000105ed8024 rbp: 0x00007fff5fbff5b0 rsp: 0x00007fff5fbff538
r8: 0x0000000000002060 r9: 0x00007fff5fbff500 r10: 0x0000000000000000 r11: 0x000000010961c880
r12: 0x0000000105ed8024 r13: 0x0000000000000000 r14: 0x0000000000000001 r15: 0x000000000000004d
rip: 0x0000000000000000 rfl: 0x0000000000010246 cr2: 0x0000000000000000
Logical CPU: 4

**SHORTENED**

External Modification Summary:
Calls made by other processes targeting this process:
task_for_pid: 2
thread_create: 0
thread_set_state: 0
Calls made by this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by all processes on this machine:
task_for_pid: 253
thread_create: 1
thread_set_state: 0

VM Region Summary:
ReadOnly portion of Libraries: Total=324.1M resident=179.0M(55%) swapped_out_or_unallocated=145.1M(45%)
Writable regions: Total=65.4M written=6248K(9%) resident=6532K(10%) swapped_out=0K(0%) unallocated=59.0M(90%)

REGION TYPE VIRTUAL
=========== =======
CG shared images 96K
CoreServices 2816K
MALLOC 52.6M
MALLOC guard page 48K
Memory tag=251 28K
STACK GUARD 56.0M
Stack 9752K
VM_ALLOCATE 32K
__DATA 21.7M
__IMAGE 528K
__LINKEDIT 60.9M
__TEXT 263.2M
__UNICODE 544K
mapped file 18.1M
shared memory 308K
=========== =======
TOTAL 486.4M

Model: MacBookPro10,1, BootROM MBP101.00EE.B02, 4 processors, Intel Core i7, 2.3 GHz, 8 GB, SMC 2.3f32
Graphics: Intel HD Graphics 4000, Intel HD Graphics 4000, Built-In, 512 MB
Graphics: NVIDIA GeForce GT 650M, NVIDIA GeForce GT 650M, PCIe, 1024 MB
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54333531533642465238432D50422020
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54333531533642465238432D50422020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xEF), Broadcom BCM43xx 1.0 (5.106.98.81.22)
Bluetooth: Version 4.0.9f33 10885, 2 service, 18 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
Serial ATA Device: APPLE SSD SM256E, 251 GB
USB Device: hub_device, 0x8087 (Intel Corporation), 0x0024, 0x1a100000 / 2
USB Device: FaceTime HD Camera (Built-in), apple_vendor_id, 0x8510, 0x1a110000 / 3
USB Device: hub_device, 0x8087 (Intel Corporation), 0x0024, 0x1d100000 / 2
USB Device: hub_device, 0x0424 (SMSC), 0x2512, 0x1d180000 / 3
USB Device: BRCM20702 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0x1d181000 / 5
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8286, 0x1d181300 / 7
USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0262, 0x1d182000 / 4
Click to expand...
 
In order to investigate the issue further Parallels Maintenance Team has requested core dump.

To collect core dump you will need one more Mac connected to the one that experiences Kernel Panics. Here are instructions on how to collect Core Dump and upload it to our FTP share.

To get core dumps from the Mac that experiences Kernel Panics, you will need to enable this Mac to send core-dumps to the Kernel Core Dump Server and use a second Mac as a Kernel Core Dump Server on the same network. Each Mac should be connected with the Ethernet cable.

1. Second Mac (Core Dump Server) should be configured this way:

Open Terminal application (Applications -> Utilities -> Terminal ) and insert following commands one by one and after each one press Return.
NOTE: You will be asked for your password, but you will not see it while typing for security reasons.

sudo mkdir /PanicDumps
sudo chown root:wheel /PanicDumps
sudo chmod 1777 /PanicDumps
sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.kdumpd.plist

2. The Mac which crashes should be configured this way:

2.1. Open Terminal application (Applications -> Utilities -> Terminal )

2.2. Use the following command to enable kernel core dumps:
sudo nvram boot-args="debug=0xd44 _panicd_ip=your_kdump_server_ip_address"

NOTE2: 'your_kdump_server_ip_address' should be replaced with the IP address of the Mac configured as Kernel Core Dump Server For example, if your second Mac has the IP 192.168.0.10 the command will look like this:

sudo nvram boot-args="debug=0xd44 _panicd_ip=192.168.0.10"

NOTE3: You will be asked to enter your password as well.

2.3. Reboot the Mac which crashes to activate the previous command.

NOTE: Please print these instructions from File ► Print browser menu for your convenience

After reproducing panic on the crashing Mac, you will see a progress on sending dump to the server (white dots on black background). Please do not interrupt the process.

3. As soon as the crashed Mac reboots, the core dump could be found in the directory Macintosh HD -> PanicDumps on your second Mac serving as Kernel Core Dump Server.
It would be large enough, so you cannot send it via e-mail or attach to the support ticket.

Please follow instructions described in the below mentioned KB article to upload the dump to our server using below mentioned FTP share:
KB article: http://kb.parallels.com/en/9082
FTP share: Please let me know when the dump is ready.

After crash dump was uploaded and there is no need to use second Mac as Kernel Core Dump Server, you can disable crash dump service with the following command:
sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.kdumpd.plist

Please kindly provide us with requested information if possible, we are looking forward to your reply.
 
I'd like to help out but there are 3 problems with this
1) I have a retina macbook pro with no ethernet jak
2) I only have 1 mac
3) Parallels is crashing not causing a kernel panic
 
there are adapters available for Retina MBP ethernet to USB. And it is ok that you don't have kernel panic. We still need dump i'm afraid
 
You must log in or register to reply here.
Back
Top