OS X (10.5.6) and the "AppleFWOHCI_Async" coma

The past two days after updating OS X, I find my computer absolutely unresponsive to any attempt to wake the machine after overnight sleep. I have to force quit the machine, then restart. A check of the system log reveals 80MB of the following two repeated entries (18-20 times a second for the hours I thought the machine was sleeping!):
Dec 21 00:02:18 NewYorkCity kernel[0]: AppleFWOHCI_AsyncTransmit::waitForDMA - context not going inactive.
Dec 21 00:02:18 NewYorkCity kernel[0]: AppleFWOHCI_AsyncReceive::waitForDMA - context not going inactive.
Suspecting a FireWire issue, I reset the FW ports (fixed temporarily, but most likely because of the system restart). During the day, only the "transmit" variety of the log entry appears, and only once every few minutes; then at some point after a few hours of running, the entries begin to cascade as described above. Once the cascade starts (and the machine is still responsive) a check of FW status in Apple System Profiler reveals a message (in red letters) that FW status cannot be reported. At some point after a few hours of cascading log entries, normal sleep or shutdown are impossible -- the screen goes blank as expected, but the machine is neither sleeping nor off, but in a comatose state -- a system reset (hold the power button for 10 seconds) and a restart are required to regain control.
From reading other threads, I've tried resetting PRAM and NVRAM -- the fix is temporary (and likely just due to the related system restart). I've tried reapplying the 10.5.6 combo updater with no improvement in behavior.
It seems that until Apple provides a more permanent fix, those of us who have this issue will just have to periodically force a shutdown and restart for temporary relief. Logging out and back in is not enough to stop the cascading log entries -- a system reboot is required.
I'm hoping somebody stumble across a fix before too long -- I'm getting ready to go back to 10.5.5 before too long.
Message was edited by: Brie Fly

Hi
I'm getting these messages too. But I have no directly attached drives. Only via AEBS. Having issues with sleep mode and waking up HDDs on the AEBS (see http://discussions.apple.com/thread.jspa?threadID=1840492&tstart=0). Even if I unmount all drives the messages keep on rolling by...
I had my iMac crash once while it was in sleep mode over night really had issues getting it running again. Didn't want to react to nothing (but finally did). Might have had something to do with this. This has never happened to me with any Mac that I've so far owned (poweroutage was checked and there was none).
Cheers Oliver

Similar Messages

Maybe you are looking for