deciphering error "MacAsyncDevice.cpp:229" in console log

[pendolino]

i've been trying to figure out what in the world the following message means or what generated it but to no avail. no amount of googling or digging has revealed anything and this is the last step before i call apple.

to give a bit of background here, i recently migrated using the assistant from a black 2008 macbook to my new aluminum macbook pro 13 and that in itself went smoothly but since then, my macbook hangs without even the SBB and just a frozen cursor for 10 to 20 seconds and on checking the console i find multiple (20 or so?) successive instances of the following:

23/Jul/09 23-Jul-09 14:42 kernel /drv/ MacAsyncDevice.cpp:229 Wait for host_wait_work_complete_async_device (02:00) finished with timeout.

can anyone out there figure out what could be causing this? i've gone through the general troubleshooting steps including creating another account and have pretty much concluded its a software error.

UPDATE: here's another error that i feel may be related to the one above and has been also happening - although less frequently - since i migrated to the new machine:

"23/Jul/09 23-Jul-09 16:26 /usr/libexec/hidd[40] IOHIDEventQueueEnqueue: Error enqueuing memory. (0xe00002e8) "

 

[BobZune]

Sounds like a human interface device (HID) is acting up -- can be a mouse/trackpad driver problem or a graphic driver issue (the machine waits for a while for a response and them times-out). If the software is not up to date, I'd recommend doing so (preferably using the latest combo updater downloaded from the Apple site rather than using the software update feature). The AsyncDevice can be the same, or some other external device (so if you have any connected, disconnect and see if the problem goes away).

You can also try an external mouse if it is not inconvenient and see if this problem happens. [Just curious: Is this all on the new machine or the older one? Did the machine ever work correctly?]

 

[pendolino]

@bobzune -

i dont use any external devices and the machine is completely stock as received from apple.

and yes, this problem i have only been experiencing on the new machine. could it possibly be a hardware incompatibility with some of the older software that was moved over with migration assistant?

all Apple software is always up to date. i check regularly.

what i guess i might try is set up another user account and use it for a while to see if the problems show up there.