[El Maestro]

Hi all,

I came across this in my system.log tonight:

Dec 18 20:21:45 localhost kernel[0]: AMS::clearInterrupt ERROR: failed to write the bytes, retval = 0xe00002ed
Dec 18 20:21:45 localhost kernel[0]: AMS::freeFallIntHandler ERROR: failed to clear the interrupt, retval = 0xe00002ed
Dec 18 20:21:45 localhost kernel[0]: IOI2CController::clientReadI2C cmd key:101f, B:1, A:b0 S:0, L:1, M:3 status:0xe00002ed
Dec 18 20:21:45 localhost kernel[0]: -IOI2CController::clientReadI2C status = 0xe00002ed
Dec 18 20:21:45 localhost kernel[0]: AMS::readBytes ERROR: failed to read from I2C
Dec 18 20:21:45 localhost kernel[0]: AMS::checkResult ERROR: failed to read the bytes
Dec 18 20:21:45 localhost kernel[0]: AMS::writeCommand ERROR: failed to check the result code
Dec 18 20:21:45 localhost kernel[0]: AMS::startApp ERROR: failed to send kStartAppComm
Dec 18 20:21:45 localhost kernel[0]: AMS::start ERROR: startApp failed

I think based on some googling and whatnot that "AMS" refers to the Apple Motion Sensor. I have a 17" PB G4 1.67, which is equipped with that feature. That's the only thing I could think of for "AMS", but it could certainly be something else.

My PB has functioned fine since I got it last February. Is this anything to worry about, and regardless, any ideas as to what it is?

[Tesseract]

Most of the entries in system.log are intended for programmers. They may be harmless debugging messages or they may point they may point to something more serious. But unless you're a programmer working on the AMS-related code of OS X (or, I suppose, a repair technician trying to diagnose a broken AMS), there's not much you can do about them. I wouldn't worry about too much of what you see in system.log - is there a specific reason you were looking in there?

As for what it is, it does indeed look like something to do with the motion sensor, based on "AMS" and "I2C" appearing in the messages. I have no idea whether those messages are normal or not. If your PowerBook is working fine and especially if the messages aren't recurring, I wouldn't be too concerned.

[El Maestro]

I was cutting/pasting a panic log from a few weeks ago when I had a bad stick of RAM. I clicked on the other logs to see what they were and I saw that.

Thanks for the reply. I don't think I'll sweat it, I was just curious. I certainly won't drop my PB to see if the AMS works!

[Mat]

I also encountered this problem, and this forum was the only place google found discussing it.

Deleting /System/Library/Extensions.mkext and
/System/Library/Extensions.kextcache, then rebooting, fixed the problem.

It's pretty likely that AMS is not working at all when these messages are generated at startup.