Pablo Sanchez wrote on 04/02/2012 10:49 AM: > [ Comments below, in-line ] > > On 04/02/2012 10:46 AM, Phil Schaffner wrote: >> My system was tested for bad memory and other problems by our support >> technicians. > How long did the run the memory tests? Depending on the amount of > memory, I've had to run the test for many hours. > > I'd confirm they went through at least one iteration of the tests. > > But it smells like it may not be a memory issue. :) > > Cheers, The tech who ran the diagnostics has moved on, so I decided to do it myself to verify. The begins the strange chain of events. :-)
1. Downloaded the latest memtest86+ ISO and burned to CD after verifying that it should work on the Mac Pro. 2. Shut down VirtualBox clients and stopped VB. 3. Initiated a reboot and instead of a clean boot got the dreaded many-languages box saying that an error had occurred and I must hit the power button. 4. Forced power down and booted to the memtest86+ ISO which ran overnight, completing 5+ passes and finding no errors. 5. Rebooted to OS-X and got a request to allow sending a panic report. Captured the text of the error and I see: Interval Since Last Panic Report: 11 sec Panics Since Last Report: 4 Anonymous UUID: 2370895F-3CEE-485F-9800-22A6DCA8606C ... snip register dumps and backtrace ... BSD process name corresponding to current thread: ssh Mac OS version: 10K549 Kernel version: Darwin Kernel Version 10.8.0: Tue Jun 7 16:32:41 PDT 2011; root:xnu-1504.15.3~1/RELEASE_X86_64 System model name: MacPro3,1 (Mac-F42C88C8) System uptime in nanoseconds: 84921356318831 unloaded kexts: com.apple.filesystems.cd9660 1.4.1 (addr 0xffffff7f80e3e000, size 0x32768) - last unloaded 73873096132064 loaded kexts: org.virtualbox.kext.VBoxNetAdp 4.1.10 org.virtualbox.kext.VBoxNetFlt 4.1.10 com.Symantec.kext.SAVAPComm 11.0.6 org.virtualbox.kext.VBoxUSB 4.1.10 org.virtualbox.kext.VBoxDrv 4.1.10 com.apple.filesystems.cd9660 1.4.1 - last loaded 84894169883714 com.apple.filesystems.autofs 2.1.0 com.apple.driver.AppleHWSensor 1.9.3d0 com.apple.driver.AppleUpstreamUserClient 3.5.7 ... snip other stuff apparently not VB related ... So, apparently VB was not the running thread, ssh was, but kexts were still loaded. Seems inconclusive. 6. Checked Console logs and found a VirtualBox Crash report from yesterday morning, but no Panic reports logged. I recall no problems at the time, 8 hours or so before the shutdown, nor the rest of the day. That and the full log from above available on request. 7. Started VB and got a notice a new version was available. Clicked the link and downloaded VirtualBox-4.1.12-77245-OSX.dmg to the desktop. 8. VB was shown as still running on the task bar, but did not appear on any desktop. Attempted to close it on the task bar but to no effect. Attempted to reboot, but was stopped because VB was still running. Used "Force quit..." to kill it and rebooted. 9. Started VB and it seemed to run normally, including starting a VM. Shut down VM and exited VB cleanly. 10. Installed the update. No problems encountered yet with 4.1.12, but has only been running a few minutes. This message is coming from a CentOS-6.2 VM. Let me know if you would like to see the logs or have any other tests done. Phil ------------------------------------------------------------------------------ Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev _______________________________________________ VBox-users-community mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/vbox-users-community
