Constant Crashes with Mac Pro and any Beat with Coherence

A

alexjasper

Junior Member
Hardware:

Mac Pro Quad 3Ghz
2 ATI Radeon X1900 XT Video Cards
3 GB RAM (6 512MB DIMMS, all OEM)
2 500 GB SATA stripped in RAID 0
1 Apple 30" Cinema Dispay - 2560x1600
2 Dell 24" Wide Aspect Ratio Displays - 1920x1200

Software:

OS X Tiger 10.4.8 w/ Xcode tools installed
Parallels 3094 and 3106 tested
Virtual HDD is a clean Windows XP Pro install

I can start the VM, login and work, but can expect 5-10 crashes per day. I have tested with a minimum config (less RAM, 1 video card) and had similar results. At present I have installed the XCODE tools so that I can disable the second processor and the second core of the first processor. If I do this it seems more stable, though performance is crap.

I experience the following crashes.

Grey KP - screen fills grey with foreign text telling you to reboot
Freeze - Both VM and OS X freeze, force quit will not help, must manually power off and on

There is no ryme or reason to these crashes. They happen when they want to and I have not found a way to costantly recreate. I have run hardware tests on the machine and everything checks out well.

The questions I have are below.

1. Is anyone else out there with a similar setup having these issues. When I say similar config I mean a Mac Pro, not a Mac Book, not a Mac Mini, not anything but a Mac Pro.

2. Is there a way to restrict these crashes to parallels so that just the VM quits?

3. Are there any other work arounds?

Any help would be appreciated. I have pasted the panic.log data from today below. Everyone of the below panics has been with Parallels running in Coherence. These have been all with 3094. 3106 seems much more unstable than 3094 at this point for me. Essentially I experience the same issues with 3106 but more frequently.

Thanks,
Alex



*********

Thu Jan 4 08:56:43 2007
panic(cpu 3 caller 0x0035BEAC): m_freem_list: m_nextpkt of m_next != NULL
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x3741b928 : 0x128d1f (0x3c9540 0x3741b94c 0x131df4 0x0)
0x3741b968 : 0x35beac (0x3e9cbc 0x4a438314 0x3741b9b8 0x2)
0x3741b9a8 : 0x473884e2 (0x4a302d00 0x4a4a6300 0x558c161c 0x20)
0x3741b9c8 : 0x4739fe5b (0x5b56000 0x4a302d00 0x1 0x12767a)
0x3741ba08 : 0x473a2539 (0x5b56000 0x0 0x3741ba38 0x34afd5)
0x3741bad8 : 0x4739037e (0x5b56000 0x4a43f300 0x0 0x4a436f00)
0x3741bb08 : 0x47390154 (0x5b6a9c0 0x5fe58e0 0x3741bb2c 0x19d23a)
0x3741bb48 : 0x473902b9 (0x5b6a9c0 0x495b4 0x5b92d00 0x21aead)
0x3741bb78 : 0x4738bb77 (0x5b6a9c0 0x4a43f300 0x0 0x0)
0x3741bbb8 : 0x2025fe (0x6284804 0x4a43f300 0x2 0x3741bc28)
0x3741bc18 : 0x232a47 (0x6284804 0x2 0x4a43f300 0x659d304)
0x3741bd58 : 0x23e705 (0x4a43f300 0x0 0x0 0x5bbe3f0)
0x3741bdc8 : 0x35f5cc (0x6427b40 0x0 0x4a43f300 0x6038b64)
0x3741be68 : 0x363e7e (0x6427b40 0x6038b64 0x6de6c80 0x4a43f300)
0x3741bec8 : 0x36422d (0x6de6c80 0x0 0x65d041c 0x5)
0x3741bf68 : 0x378337 (0x63e59c4 0x65d03d8 0x65d041c 0x0) Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AppleIntel8254XEthernet(1.1.4a5)@0x47397000
dependency: com.apple.iokit.IONetworkingFamily(1.5.1)@0x47381000
dependency: com.apple.iokit.IOPCIFamily(2.1)@0x4747c000
com.apple.iokit.IONetworkingFamily(1.5.1)@0x47381000

Kernel version:
Darwin Kernel Version 8.8.1: Mon Sep 25 19:42:00 PDT 2006; root:xnu-792.13.8.obj~1/RELEASE_I386


*********

Thu Jan 4 11:42:03 2007
panic(cpu 3 caller 0x001A3135): Unresolved kernel trap (CPU 3, Type 14=page fault), registers:
CR0: 0x80010033, CR2: 0x00000000, CR3: 0x00b71000, CR4: 0x000006e0
EAX: 0x00000000, EBX: 0x00000000, ECX: 0x00000000, EDX: 0x00000000
CR2: 0x00000000, EBP: 0x373d3438, ESI: 0x05c80780, EDI: 0x061a3e00
EFL: 0x00010246, EIP: 0x0039cfcd, CS: 0x00000008, DS: 0x06620010

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x373d3178 : 0x128d1f (0x3c9540 0x373d319c 0x131df4 0x0)
0x373d31b8 : 0x1a3135 (0x3cf1f4 0x3 0xe 0x3cea24)
0x373d32c8 : 0x19a8d4 (0x373d32e0 0x100 0x6871c30 0x100)
0x373d3438 : 0x39db92 (0x5c80780 0x39db94 0x80 0x373d34d0)
0x373d3468 : 0x4e629868 (0x5c80780 0x373d34d0 0x373d34c0 0x373d34dc)
0x373d34f8 : 0x4e629a09 (0x5e61000 0x6651d00 0x6871f84 0x0)
0x373d3528 : 0x4e615343 (0x5e61000 0x6651d00 0x6871f84 0x0)
0x373d3558 : 0x4e625f08 (0x5e61000 0x6651d00 0x6871f84 0x4186f000)
0x373d3578 : 0x4e613b06 (0x5e61000 0x6651d00 0x6871f84 0x6036f40)
0x373d3598 : 0x4e625f40 (0x5e61000 0x6871f80 0x10000000 0x6651f00)
0x373d35b8 : 0x4e617229 (0x5e61000 0x6871f80 0x5969da0 0x0)
0x373d35e8 : 0x4e634ec7 (0x65d0800 0x6871f80 0x0 0x1)
0x373d36b8 : 0x4e635547 (0x65d0800 0x6651e00 0x373d3708 0x4e62c246)
0x373d3708 : 0x4e637c2f (0x65d0800 0x6651e00 0xa02020 0xd0)
0x373d3c68 : 0x4e61995a (0x65d0800 0x373d3cd0 0x61ce4a4 0x61ce4a8)
0x373d3cf8 : 0x3ae95b (0x65d0800 0x1 0x373d3d2c 0x373d3d28) Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.apple.ATIRadeonX1000(4.4.0)@0x4e610000
dependency: com.apple.iokit.IOPCIFamily(2.1)@0x4747c000
dependency: com.apple.iokit.IOGraphicsFamily(1.4.4)@0x47599000
dependency: com.apple.iokit.IONDRVSupport(1.4.4)@0x475b4000

Kernel version:
Darwin Kernel Version 8.8.1: Mon Sep 25 19:42:00 PDT 2006; root:xnu-792.13.8.obj~1/RELEASE_I386


*********

Thu Jan 4 12:03:36 2007
panic(cpu 3 caller 0x001A3135): Unresolved kernel trap (CPU 3, Type 14=page fault), registers:
CR0: 0x80010033, CR2: 0x00000000, CR3: 0x00b71000, CR4: 0x000006e0
EAX: 0x00000000, EBX: 0x05e62000, ECX: 0x0000000c, EDX: 0x064d3700
CR2: 0x00000000, EBP: 0x3734bca8, ESI: 0x06650800, EDI: 0x0000013b
EFL: 0x00010202, EIP: 0x00000000, CS: 0x00000008, DS: 0x06430010

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x3734ba68 : 0x128d1f (0x3c9540 0x3734ba8c 0x131df4 0x0)
0x3734baa8 : 0x1a3135 (0x3cf1f4 0x3 0xe 0x3cea24)
0x3734bbb8 : 0x19a8d4 (0x3734bbd0 0x0 0x3734bbe8 0x3bc4c9)
0x3734bca8 : 0x4756cb41 (0x5e62000 0x64d3700 0x13b000 0x685e200)
0x3734bcc8 : 0x4757d6f2 (0x5e62000 0x685e200 0x6034b44 0x1)
0x3734bcf8 : 0x475719d2 (0x6168940 0x685e200 0x3734bd28 0x3bb77e)
0x3734bd28 : 0x3b05d2 (0x6650800 0x1 0x6537fcc 0x0)
0x3734bd68 : 0x189ff5 (0x6650800 0xb 0x6537fc4 0x1)
0x3734bdb8 : 0x12b4da (0x6537f9c 0x5b17ea8 0x0 0x0)
0x3734bdf8 : 0x124b2b (0x6537f00 0x0 0x30 0x3734bedc)
0x3734bf08 : 0x1955a1 (0x3734bf44 0x0 0x0 0x0)
0x3734bfc8 : 0x19ad4e (0x64f8b20 0x0 0x19d0b5 0x61b5c40) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xbfffdbc8
Kernel loadable modules in backtrace (with dependencies):
com.apple.ATIRadeonX1000(4.4.0)@0x47569000
dependency: com.apple.iokit.IOPCIFamily(2.1)@0x4747c000
dependency: com.apple.iokit.IOGraphicsFamily(1.4.4)@0x47409000
dependency: com.apple.iokit.IONDRVSupport(1.4.4)@0x47424000

Kernel version:
Darwin Kernel Version 8.8.1: Mon Sep 25 19:42:00 PDT 2006; root:xnu-792.13.8.obj~1/RELEASE_I386


*********

Thu Jan 4 16:56:17 2007
panic(cpu 0 caller 0x001A3135): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
CR0: 0x8001003b, CR2: 0x800cb88d, CR3: 0x00b71000, CR4: 0x000006e0
EAX: 0x060a28c0, EBX: 0x05b56000, ECX: 0x05b56000, EDX: 0x4e7e4860
CR2: 0x800cb88d, EBP: 0x37123ef8, ESI: 0x05b56000, EDI: 0x060a0400
EFL: 0x00010202, EIP: 0x800cb88d, CS: 0x00000008, DS: 0x00460010

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x37123cd8 : 0x128d1f (0x3c9540 0x37123cfc 0x131df4 0x0)
0x37123d18 : 0x1a3135 (0x3cf1f4 0x0 0xe 0x3cea24)
0x37123e28 : 0x19a8d4 (0x37123e40 0x0 0x13d 0x0)
0x37123ef8 : 0x4ea5bdb0 (0x5b56000 0x297 0x37123f28 0x37ec3e)
0x37123f28 : 0x39aaf2 (0x5b56000 0x60a0400 0x4ae800 0x2)
0x37123f78 : 0x13d7d2 (0x60a0400 0x609a27c 0x19d23a 0x64b1db8)
0x37123fc8 : 0x19a74c (0x0 0x0 0x19d0b5 0x64b1d74) Backtrace terminated-invalid frame pointer 0x0

*********

Thu Jan 4 17:39:07 2007
panic(cpu 2 caller 0x001A3135): Unresolved kernel trap (CPU 2, Type 27=Unknown), registers:
CR0: 0x8001003b, CR2: 0x302b6020, CR3: 0x00b72000, CR4: 0x000006e0
EAX: 0x00000003, EBX: 0x6d626572, ECX: 0x6c441000, EDX: 0x25a33b70
CR2: 0x302b6020, EBP: 0x25a33bb0, ESI: 0x6d616769, EDI: 0x63216e75
EFL: 0x00000006, EIP: 0x6ae5711a, CS: 0x00000008, DS: 0x043a0010

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x25a33978 : 0x128d1f (0x3c9540 0x25a3399c 0x131df4 0x0)
0x25a339b8 : 0x1a3135 (0x3cf1f4 0x2 0x1b 0x3c89c4)
0x25a33ac8 : 0x19a8d4 (0x25a33ae0 0x3d8b7594 0x0 0x399342)
0x25a33bb0 : 0x6ae56fa4 (0x6a4e1d6c 0xdeadbeef 0x246 0x4a12000)
0x25a33be8 : 0x6a4e29f0 (0x6ae56f90 0x25a33c1c 0x108 0x0)
0x25a33d48 : 0x6a4df8c7 (0x4c75c04 0xc0185405 0x25a33ec8 0x6)
0x25a33d78 : 0x1ef2fd (0xb000000 0xc0185405 0x25a33ec8 0x81)
0x25a33db8 : 0x1e624b (0x25a33de0 0x297 0x25a33e18 0x1cfbe5)
0x25a33e18 : 0x1de0ef (0x4b96ce4 0xc0185405 0x25a33ec8 0x81)
0x25a33e68 : 0x330295 (0x4bbd6d0 0xc0185405 0x25a33ec8 0x4a12000)
0x25a33e98 : 0x34e562 (0x4bbd6d0 0xc0185405 0x25a33ec8 0x4a12000)
0x25a33f68 : 0x378337 (0x4a12000 0x4b3fb90 0x4b3fbd4 0x0)
0x25a33fc8 : 0x19acae (0x4ad6820 0x1 0x19d0b5 0x4be9bf8) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xb0220eb8
Kernel loadable modules in backtrace (with dependencies):
com.parallels.kext.vmmain(2.2)@0x6a4de000

Kernel version:
Darwin Kernel Version 8.8.1: Mon Sep 25 19:42:00 PDT 2006; root:xnu-792.13.8.obj~1/RELEASE_I386


*********
 
Just a wild guess, but the failures appear to be occurring at different points and to be different problems. To me, this suggests hardware, or some external triggering cause unrelated to any one activity in the machine. Power glitches, static, bad memory, and the like come to mind.

But with not much to go on, it's just a wild guess.
 
Not Faulty Hardware

Joem,

Thanks for the reply. It is not hardware. The machine has been tested throughly and has also been booted in minimal config with similar problems. Not to mention the machine stays up and DOES NOT crash when parallels is not running in coherence.

Power is good as the unit is plugged into an Online UPS.

I understand it is hard for you to take in as Parallels runs smoothly on your Mac Book Pro. It runs great on my Mac Book Pro as well. But since the release of the Mac Pro, Parallels support has been marginal at best.

I am amazed that no other Mac Pro owners are joining me on this. This is now my second Mac Pro and both have had issues with Parallels.

Any help would be appreciated.

-ajasper
 
Have you checked your system log for processes running when the KP occurred?

I am running a MacPro 2.15GHz , 10.4.8 w/3GB RAM and 4 drives (no raid).

Since I've upgraded Parallels (two versions ago), I am seeing Kernel Panics with "m_freem_list: m_nextpkt of m_next != NULL" and "mbuf" issues as well. I haven't seen a panic in years otherwise.

The Parallels application wasn't actually running when the machine KP'd tonight but it KP'd at the same time as some Parallels system activity as indicated by the system log files.

Strange. I wonder why Parallels system activity occurs when the app isn't running?

Anyhow, perhaps your system log can provide additional information.


Jan 9 19:29:00 MacPro SystemStarter[55]: "/Library/StartupItems/Tablet" failed security check: permissions
Jan 9 19:29:00 MacPro configd[46]: executing /System/Library/SystemConfiguration/Kicker.bundle/Contents/Resources/enable-network
Jan 9 19:29:00 MacPro configd[46]: posting notification com.apple.system.config.network_change
Jan 9 19:29:00 MacPro lookupd[123]: lookupd (version 369.6) starting - Tue Jan 9 19:29:00 2007
Jan 9 19:29:00 MacPro Parallels: Loading Hypervisor module...
Jan 9 19:29:00 MacPro kernel[0]: [Parallels] Parallels Workstation Hypervisor started.
Jan 9 19:29:00 MacPro Parallels: Loading Monitor module...
Jan 9 19:29:00 MacPro kernel[0]: [Parallels] Parallels VM observer thread started
Jan 9 19:29:00 MacPro Parallels: Loading ConnectUSB module...
Jan 9 19:29:01 MacPro Parallels: Loading Network module...
Jan 9 19:29:00 MacPro configd[46]: target=enable-network: disabled
Jan 9 19:29:00 MacPro Parallels: Loading Virtual Ethernet module...
Jan 9 19:29:01 MacPro kernel[0]: com_parallels_kext_Pvsvnic0: Ethernet address 00:xx:xx:xx:xx:xx
Jan 9 19:29:01 MacPro kernel[0]: com_parallels_kext_Pvsvnic1: Ethernet address 00:xx:xx:xx:xx:xx
Jan 9 19:29:01 MacPro Parallels: Staring DHCP/NAT daemon...
Jan 9 19:29:02 MacPro Parallels: Restarting InternetSharing...
Jan 9 19:29:02 MacPro Parallels: Restaring CiscoVPN...
Jan 9 19:29:02 MacPro Parallels: Initialization complete.

Here's the KP info:

Tue Jan 9 19:29:00 2007
panic(cpu 2 caller 0x0035BEAC): m_freem_list: m_nextpkt of m_next != NULL
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x372b3928 : 0x128d1f (0x3c9540 0x372b394c 0x131df4 0x0)
0x372b3968 : 0x35beac (0x3e9cbc 0x441838 0x0 0x0)
0x372b39a8 : 0x6984e2 (0x4a14ec00 0x4a036900 0x372b39e8 0x201ed4)
0x372b39c8 : 0xb93e5b (0x5989000 0x4a14ec00 0x1 0x4a1ec600)
0x372b3a08 : 0xb96539 (0x5989000 0x0 0x4a1ec600 0x34afd5)
0x372b3ad8 : 0x6a037e (0x5989000 0x4a1ea900 0x0 0x4a032100)
0x372b3b08 : 0x6a0154 (0x598c740 0x58ab2f0 0x372b3b2c 0x19d23a)
0x372b3b48 : 0x6a02b9 (0x598c740 0x528a1 0x5948a40 0x21aead)
0x372b3b78 : 0x69bb77 (0x598c740 0x4a1ea900 0x0 0x0)
0x372b3bb8 : 0x2025fe (0x5f6f204 0x4a1ea900 0x2 0x372b3c28)
0x372b3c18 : 0x232a47 (0x5f6f204 0x2 0x4a1ea900 0x618a004)
0x372b3d58 : 0x23e705 (0x4a1ea900 0x0 0x0 0x6236ca0)
0x372b3dc8 : 0x35f5cc (0x6284718 0x0 0x4a1ea900 0x5c525c4)
0x372b3e68 : 0x363e7e (0x6284718 0x5c525c4 0x875e800 0x4a1ea900)
0x372b3ec8 : 0x36422d (0x875e800 0x0 0x796b19c 0x32)
0x372b3f68 : 0x378337 (0x89a31f4 0x796b158 0x796b19c 0x0) Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AppleIntel8254XEthernet(1.1.4a5)@0xb8b000
dependency: com.apple.iokit.IONetworkingFamily(1.5.1)@0x691000
dependency: com.apple.iokit.IOPCIFamily(2.1)@0x595000
com.apple.iokit.IONetworkingFamily(1.5.1)@0x691000

I've removed the tablet items from my startup folder and we'll see what happens.

I'm also going to send this to parallels support team.

Any input is appreciated.

thanks

:)
 
Last edited:
Another Mac Pro owner here with KPs

I've had six kernel panics on my Mac Pro since the beginning of the year, all starting something like: panic(cpu 3 caller 0x0035BEAC): m_freem_list: m_nextpkt of m_next != NULL

After reading this thread, I checked system.log around the time of the last two KPs, and sure enough, Parallels was attempting to do some networking stuff right around then. For now, I'm taking the step of uninstalling Parallels and maintaining a holding pattern.

bluloo: I notice that you too have the Restaring [sic] CiscoVPN line. Do you have the Cisco VPN client installed in a VM, or on your Mac Pro? After having had trouble with the Cisco VPN client on my machine, I ditched it and swore to never install it again.
 
No help from Parallels yet - same issues

I am still experiencing these problems. I run my computer with only 1 core when Parallels is open to avoid KP's and random freezes. The random freezes are the most frustrating because I dont get a KP report, I can still move my mouse but nothing happens.

The majority of these freezes happen when I am not using the virtual machine and am away rom my computer. So to reduce this I close Parallels while I am gone.

Its a shame that I have such a nice computer that can only run off of one processor and 1GB of RAM or the only app I bought this computer for will not work.

On another note, the same BETA version 3106 of Parallels runs on my Mac Book Pro with no issues whatsoever. It has been on for the last 3 weeks without one freeze.

Parallels team please find a way to make your product work with the Mac Pro.

Thanks,
ajasper
 
I am seeing kernel panics on a mac pro running 3106 beta.

Thu Feb 1 00:26:13 2007
panic(cpu 2 caller 0x001A3135): Unresolved kernel trap (CPU 2, Type 14=page fault), registers:
CR0: 0x8001003b, CR2: 0x00000000, CR3: 0x00fef000, CR4: 0x000006e0
EAX: 0x06f24e80, EBX: 0x06f678a0, ECX: 0x00000091, EDX: 0x06f1d5a0
CR2: 0x00000000, EBP: 0x48863ec8, ESI: 0x00000002, EDI: 0x606f3000
EFL: 0x00010206, EIP: 0x00000000, CS: 0x00000008, DS: 0x5fea0010

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x48863ca8 : 0x128d1f (0x3c9540 0x48863ccc 0x131df4 0x0)
0x48863ce8 : 0x1a3135 (0x3cf1f4 0x2 0xe 0x3cea24)
0x48863df8 : 0x19a8d4 (0x48863e10 0x862e640 0x0 0x5fea7c00)
0x48863ec8 : 0x5fea46c6 (0x6f678a0 0x5fea7f80 0x5fea8054 0x12a)
0x48863ef8 : 0x5fea77ca (0x8469f80 0x297 0x48863f28 0x5fea3e2d)
0x48863f28 : 0x5fea57a9 (0x78df704 0x5fea8548 0x5fea8564 0x2c)
0x48863f58 : 0x5fea3577 (0x78df704 0x5fea7c30 0x5fea7c10 0x16a)
0x48863f88 : 0x5fea36b2 (0xb000000 0x0 0x0 0x7866bb8)
0x48863fc8 : 0x19a74c (0x0 0x0 0x19d0b5 0x6f08b04) Backtrace terminated-invalid frame pointer 0x0
Kernel loadable modules in backtrace (with dependencies):
com.parallels.kext.vmmain(2.2)@0x5fea2000

Kernel version:
Darwin Kernel Version 8.8.1: Mon Sep 25 19:42:00 PDT 2006; root:xnu-792.13.8.obj~1/RELEASE_I386

look it is in a kernel loadable module. i also run the cisco vpn client, and maybe its a bad interaction. i only panic once a week or so. its tolerable, if annoying. but hey, this *is* a beta.

problem with VM sw is that it does not just crash itself, it crashes the whole machine.

andrew
 
Still Having Issues

I wish we could get some support from Parallels on this. I am still having issues with every Beta.

1970 - I have random screen outs that are only solved by reseating the DVI cable

3096 - Wont even boot

3106 - Most Stable, but crashes atleast 4 times a day, I can reduce this to 1 or 2 if I close the Parallels toolbar and run the VM with only one core of the avaialbe 4.

3120 - Crashes even more than 3106


I guess the question really should be this.

ARE THERE ANY MAC PRO OWNERS OUT THERE THAT ARENT HAVING ISSUES WITH PARALLELS?

As I described earlier I have 3106 on my MacBook Pro and have no issues whatsoever.

Any help from Parallels on this would be great.

Thanks,
Alex
 
I don't have any issue with Parellels from 3096 to 3120 on my Mac Pro. The only issue I've ever encountered was the memory leak issue in 3106 and the VM quits on its own. This only happened after the VM has been running for over 6 hours.
 
How Often are you using Parallels

CountZero,

Thanks for the quick reply. Maybe I am not in the average here but I am primarily a PC user so my VM runs 24 hours a day atleast when I am in front of it. I dont have memory leak quits like you described but full on freezes that affefct the VM and OS X. Sometimes I am lucky enough to have a Kernal Panic but more often than not I just get these odd freezes.

To keep the issues to a minimum I kill the Parallels tools assistant in the taskbar and only enable 1 processor core of the 4 available using the developers tools. By doing this my VM might make it thorugh a day with only 1 or 2 crashes.

What is your setup?

Thanks,
Alex
 
Build 3160 is also stable on my Mac Pro. Successive builds, up to and including 3120 cause KPs.

I haven't tried 3150 yet.

After I do, I am going to send a detailed report to support, via a PM and through the normal channels provided.

Hopefully, they can resolve though it seems to be plaguing relatively few users.

Sorry, no advice other than to stick with 3160 for now. :(
 
soi2k said:
bluloo: I notice that you too have the Restaring [sic] CiscoVPN line. Do you have the Cisco VPN client installed in a VM, or on your Mac Pro? After having had trouble with the Cisco VPN client on my machine, I ditched it and swore to never install it again.
Click to expand...

If I have it installed on my Mac Pro, I don't know how it got there.

I didn't notice an option under Parallels for that. Perhaps I need to more carefully look at the set up options or preferences.
 
bluloo said:
Build 3160 is also stable on my Mac Pro. Successive builds, up to and including 3120 cause KPs.

I haven't tried 3150 yet.

After I do, I am going to send a detailed report to support, via a PM and through the normal channels provided.

Hopefully, they can resolve though it seems to be plaguing relatively few users.

Sorry, no advice other than to stick with 3160 for now. :(
Click to expand...

When you say 3160 do you mean 3106? How could I go about trying 3150?

Thanks,
Alex
 
alexjasper said:
When you say 3160 do you mean 3106? How could I go about trying 3150?

Thanks,
Alex
Click to expand...


Apologies. yes, 3106.

3150 is available for download. It is available elsewhere in other threads or via Mac Update or VersionTracker.

3150 also looks like it has some neat features.
 
I too am having problems with 3120. At least one KP but more problematic are numerous random aplication crashes. Mostly occuring in Firefox and Thunderbird but not limited to them.

I also noticed a reference to CiscoVPN at one point in one of the logs. That left me scatching my head as i have never touched cisco vpn.

I havent noticed any freezing as reported by others.

Thinking it might be Coherence related, i have disabled Coherence using full screen instead and things seem a bit more stable now. Though at the moment i'm not leaving my VM up and running 24/7 like i usually do.

I'll likely try RC2 shortly, after i read a few more reports on its behaviour.
 
Upgraded

I have downloaded and installed 3150. Updated the tools, turned VT-X back on and set acceleration to high. Enabled all my processors, and booted the VM using Coherence. So far so good. I will keep you all posted.

Thanks,
Alex
 
3150 works well on my MBP but it boots to a black screen on my Mac Pro. :(

No "device removal" related KPs though. :)

Not using bootcamp partition.

Glad it's working well for you.

/Me scratches head
 
Ugghhhhh

This is what I dont understand. Why does this program act differently for everyone. My only recomendation for ou is to boot to safe mode and uninstall the Parallels Tools. Then reboot and see if the video is working, install the tools and reboot again. I saw that same issues in an earlier build and that worked for me.

Let me know your results.

-Alex
 
Not sure how to uninstall from safe mode any differently than normal mode. In safe mode Parallels won't start up.


I didn't see a GUI tool on the Mac to remove only the parallels tools.

I removed 3150 and reinstalled 3106.

I "solved" the problem accidentally. I clicked the mouse and hit the enter key a few times until I didn't hear the error sound from Windows. I waited to see what happened and the VM rebooted to a normal window. It must have been uninstalling or installing something but I couldn't see what because of the black screen.

I now have a normal window view and will uninstall parallels tools before updating to 3150.

Software can and often does function differently on different machines. It is certainly not unique to Parallels. IMO, that is the nature of software on many different configurations, unfortunately.

thanks again
 
Last edited:
You must log in or register to reply here.
Back
Top