Kernel Panic on MB Retina Pro

G

GeraldFi

Junior Member
Hi!

After upgrading from Parallels 9 to Parallels 10 I had today 3 Kernel Panics. And on the stack I always do find a parallels vnic extension.
This never happend with Parallels 9. I am running 10.10.4.

I did a
prlsrvctl problem-report --send --stand-alone

and received the following id:
71020948

Hopefully you do find a solution. I am just running a training and its not funny seeing the system rebooting.
 
Yes, it´s 10.2.2. And I was using VNIC1 at this time, connected my virtual machine to host-only and used this interface on my router simulator GNS3. No Problem with Parallels 9, but it seems to be an issue with 10.
 
GeraldFi said:
Yes, it´s 10.2.2. And I was using VNIC1 at this time, connected my virtual machine to host-only and used this interface on my router simulator GNS3. No Problem with Parallels 9, but it seems to be an issue with 10.
Click to expand...
Ok, I see..
Please try the following:
1. stop your VM and open VM configurations
2. In the VM config go to Hardware -> Boot Order and add this flag
vm.mem_anonymous=1
in the Boot flags box
3. Start VM and check the issue.
 
Ok, I will try this. otherwise I will downgrade to Parallels 9. I don´t have time to make an in depth troubleshooting.
 
Your recommendation might had helped, no Kernel Panic so far. And from what I have seen, the faulty VM is most probably the one running Windows 10.
What is this switch actually doing? And shouldn´t it be there automatically if it protects my system from crashing?
 
Hi again!

Sorry to say that, but today I had another crash. So it seems, your advice did not help at all.
I sent again the crash logs. ID: 71447710
Can I simply go back to Parallels9?
 
@GeraldFi of course you can revert back to the Parallels Desktop 9, you may download one of the previous versions using this KB.
But could you please check your Mac for the i/o error in the Console application:
1. Finder -> Utilities -> Console
2. in the search box please type i/o and hit Enter.
3. If you find any of this message please provide us with the results.
 
No i/o Errors found in the console.
Anything else I can send you?
I just removed P10 completly (with pdremove) and will try a reinstallation of P10. Maybe this helps, although I doubt that.
 
GeraldFi said:
No i/o Errors found in the console.
Anything else I can send you?
I just removed P10 completly (with pdremove) and will try a reinstallation of P10. Maybe this helps, although I doubt that.
Click to expand...
Ok, thanks a lot for this information.
Please try to reinstall it and let me know if the issue reoccurs.
Thanks a lot for your cooperation.
 
@GeraldFi, We've recheck your report and would like to let you know that And no Parallels-related(com.parallels.*) Kernel extensions (kexts) are present in the backtrace. ## Cause This panic happens within Nvidia or other drivers, are not directly related to Parallels Desktop.
In this case could you please ask the Apple Support about it, for more info please check the backtrace below.
(Also you may provide the Apple Support about same information)
Please accept our apologize for the inconvenience.


Kernel Extensions in backtrace:
com.apple.iokit.IOAcceleratorFamily2(156.16)[8DA5CE1F-2C00-3CE3-8BF1-1FC07BFCF4E7]@0xffffff7fa5538000->0xffffff7fa55a6fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[D8F585E8-2EE9-3135-8E37-A034123FE45C]@0xffffff7fa3b4d000
dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[6F7F093D-DBEA-356A-9A08-D8EAC7F767DE]@0xffffff7fa3c27000
com.apple.GeForce(10.0.4)[84C92A5B-73D3-33C4-9A69-9CE32825816C]@0xffffff7fa55b5000->0xffffff7fa564bfff
dependency: com.apple.iokit.IOPCIFamily(2.9)[D8F585E8-2EE9-3135-8E37-A034123FE45C]@0xffffff7fa3b4d000
dependency: com.apple.iokit.IONDRVSupport(2.4.1)[161AE366-94FE-3E53-8ABD-78A603351329]@0xffffff7fa3f33000
dependency: com.apple.nvidia.driver.NVDAResman(10.0.4)[95736EED-9154-3CBF-B639-6038E7128035]@0xffffff7fa3f4a000
dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[6F7F093D-DBEA-356A-9A08-D8EAC7F767DE]@0xffffff7fa3c27000
dependency: com.apple.iokit.IOAcceleratorFamily2(156.16)[8DA5CE1F-2C00-3CE3-8BF1-1FC07BFCF4E7]@0xffffff7fa5538000
 
Thank you for your answer. Yes, you are right, the second backtrace I did sent you occured when I pressed <cmd-F1> to mirror the display to an external monitor.

And this error occurs only when: Running Win7 in a VM with "Optimized for Retina" enabled.
I running the same Win7 and having only "Scaled" enabled, then it works fine.
So yes, it might be driver related but only occurs under a specific circumstance. Its ok and I can live with it.

Today I will do some further testing because I also did have a trace with a vnic error. But maybe this is gone with the mentioned boot option.
 
You must log in or register to reply here.
Back
Top