Dual Quad Core - freeze after sleep

Question

Level 1

0 points

Dual Quad Core - freeze after sleep

Dual Quad 2.8GHz early '08

besides the restart-after-sleep Problem my MacPro sometimes freeze after awake from sleep. It happend twice since I own the Pro. Because of the restart-after-sleep issue I happen to send it to sleep quite often, so maybee it was triggered by sleeping to often, who knows.

The machine comes up as usual, then upon the first app you try to access the UI just stalls (showing the spinning beachball). The only possible solution is to hard-reset and reboot.

One time I was "lucky" and I had a Terminal and Activity Monitor running. I think otherwise you would just see the spinning beachball before rebooting.

I have a Screenshot made with my digicam: http://cachescrubber.org/IMG_1225.jpg

It was still possible to focus the Terminal window and the shell was still accepting commands. Every command faild to execute with "Cannot allocate memory". You see 90% of 6GB RAM free in the Activity Monitor window ....

There is no ChrashReporter coming which is usually the case after a crash. The only error message I found in the logs is

disk0s2: memory allocation error.

I have a call open with apple care regarding the restart-after-sleep, so I allready did a lot of tests (AHT, passed, memtest|OSX, passed) and of course SMC/NVRAM resets.

The OSX instance running had Parallels and Vmware installed (both installing a bunch of kernel extensions). Otherwise it's 10.5.2 + all updates (incl. ATI firmware update).

Maybee other experiencing a freeze after sleep should check their syslog for "memory allocation error".

I'm unsure wether this is another OS/Firmware issue or in deed a hardware problem. I must decide this week wether I try to get replacement hardware (via DOA) or just wait for a possible software update. What do you think?

Mac Pro, Mac OS X (10.5.2), Dual 2.8GHz, 6GB RAM, ATI Radeon HD 2600 XT

Posted on Mar 25, 2008 6:13 AM

Reply

Answer 1

islk350

Level 1

65 points

Mar 25, 2008 6:34 PM in response to Lars Uffmann

Gotta try it without parallels and vmware... other than the reboot from sleep. See if the hang you're seeing goes away... I doubt the parallels / vmware is optimized for this platform and sleep issues will be found...

Reply

Answer 2

Lars Uffmann Author

Level 1

0 points

Mar 31, 2008 12:07 AM in response to Lars Uffmann

I had another freeze like I described above. This time vmare was actually running. I got a "cannot allocate memory" error in Terminal and vmware. All other apps just stalled and showed the spinning beachball. This time I did not find the "dis02s2 memory" errors in syslog, in fact the whole time between wake and the forced restart did not leave any trace in the logs.

The EFI Firmware upgrade was allready applied. It seems, like the memory subsystem could not be initialized from sleep under some conditions.

Reply

Answer 3

doublep

Level 1

9 points

Mar 31, 2008 3:14 AM in response to Lars Uffmann

Hello,

I was having freezes similar to what you described. I discovered that these freezes were linked to my boot drive (an initial model of Raptor 150 GB - version Lr0). I have since cloned this boot drive onto a new Samsung drive. And now, these freezes after the computer wake-up have totally disappeared.

Reply

Answer 4

Lars Uffmann Author

Level 1

0 points

Mar 31, 2008 7:49 AM in response to doublep

interesting - I never though of the boot-drive as the root-cause for my problem.

I use a Samsung F1 1TB as my boot-drive.

How did you discovered it was the hard disk causing your problem?

Reply

Answer 5

Lars Uffmann Author

Level 1

0 points

Apr 1, 2008 11:22 PM in response to Lars Uffmann

I happend again - 5 times total now.

After the forced reboot I had lots of files and directories in my home directory with wrong ownership and permissions (for example Library/Preferences was owned by root/wheel). Arghhh.

Some possibilities / thoughts:

it hapend before the firmware update.

virtualization (vmware and / or parallels) Bugs: this is what I'm trying right now. I disabled (not deinstalled) both suites by hacking their startup items respectively lauchdaemon configuration. No vmware or parallels kernel extension or daemon processes are running.

hard disk: so far I have no obvious problems with the Samsung F1, but I found reports posted here that Samsung Spinpoints are not working in a raid setup (the raid gets rebuild all the time, connection to the drives is getting lost).

Yet another OS X bug: search the apple discussions for "disk0s2: memory allocation error". It pops up quit often, almost always together with a freeze / crash.

Reply

Answer 6

fat tom

Level 1

5 points

Apr 2, 2008 12:46 PM in response to Lars Uffmann

Same problem here. Always after wake from sleep.

Machine will kernel panic (cascading black sceen of death) or freeze at random system actions. Mostly with file system access that requires loginwindow (such as software updates), or attaching a USB device (previous post here: http://discussions.apple.com/thread.jspa?threadID=1341342&tstart=0).

Nothing in the crash logs.

Occasionally I'll see "disk0s2: memory allocation error" in system.log. Not always. Never any other errors in system.log before a crash though.

I have VMWare 1.1 installed.

I have Samsung, Hitachi, and WD drives. Makes no difference on which the system is installed.

First noticed the problem after 10.5.1.

Problem is more frequent after update to 9.2.2.

Reply

Answer 7

Apr 2, 2008 2:18 PM in response to fat tom

I'll throw my hat in the ring too. I get spinning beach balls when waking from sleep after installing the firmware update. I have to hard reset and reboot to fix it.

Question: it looks like everyone experiencing this problem has VMWare or Parallels installed. Is anyone experiencing this issue WITHOUT virtualization software installed? Has anyone tried removing the software to see if the problem persists?

I'll do that when I get home. I never really use Windows anyhow, and was just trying VMWare out. I don't mind uninstalling it to see if it's causing the problem.

Reply

Answer 8

Apr 3, 2008 6:39 AM in response to s_w_i_t_t_e_r_s

Just wanted to report that I uninstalled VMWare Fusion, and this morning my Mac Pro woke up without a hiccup. No spinning beach ball, no freeze, no hard reset.

It appears that for me at least, the problem was related to VMWare.

Anyone else tried this?

Reply

Answer 9

Lars Uffmann Author

Level 1

0 points

Apr 3, 2008 8:31 AM in response to s_w_i_t_t_e_r_s

The biggest problem I have is that this is not as easyly reproducable then for example the restart-after-sleep thing. I had a total of five freezes, but also several days without problems.

I currently also disabled the vmware launchd item, so none of the vmware kernel extension or deamons are running. So far no freeze, but ...

If anyone is experiencing problems like we describe here:

Please try to have a Terminal.app window open before you send the machine to sleep. Then, if it freezes after wakeup you should be able to type commands into the running shell. All attempts to execute a command will result in "Cannot allocate memory". This would be very interesting to know, because otherwise a freeze like I described leaves no traces in the system log.

Reply

Answer 10

Lars Uffmann Author

Level 1

0 points

Apr 6, 2008 6:37 AM in response to Lars Uffmann

Ok, it happend again.

This time vmware/parallels were definitely not installed.

I had a root shell running, it was still possible to execute some commands, incl. "dmesg" (output below). I was still able to access the second SATA drive (stock Samsung) to save the dmesg output and execute commands from there. I have macports installed on the second drive, mounted below /opt. It was not possible to access any files on the boot drive (samsung Spinpont F1 1TB, as mentioned earlier).

After reboot I checked ErrNo #12 in /usr/include/sys/errno.h:

#define ENOMEM 12 /* Cannot allocate memory */

So I still have no clue wether the drive is faulty or if the problem is within the firmware / OS X kernel failing to initialize the memory subsystem after wake from sleep.

So, the next thing to try is to move everything back to the 320 GB Seagate drive and see.

-----
IOBlockStorageDriver[IOBlockStorageDriver]; executeRequest: request failed to start!
disk0s5: resource shortage.
0 [Level 3] [ReadUID 0] [Facility com.apple.system.fs] [ErrType IO] [ErrNo 12] [IOType Read] [PBlkNum 201800] [LBlkNum 168] [FSLogMsgID 247033654] [FSLogMsgOrder First]
0 [Level 3] [ReadUID 0] [Facility com.apple.system.fs] [DevNode /dev/disk0s5] [MountPt /Users] [FSLogMsgID 247033654] [FSLogMsgOrder Last]
IOBlockStorageDriver[IOBlockStorageDriver]; executeRequest: request failed to start!
disk0s5: resource shortage.
0 [Level 3] [ReadUID 0] [Facility com.apple.system.fs] [ErrType IO] [ErrNo 12] [IOType Read] [PBlkNum 201800] [LBlkNum 168] [FSLogMsgID 2136332915] [FSLogMsgOrder First]
0 [Level 3] [ReadUID 0] [Facility com.apple.system.fs] [DevNode /dev/disk0s5] [MountPt /Users] [FSLogMsgID 2136332915] [FSLogMsgOrder Last]
IOBlockStorageDriver[IOBlockStorageDriver]; executeRequest: request failed to start!
disk0s5: resource shortage.
0 [Level 3] [ReadUID 0] [Facility com.apple.system.fs] [ErrType IO] [ErrNo 12] [IOType Read] [PBlkNum 201800] [LBlkNum 168] [FSLogMsgID 2101166086] [FSLogMsgOrder First]
0 [Level 3] [ReadUID 0] [Facility com.apple.system.fs] [DevNode /dev/disk0s5] [MountPt /Users] [FSLogMsgID 2101166086] [FSLogMsgOrder Last]
IOBlockStorageDriver[IOBlockStorageDriver]; executeRequest: request failed to start!
disk0s5: resource shortage.
0 [Level 3] [ReadUID 0] [Facility com.apple.system.fs] [ErrType IO] [ErrNo 12] [IOType Read] [PBlkNum 201800] [LBlkNum 168] [FSLogMsgID 1346684118] [FSLogMsgOrder First]
0 [Level 3] [ReadUID 0] [Facility com.apple.system.fs] [DevNode /dev/disk0s5] [MountPt /Users] [FSLogMsgID 1346684118] [FSLogMsgOrder Last]
IOBlockStorageDriver[IOBlockStorageDriver]; executeRequest: request failed to start!
disk0s5: resource shortage.
0 [Level 3] [ReadUID 0] [Facility com.apple.system.fs] [ErrType IO] [ErrNo 12] [IOType Read] [PBlkNum 201800] [LBlkNum 168] [FSLogMsgID 1834323399] [FSLogMsgOrder First]
0 [Level 3] [ReadUID 0] [Facility com.apple.system.fs] [DevNode /dev/disk0s5] [MountPt /Users] [FSLogMsgID 1834323399] [FSLogMsgOrder Last]
IOBlockStorageDriver[IOBlockStorageDriver]; executeRequest: request failed to start!
disk0s2: resource shortage.
0 [Level 3] [ReadUID 0] [Facility com.apple.system.fs] [ErrType IO] [ErrNo 12] [IOType Read] [PBlkNum 12556576] [LBlkNum 0] [FSLogMsgID 1661513145] [FSLogMsgOrder First]
0 [Level 3] [ReadUID 0] [Facility com.apple.system.fs] [DevNode /dev/disk0s2] [MountPt > [Path /System/Library/CoreServices/ReportCrash] [FSLogMsgID 1661513145] [FSLogMsgOrder Last]
IOBlockStorageDriver[IOBlockStorageDriver]; executeRequest: request failed to start!
disk0s5: resource shortage.
0 [Level 3] [ReadUID 0] [Facility com.apple.system.fs] [ErrType IO] [ErrNo 12] [IOType Read] [PBlkNum 222344] [LBlkNum 1452] [FSLogMsgID 526213311] [FSLogMsgOrder First]
0 [Level 3] [ReadUID 0] [Facility com.apple.system.fs] [DevNode /dev/disk0s5] [MountPt /Users] [FSLogMsgID 526213311] [FSLogMsgOrder Last]
IOBlockStorageDriver[IOBlockStorageDriver]; executeRequest: request failed to start!
disk0s5: resource shortage.
0 [Level 3] [ReadUID 0] [Facility com.apple.system.fs] [ErrType IO] [ErrNo 12] [IOType Read] [PBlkNum 219864] [LBlkNum 1297] [FSLogMsgID 612641497] [FSLogMsgOrder First]
0 [Level 3] [ReadUID 0] [Facility com.apple.system.fs] [DevNode /dev/disk0s5] [MountPt /Users] [FSLogMsgID 612641497] [FSLogMsgOrder Last]
IOBlockStorageDriver[IOBlockStorageDriver]; executeRequest: request failed to start!
disk0s2: resource shortage.
0 [Level 3] [ReadUID 0] [Facility com.apple.system.fs] [ErrType IO] [ErrNo 12] [IOType Read] [PBlkNum 27608680] [LBlkNum 0] [FSLogMsgID 616317556] [FSLogMsgOrder First]
0 [Level 3] [ReadUID 0] [Facility com.apple.system.fs] [DevNode /dev/disk0s2] [MountPt > [Path /Library/Preferences/.GlobalPreferences.plist] [FSLogMsgID 616317556] [FSLogMsgOrder Last]
-----

Reply

Answer 11

DSDNYC

Level 1

0 points

May 29, 2008 3:30 PM in response to Lars Uffmann

Interesting Reading. Same problem here. I "uninstalled" Parallels a few weeks ago, and then the problem began in earnest. Now, viewing files in cover flow often brings my machine to a standstill, as does waking the machine from sleep. Diskwarrior found little and failed to fix anything. Any clues or advice much appreciated.

Reply