VMware Communities
P_2
Contributor
Contributor
Jump to solution

After update to 10.7.4 Fusion 4.1.2 crashes everytime!

Before updateting to 10.7.4 everything was right.

After updating launching Fusion causes almost always a Kernel Panic.

Reply
0 Kudos
1 Solution

Accepted Solutions
dariusd
VMware Employee
VMware Employee
Jump to solution

Aha! That is precisely what I had expected, but I was unsure if AHT would find it, and it could have otherwise been difficult to prove.  I haven't had much luck using AHT to find memory errors, but this time it hit the mark.

Here's the full explanation: The least-significant bit of memory location 0x61808b is defective and doesn't reliably hold a "zero" value.  It is in a memory area used to hold the Mac OS kernel – the core instructions to run your Mac.  The Mac OS kernel changes with each update in such a way that each new version's kernel may use a given piece of memory for a different purpose.  Sometimes the defective area might have been used rarely or not at all, or sometimes it might be some critical part of the kernel (in which case your system would probably not be bootable or would crash at entirely random times).  For the Mac OS 10.7.4 32-bit kernel, it falls within the part of the kernel that is responsible for loading a new Kernel Extension (kext), which is exactly what Fusion needs to do when it's launching... that's why Fusion triggers the crash, even though Fusion itself is not doing anything wrong.  The defective piece of memory causes a simple request to copy 8 bytes of memory to be mutated into a request to copy 65544 (0x10008) bytes from a region which doesn't have that much data, which then causes the kernel panic you've seen.

You can actually see the evidence in each of the panic logs (if you know where to look Smiley Wink):

   Backtrace (CPU 0), Frame : Return Address (4 potential args on stack)

   [...]

   0xdfbd28 : 0x618093 (0xcb4cb20 0xdfbd50 0x10008 0x609339)

The second entry there is the return address, which roughly indicates what the CPU was doing a moment ago.  The value 0x618093 means that the CPU has very recently executed code from the defective location in memory!  The third "potential argument" inside the parentheses should always be 8 here, but it is 0x10008 – a one-bit error that would only occur consistently if there was a hardware fault or kernel memory corruption in the code that it had just executed, at address 0x61808b.  The rest of the system state and panic log info are explained neatly by that one-bit error, and the crash has the same signature in every one of the panic logs you provided.

For Mac OS 10.7.3, the defective memory location was only used by the kernel once, very early in boot; likewise for Mac OS 10.7.2.  So, it looks like earlier versions were unaffected simply because at the time it was used, its value may have still been correct.  Or you were just very lucky.  Or maybe the memory just happened to start failing at the same time as you installed the 10.7.4 update...  And no-one knows what would happen when you update to Mac OS 10.7.5.

Either way, I agree that new memory modules will almost certainly lead to a happy Mac and hopefully a happy Fusion user again. :smileycool:

Cheers,

--

Darius

View solution in original post

Reply
0 Kudos
20 Replies
koi
Enthusiast
Enthusiast
Jump to solution

Panic logs? They're somewhere like /Library/Logs/PanicReporter (note this is the system library, not the one in your home folder).

Reply
0 Kudos
P_2
Contributor
Contributor
Jump to solution

Hi Koi!

I can't find such folder.
In order to work I'm following the suggestions found in this discussion http://communities.vmware.com/message/2010980 and I do not quit Fusion any more!
The problem seems to be the same (symptoms are the same...).
I will quit it and try to restart in order to obtain a new OS crash. I will upload Logs as soon as I can.

bye.

Reply
0 Kudos
P_2
Contributor
Contributor
Jump to solution

Maybe these are the files you need!
Them were in  /Library/Logs/DiagnosticReports.
Thanks.
Reply
0 Kudos
dariusd
VMware Employee
VMware Employee
Jump to solution

Hi P@olo,

Thanks for posting those panic reports... they are exactly what we needed.  It's a very strange panic, that's for sure, and it's going to require a bit more investigation before I can understand what's happening.

My first thought is that it looks quite different from the panic discussed in that other thread.  Does Fusion ever crash on the first time you launch it, or does it only crash if you quit Fusion and relaunch it again?  The kernel panic on 2012-05-11-180439 seems to have occurred as Fusion was being launched for the first time, but I don't fully trust that panic log.

Cheers,

--

Darius

Reply
0 Kudos
enucho
Contributor
Contributor
Jump to solution

Hi there Darius,

I am nor P@olo, but I got this message you wrote to him. I assume it was because a few hours ago I sent it a question about the same thing. Hereare some more details:

1. I click on the VMware Fusion to start it up, then a small window opens up with the following message: Unable to retrieve kernel zone sizes.

2. I click on OK and get the following message: Failed to initialize monitor device.

3. So then I click on OK again and I get this: Cannot find a valid peer process to connect to

4. Then I click again on OK and get nothing more except the black screen with the big white arrow. If I click on the big white arrow, I get the same series of answers as in 1, 2 and 3.

I have not attepted to get into Windows in quite a while, so I cannot tell you whether there is a pattern or not. The only thing I can tell you is that a couple of days ago, I received and installed an important Apple update for my OS (Lion).

I have never had this problem before (crashing) and, as I mentioned in my first message, it isn't as if I do not have Windows installed. It's all there, but, of course, cannot open.

Emile

Reply
0 Kudos
enucho
Contributor
Contributor
Jump to solution

Hello Darius,

I just sent you a comment about this problem. But I forgot to mention that I have the most up to date version 3.x.x NOT the 4.x.x

Emile

Reply
0 Kudos
P_2
Contributor
Contributor
Jump to solution

I'm trying to remember.....
The first crash occurs on the very first launch after the reboot required from Apple Software Update. One VM was suspended and a couple of seconds after I clicked on Fusion's icon the OS crash occurs. After a reboot of the system Fusion started again.
I'm not sure, but if I'm not wrong the second crash occurs after a Fusion quit (perhaps always with a suspended VM): I tried to relaunch Fusion and.... ops, a Kernel Panic!
I don't remember about third issue, sorry.
Reply
0 Kudos
avannoord
Contributor
Contributor
Jump to solution

I too am having the same issue... I also have the most up to date version 3.x.x.  Any idea what to do to restore my VM? I'm attempting to run Win XP Pro.

Reply
0 Kudos
avannoord
Contributor
Contributor
Jump to solution

Nevermind... I had 3.1.3. After upgrading to 3.1.4 everything worked fine.    

Reply
0 Kudos
dariusd
VMware Employee
VMware Employee
Jump to solution

Hi Emile,

Are you sure you have the latest version?  Fusion 3.1.4 was released a few weeks ago, and it specifically fixes a problem powering on VMs with Lion 10.7.4 hosts, where the exact error message is "Unable to retrieve kernel zone sizes".  Please check that you have Fusion 3.1.4 installed.

Thanks,

--

Darius

Reply
0 Kudos
enucho
Contributor
Contributor
Jump to solution

Yes, that is the versión i downloaded and instales. Thanks again.

Reply
0 Kudos
P_2
Contributor
Contributor
Jump to solution

Hi!

I experienced a new Panic! This time, after a reboot of my MacBook I launch Fusion and it opens a suspended VM window: as soon as I click on PLAY the OS crashes!

Here there is the complete report that Lion is going to send to Apple, and attached you can find the panic file:


Interval Since Last Panic Report:  441947 sec
Panics Since Last Report:          2
Anonymous UUID:                    D243BFC1-4C41-46DD-A2B1-A96EFA0B3B0E
Wed May 16 22:20:52 2012
panic(cpu 0 caller 0x2ceabf): Kernel trap at 0x002b850c, type 14=page fault, registers:
CR0: 0x80010033, CR2: 0x00dfc000, CR3: 0x1a120000, CR4: 0x00000660
EAX: 0x00010010, EBX: 0x00010008, ECX: 0x00003f56, EDX: 0x00010008
CR2: 0x00dfc000, EBP: 0x00dfbd28, ESI: 0x00dfc000, EDI: 0x475012b0
EFL: 0x00010212, EIP: 0x002b850c, CS:  0x00000008, DS:  0x00000010
Error code: 0x00000000
Backtrace (CPU 0), Frame : Return Address (4 potential args on stack)
0xdfbb68 : 0x2203de (0x6afa8c 0xdfbb88 0x229fb0 0x0)
0xdfbb98 : 0x2ceabf (0x6bcb6c 0x2b850c 0xe 0x6bcb15)
0xdfbc48 : 0x2e5214 (0xdfbc70 0xdfbc58 0xdfbc68 0x243bcc)
0xdfbc68 : 0x2b850c (0xe 0x2760048 0xdf0010 0x270010)
0xdfbd28 : 0x618093 (0xcb4cb20 0xdfbd50 0x10008 0x609339)
0xdfbd68 : 0x60e8fd (0xcb25c80 0xcaeb1c0 0xcb4c4e0 0x7117d8)
0xdfbd98 : 0x61984c (0xcb25c80 0xcb537c0 0xcaeb1c0 0xcb53780)
0xdfbdb8 : 0x619b30 (0xcb537c0 0xcaeb1c0 0xdfbdd8 0x60b7bf)
0xdfbdf8 : 0x619c69 (0xcaeb1c0 0xdfbe28 0x0 0x0)
0xdfbe38 : 0x622975 (0x0 0x13cf000 0x1871a 0xdfbe74)
0xdfbe98 : 0x24da0e (0x85fb00 0x0 0x7866ec0 0x1871a)
0xdfbed8 : 0x222db6 (0xba7b080 0xc92906c 0x1 0xdfbf34)
0xdfbf08 : 0x214063 (0xba7b000 0xffe00000 0x1 0x1)
0xdfbf48 : 0x21b25b (0xba7b000 0x0 0x0 0x0)
0xdfbf98 : 0x2b7bb7 (0x71d55d4 0x7fff 0x71d5604 0x8)
0xdfbfc8 : 0x2e5d77 (0x71d55d0 0x0 0x10 0x71d55d0)
BSD process name corresponding to current thread: kextd
Mac OS version:
11E53
Kernel version:
Darwin Kernel Version 11.4.0: Mon Apr  9 19:33:05 PDT 2012; root:xnu-1699.26.8~1/RELEASE_I386
Kernel UUID: DC2420E0-4451-376C-8A70-74301C98CE6B
System model name: MacBook3,1 (Mac-F22788C8)
System uptime in nanoseconds: 1038459037211
last loaded kext at 130539388716: com.apple.filesystems.smbfs     1.7.2 (addr 0x1392000, size 249856)
last unloaded kext at 117734876382: com.apple.driver.StorageLynx     3.0.1 (addr 0x1736000, size 12288)
loaded kexts:
com.apple.filesystems.smbfs     1.7.2
com.apple.driver.AppleBluetoothMultitouch     70.12
com.apple.filesystems.autofs     3.0
com.apple.driver.AudioAUUC     1.59
com.apple.driver.AppleHDA     2.2.0f3
com.apple.driver.AppleUpstreamUserClient     3.5.9
com.apple.driver.AppleHWSensor     1.9.5d0
com.apple.driver.AppleMCCSControl     1.0.26
com.apple.driver.SMCMotionSensor     3.0.2d6
com.apple.driver.AppleIntelGMAX3100     7.0.0
com.apple.driver.AppleIntelGMAX3100FB     7.0.0
com.apple.driver.AppleSMCPDRC     5.0.0d0
com.apple.iokit.IOUserEthernet     1.0.0d1
com.apple.iokit.IOBluetoothSerialManager     4.0.5f11
com.apple.Dont_Steal_Mac_OS_X     7.0.0
com.apple.driver.AudioIPCDriver     1.2.2
com.apple.driver.AppleLPC     1.5.8
com.apple.driver.ACPI_SMC_PlatformPlugin     5.0.0d0
com.apple.driver.AppleBacklight     170.1.9
com.apple.driver.CSRUSBBluetoothHCIController     4.0.5f11
com.apple.driver.AppleUSBTrackpad     225.2
com.apple.driver.AppleUSBTCKeyEventDriver     225.2
com.apple.driver.AppleUSBTCKeyboard     225.2
com.apple.driver.AppleIRController     312
com.apple.driver.Oxford_Semi     3.0.1
com.apple.iokit.SCSITaskUserClient     3.2.0
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless     1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib     1.0.0d1
com.apple.BootCache     33
com.apple.driver.XsanFilter     404
com.apple.iokit.IOAHCIBlockStorage     2.0.3
com.apple.driver.AppleHPET     1.6
com.apple.driver.AppleIntelPIIXATA     2.5.1
com.apple.driver.AppleAHCIPort     2.3.0
com.apple.driver.AppleFWOHCI     4.8.9
com.apple.driver.AppleUSBHub     4.5.0
com.apple.driver.AppleSmartBatteryManager     161.0.0
com.apple.iokit.AppleYukon2     3.2.2b1
com.apple.driver.AirPortBrcm43224     501.36.15
com.apple.driver.AppleUSBUHCI     4.4.5
com.apple.driver.AppleEFINVRAM     1.5.0
com.apple.driver.AppleRTC     1.5
com.apple.driver.AppleUSBEHCI     4.5.8
com.apple.driver.AppleACPIButtons     1.5
com.apple.driver.AppleSMBIOS     1.8
com.apple.driver.AppleACPIEC     1.5
com.apple.driver.AppleAPIC     1.5
com.apple.driver.AppleIntelCPUPowerManagementClient     193.0.0
com.apple.nke.applicationfirewall     3.2.30
com.apple.security.quarantine     1.3
com.apple.driver.AppleIntelCPUPowerManagement     193.0.0
com.apple.driver.AppleHIDKeyboard     160.7
com.apple.driver.AppleMultitouchDriver     231.4
com.apple.driver.IOBluetoothHIDDriver     4.0.5f11
com.apple.kext.triggers     1.0
com.apple.driver.DspFuncLib     2.2.0f3
com.apple.iokit.IOFireWireIP     2.2.4
com.apple.iokit.IOSurface     80.0.2
com.apple.iokit.IOSerialFamily     10.0.5
com.apple.iokit.IOAudioFamily     1.8.6fc17
com.apple.kext.OSvKernDSPLib     1.3
com.apple.driver.ApplePolicyControl     3.0.16
com.apple.driver.AppleHDAController     2.2.0f3
com.apple.iokit.IOHDAFamily     2.2.0f3
com.apple.driver.AppleSMC     3.1.3d8
com.apple.driver.IOPlatformPluginLegacy     5.0.0d0
com.apple.driver.IOPlatformPluginFamily     5.1.0d17
com.apple.driver.AppleGraphicsControl     3.0.16
com.apple.driver.AppleBacklightExpert     1.0.3
com.apple.iokit.IONDRVSupport     2.3.2
com.apple.iokit.IOGraphicsFamily     2.3.2
com.apple.driver.AppleUSBBluetoothHCIController     4.0.5f11
com.apple.iokit.IOBluetoothFamily     4.0.5f11
com.apple.iokit.IOSCSIBlockCommandsDevice     3.2.0
com.apple.iokit.IOUSBHIDDriver     4.4.5
com.apple.driver.AppleUSBMergeNub     4.5.3
com.apple.driver.AppleUSBComposite     4.5.8
com.apple.iokit.IOFireWireSerialBusProtocolTransport     2.1.0
com.apple.iokit.IOFireWireSBP2     4.2.0
com.apple.iokit.IOSCSIMultimediaCommandsDevice     3.2.0
com.apple.iokit.IOBDStorageFamily     1.6
com.apple.iokit.IODVDStorageFamily     1.7
com.apple.iokit.IOCDStorageFamily     1.7
com.apple.iokit.IOATAPIProtocolTransport     3.0.0
com.apple.iokit.IOSCSIArchitectureModelFamily     3.2.0
com.apple.iokit.IOATAFamily     2.5.1
com.apple.iokit.IOAHCIFamily     2.0.8
com.apple.iokit.IOFireWireFamily     4.4.5
com.apple.iokit.IOUSBUserClient     4.5.8
com.apple.iokit.IO80211Family     420.3
com.apple.iokit.IONetworkingFamily     2.1
com.apple.driver.AppleEFIRuntime     1.5.0
com.apple.iokit.IOUSBFamily     4.5.8
com.apple.iokit.IOHIDFamily     1.7.1
com.apple.iokit.IOSMBusFamily     1.1
com.apple.security.sandbox     177.5
com.apple.kext.AppleMatch     1.0.0d1
com.apple.security.TMSafetyNet     7
com.apple.driver.DiskImages     331.6
com.apple.iokit.IOStorageFamily     1.7.1
com.apple.driver.AppleKeyStore     28.18
com.apple.driver.AppleACPIPlatform     1.5
com.apple.iokit.IOPCIFamily     2.6.8
com.apple.iokit.IOACPIFamily     1.4
Model: MacBook3,1, BootROM MB31.008E.B02, 2 processors, Intel Core 2 Duo, 2.2 GHz, 4 GB, SMC 1.24f3
Graphics: Intel GMA X3100, GMA X3100, Built-In, 144 MB
Memory Module: BANK 0/DIMM0, 2 GB, DDR2 SDRAM, 667 MHz, 0x0000000000000000, 0x3235365836344D2D363745004D5400000000
Memory Module: BANK 1/DIMM1, 2 GB, DDR2 SDRAM, 667 MHz, 0x0000000000000000, 0x3235365836344D2D363745004D5400000000
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x88), Broadcom BCM43xx 1.0 (5.10.131.36.15)
Bluetooth: Version 4.0.5f11, 2 service, 18 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en1
Serial ATA Device: ST9120822AS, 120,03 GB
Parallel ATA Device: HL-DT-ST DVDRW  GSA-S10N
USB Device: Built-in iSight, apple_vendor_id, 0x8501, 0xfd400000 / 3
USB Device: hub_device, 0x0409  (NEC Corporation), 0x005a, 0xfd100000 / 2
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8205, 0x1a100000 / 2
USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x022a, 0x5d200000 / 3
USB Device: IR Receiver, apple_vendor_id, 0x8242, 0x5d100000 / 2
FireWire Device: eGo HDD, Iomega, 400mbit_speed
Reply
0 Kudos
dariusd
VMware Employee
VMware Employee
Jump to solution

Hi P@olo,

Thanks for that update.  I am a bit unclear on one thing: Does Fusion really crash every time you try to use it after the 10.7.4 upgrade (as you mentioned in the thread title), or can you still sometimes use it?  One of your earlier comments gave me the impression that it might still be working occasionally, but I'd like to double-check rather than make an incorrect assumption, as it's a crucial factor in determining where the problem is.

Thanks for your patience,

--

Darius

Reply
0 Kudos
P_2
Contributor
Contributor
Jump to solution

Sorry Darius for misunderstanding: it doesn't crash everytime!
The very first launches after update to 10.7.4 were really disastrous: Fusion allowed me to work only after a reboot (due to OS crash). Now the situation seems to be a little better (I don't know why....) and this crash occurs after some days in which I could use Fusion normally.
In these days I provided the update of VMware Tools for all my VMs.
Bye.
Reply
0 Kudos
dariusd
VMware Employee
VMware Employee
Jump to solution

Hi again P@olo,

OK, that's good to know.

Could I ask you to temporarily move your Iomega eGo external hard drive to use the USB connector instead of Firewire, or disconnect the drive from the host computer completely if you don't need it connected all the time?  It is possible that the Firewire device or the host's Firewire port is causing the problem... I'd consider it unlikely, to be honest, but we should try to eliminate the possibility if we can.

Thanks again for your patience.  Your answers are helping us to steadily move forwards in solving this mystery.  :smileycool:

Cheers,

--

Darius

Reply
0 Kudos
P_2
Contributor
Contributor
Jump to solution

Hi Darius.
I moved my Iomega HD to a USB port. I can't keep it disconnected because it contains Time Machine's backup and VMs files.
I prefer to work with this HD on FW port because of I need more speed and also because I have only 2 USB ports.
This configuration worked properly untill update to 10.7.4: could it be a coincidence??
Anyway I'm going to make a test as you suggested, hoping to find a solution for this issue that do not force me to work with USB port.
Reply
0 Kudos
P_2
Contributor
Contributor
Jump to solution

I moved HD to USB port, but unsuccessfully!
The OS crash happended again! This time it was the third or fourth launch of Fusion after last reboot.
Reply
0 Kudos
dariusd
VMware Employee
VMware Employee
Jump to solution

Thanks for doing that experiment, P@olo.  I guess you can move the drive back to the Firewire port again now that we know that it did not affect the problem.

Next step: Could you please follow these instructions to run Apple Hardware Test on your MacBook and see if that reports any errors?  At this point, I suspect that one of the memory modules in your MacBook is defective.  It's still possible that it's a software problem, but the panic reports you have provided indicate a very specific failure that I have not seen anywhere else, so at this point it would seem most likely to be a hardware problem unique to your MacBook.

The nature of the failure is such that an AHT (Apple Hardware Test) failure might indicate that a hardware problem exists, but an AHT pass will not necessarily prove that the system is OK... it might require many runs of AHT (and perhaps a different, more intensive memory test) to rule out defective RAM as the cause.

Hopefully the document I linked above will explain the AHT process, but do feel free to ask if there's anything you're not sure about.

Cheers,

--

Darius

Reply
0 Kudos
P_2
Contributor
Contributor
Jump to solution

Hi Darius!
You seem to have hit the target! The AHT's result indicate that one of my RAM module is damaged. the error code:
4MEM/1/4000000: 618088.
If I change the position of modules the error becomes:
4MEM/5/4000000: 618c88.
So the problem was that I normally do not use that memory area and when I launch Fusion the request of memory is so high that it involes the corrupted  partition. Is it?
Now I think I will buy a couple of new modules in order to be sure that everything will be ok.
Reply
0 Kudos