paddyiyer

Q: kernel errors after updating to 10.7.4

Hello Gurus,

Just now, I updated my iMac to 10.7.4, I am seeing errors in console log .

I tried restarting, resetting SMC and PRAM and it keeps showing up when I restart.

I tried repairing disk as suggested by one member and it did not help.

 

 

Anyone experiencing similar issues,

Thanks,

Paddy

 

BTW, I updated the OS on my MacBookPro and I don't see these errors.

 

5/9/12 7:20:23.000 PM kernel: SMC::smcReadKeyAction ERROR IN0C kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff80128cf000

5/9/12 7:20:23.000 PM kernel: SMC::smcReadKeyAction ERROR Ie1S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff80128cf000

5/9/12 7:20:23.000 PM kernel: SMC::smcReadKeyAction ERROR IB0R kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff80128cf000

5/9/12 7:20:23.000 PM kernel: SMC::smcReadKeyAction ERROR ICAC kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff80128cf000

5/9/12 7:20:23.000 PM kernel: SMC::smcReadKeyAction ERROR IC2C kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff80128cf000

5/9/12 7:20:23.000 PM kernel: SMC::smcReadKeyAction ERROR Ie3S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff80128cf000

5/9/12 7:20:23.000 PM kernel: SMC::smcReadKeyAction ERROR IeBS kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff80128cf000

5/9/12 7:20:23.000 PM kernel: SMC::smcReadKeyAction ERROR ID0R kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff80128cf000

5/9/12 7:20:23.000 PM kernel: SMC::smcReadKeyAction ERROR IO0Z kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff80128cf000

5/9/12 7:20:23.000 PM kernel: SMC::smcReadKeyAction ERROR IG0C kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff80128cf000

5/9/12 7:20:23.000 PM kernel: SMC::smcReadKeyAction ERROR IF0R kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff80128cf000

5/9/12 7:20:23.000 PM kernel: SMC::smcReadKeyAction ERROR Ip1C kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff80128cf000

5/9/12 7:20:23.000 PM kernel: SMC::smcReadKeyAction ERROR IH2Z kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff80128cf000

5/9/12 7:20:23.000 PM kernel: SMC::smcReadKeyAction ERROR IM2S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff80128cf000

5/9/12 7:20:23.000 PM kernel: SMC::smcReadKeyAction ERROR ICBB kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff80128cf000

5/9/12 7:20:23.000 PM kernel: SMC::smcReadKeyAction ERROR IMAS kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff80128cf000

5/9/12 7:20:23.000 PM kernel: SMC::smcReadKeyAction ERROR IH4Z kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff80128cf000

5/9/12 7:20:24.000 PM kernel: SMC::smcReadKeyAction ERROR IC1C kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff80128cf000

5/9/12 7:20:24.000 PM kernel: SMC::smcReadKeyAction ERROR IBAC kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff80128cf000

5/9/12 7:20:24.000 PM kernel: SMC::smcReadKeyAction ERROR Ie2S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff80128cf000

5/9/12 7:20:24.000 PM kernel: SMC::smcReadKeyAction ERROR IC0R kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff80128cf000

5/9/12 7:20:24.000 PM kernel: SMC::smcReadKeyAction ERROR IeAS kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff80128cf000

5/9/12 7:20:24.000 PM kernel: SMC::smcReadKeyAction ERROR IN1C kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff80128cf000

5/9/12 7:20:24.000 PM kernel: SMC::smcReadKeyAction ERROR IN0R kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff80128cf000

5/9/12 7:20:24.000 PM kernel: SMC::smcReadKeyAction ERROR Ie4S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff80128cf000

5/9/12 7:20:24.000 PM kernel: SMC::smcReadKeyAction ERROR ICBC kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff80128cf000

5/9/12 7:20:24.000 PM kernel: SMC::smcReadKeyAction ERROR IN2R kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff80128cf000

5/9/12 7:20:24.000 PM kernel: SMC::smcReadKeyAction ERROR Ip0C kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff80128cf000

5/9/12 7:20:24.000 PM kernel: SMC::smcReadKeyAction ERROR IP0R kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff80128cf000

5/9/12 7:20:24.000 PM kernel: SMC::smcReadKeyAction ERROR IG1C kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff80128cf000

iMac (27-inch Mid 2011), Mac OS X (10.7.3)

Posted on May 9, 2012 9:26 PM

Close

Q: kernel errors after updating to 10.7.4

  • All replies
  • Helpful answers

first Previous Page 3 of 3
  • by tod1212,

    tod1212 tod1212 May 13, 2012 9:57 AM in response to gravedigger1202
    Level 1 (0 points)
    May 13, 2012 9:57 AM in response to gravedigger1202

    just a short feedback on my side:

    i finally fixed my chrashing problems with a clean reinstall of lion using hd recovery (quite handy by the way).

    restored using a backup from my time capsule.

    all is fine now.

     

    just to let you all know:

    i just got a very friendly call directly from "the mothership" in california (on a sunday).

    (for your info: i'm living in germany!)

    some nice apple employee asked some questions about my problems.

    i had to tell him that all was fine since reinstall.

    anyway, he told my about a programm called "FIPS" which might be causing problems with 10.7.4 (i did not use it).

    so: apple DOES monitor this forums

  • by Mojo66,

    Mojo66 Mojo66 May 13, 2012 5:24 PM in response to budsimrin
    Level 1 (59 points)
    May 13, 2012 5:24 PM in response to budsimrin

    budsimrin wrote:

     

    Same problem here. I went to Activity Monitor and quit smcFanControl and the problem immediately stopped. From the rest of this thread, it sounds like Apple must have changed the fan control interface in OS 10.7.4 and just about any app that reads the fan gets this error.

    I'm getting the same error message, every 3 seconds, really annoying and totally useless in my opinion, who cares about logging access to a sensor that doesn't exist?? Anyway, I've dropped a note at the devoper's home page http://www.eidac.de/?p=207 maybe you can, too.

  • by digitalidea,

    digitalidea digitalidea Jun 1, 2012 2:35 AM in response to Mojo66
    Level 1 (0 points)
    Jun 1, 2012 2:35 AM in response to Mojo66

    In my case CPUled app was the root cause; after stopping it the message was gone

  • by frankbullitt,

    frankbullitt frankbullitt Jun 5, 2012 5:16 AM in response to paddyiyer
    Level 1 (0 points)
    Jun 5, 2012 5:16 AM in response to paddyiyer

    I updated to 10.7.4 on Sunday and yesterday my MBP froze (it didn' actually froze, I could move the cursor but it looked weird an I couldn'd do anything), so I forced it to shutdown. Then it got stucked at the grey screen, with the wheel spinning until it stopped and nothing else. Then I was able to boot in safe mode, but this was my screen when i did it.

    IMG00062-20120604-2357.jpg

     

    I tried to restart but it was impossible to boot up again, even in safe or recovery mode. Today, during an inconclusive safe boot I've got this

    Previous Shutdohn Cause: 3

    SMC::smcInitHelper ERROR: MMIO regMap == NULL - fall back to old SMC mode

    NVDANV50HAL loaded and registered.

    SMC::smcHandleInterruptEvent WARNING status=0x0 (0x40 not set) notif=0x0

    NVDANV50HAL loaded and registered.

    SMC::smcReadKeyAction ERROR: smcReadData8 failed for key MOTP (kSMCKeyNotFound)

    DSMOS has arrived

    SMC::smcReadKeyAction ERROR: smcReadData8 failed for key BEMB (kSMCKeyNotFound)

    macx_swapon SUCCESS

    infunc createVirtualInterface ifRole =1 Created virtif 0xffffff800bb7100 p2p0

    Airport: Link Down on en1. Reason 8 (Disassociated because station leaving).

    I've done the PRAM and NVRAM reset and then I've been able to boot in recovery mode. I did nothing else, just restart normally and it worked. Now my fear is if i'm going to have these boot and graphic errors again. ¿Are these the same errors you've been experiencing? ¿Should I try replacing the AppleSMC.kext?

     

    Thanks

  • by Laris,

    Laris Laris Jun 6, 2012 1:00 AM in response to frankbullitt
    Level 1 (10 points)
    Jun 6, 2012 1:00 AM in response to frankbullitt

    I have replaced and works very well! No problem! Good luck.

  • by lsbee100,

    lsbee100 lsbee100 Jun 26, 2012 1:13 PM in response to Laris
    Level 1 (0 points)
    Jun 26, 2012 1:13 PM in response to Laris

    Thank you.  Relacing the 10.7.4 file with the 10.7.3 file eliminated all console errors.  This was driving me nuts!

  • by Laris,

    Laris Laris Jun 29, 2012 3:02 PM in response to lsbee100
    Level 1 (10 points)
    Jun 29, 2012 3:02 PM in response to lsbee100

    You are Welcome Glad to help !

  • by iambrainz,

    iambrainz iambrainz Jul 3, 2012 11:15 PM in response to frankbullitt
    Level 1 (0 points)
    Jul 3, 2012 11:15 PM in response to frankbullitt

    frankbullitt did you manage to fix it? I ave a somewhat similar experience./___sbsstatic___/migration-images/188/18820682-1.png

    This happened after it was frozen and restarted..

  • by frankbullitt,

    frankbullitt frankbullitt Jul 4, 2012 2:56 AM in response to iambrainz
    Level 1 (0 points)
    Jul 4, 2012 2:56 AM in response to iambrainz

    Yeah, I kinda fixed it, I´m sorry I didn't post anything after I did it and thanks to Laris and everyone else.

     

    The thing is, it works but, my mac at least, still does strange things. Let me explain. After I replaced the kext, I booted in safe mode, it worked, so I shut down and restarted in normal mode. It worked again. Next day, normal boot, it hanged again at the spinning wheel. Safe boot, it works, restart, normal boot, It works, magic. For some days it was impossible to do a normal boot without doing a safe boot previously, I didn't understand it. One day I forgot to press shift key at boot screen and I thought it was going to hang up... but it didn't. Magic. After that, it takes lke a year and a half to start up, it used to take only a year before. Maybe this is only happening to me, I don't know. Now I have some time i'm going to make a clean OS X install, maybe 10.7.3, maybe going back to 10.6, I'm not sure.

     

    That's my story, I hope it helps you (but I don't think it's going to).

  • by Mojo66,

    Mojo66 Mojo66 Jul 28, 2012 10:38 AM in response to lsbee100
    Level 1 (59 points)
    Jul 28, 2012 10:38 AM in response to lsbee100

    Just for the record: the problem with smcfancontrol flooding the console with errors is gone in 10.8.

  • by Laris,

    Laris Laris Aug 1, 2012 10:22 PM in response to Mojo66
    Level 1 (10 points)
    Aug 1, 2012 10:22 PM in response to Mojo66

    Yes, i confirm that !

  • by Martin Whittaker,

    Martin Whittaker Martin Whittaker Sep 16, 2012 1:28 AM in response to vladalexa
    Level 1 (15 points)
    Sep 16, 2012 1:28 AM in response to vladalexa

    DO NOT manually downgrade the kernel extension just because the new version exposed a bug in one of the applications using it

     

    100% agree with this.  The problem in my case was a combination of Fan Control and iStat.  I removed iStat from the dashboard, and removed Fan Control as documented elsewhere in this thread.  Problem gone.

     

    Just as an experiment I re-installed the iStat widget.  There was a flurry of SMC errors when it installed, but after that all was clear.  I assume it disables checking for any SMC calls that return errors when it is first installed.  So I can still have the useful iStat widget, and no SMC errors in the log.  Nice.

  • by TKRWH,

    TKRWH TKRWH Oct 23, 2012 9:44 AM in response to paddyiyer
    Level 1 (0 points)
    Oct 23, 2012 9:44 AM in response to paddyiyer

    Well I followed Alfonso Garcia's comment below and it fixed my error instantly.

     

    I've been having same problems with that strange kernel error. I repaired permissions and it didn't work, so I uninstall iStat Pro Wiget, FanControl and I deleted the "FanControl Daemon" folder from \Library\StartupItems

    and now I don't have any problems!

     

    Hope my experience helps all of you!

  • by TransAtlanticDan,

    TransAtlanticDan TransAtlanticDan Nov 14, 2012 6:31 PM in response to Alfonso Garcia
    Level 1 (0 points)
    Nov 14, 2012 6:31 PM in response to Alfonso Garcia

    I didn't even know I had the /Library/StartupItems/FanControlDaemon until I looked!  This was the problem.  It was from 2007.  Deleted, rebooted and the error messages are gone!

first Previous Page 3 of 3