mynameismyname

Q: PowerMac G5 frequent Kernel Panics

My Mac is a late-2005 model G5 Dual 2 GHz.  Several months ago I upgraded from Tiger 10.4.11 to Leopard 10.5.8.  Couple months later I started getting frequent Kernel Panics:  Usually after running some maintenance software and a restart, but also after regular restarts (otherwise I leave my Mac on all the time), when couple hours later, always at night, I find the Mac shut down while the fans are loudly blowing at full speed.

 

I've alreday been running DiscWarrior periodically, as well as Cocktail. I also ran some hardware tests (DiscUtility, Drive genius, TechTool Pro) which found nothing abnormal with any of my hardware.

 

Based on what I've read, I checked my Console report, looking for  "shutdown cause" and here's what I found next to each crash:  (date, time) localhost kernel[0]: AppleSMU -- shutdown cause = 2  and I'm wondering what is the "2" meaning (the article I read was showing "3" as an example, though not explaining its meaning).

 

I'm already planning to open my Mac this weekend, reset the SMU (I understand my Mac has an SMU, not PMU), but before doing that, I'd like to know if anybody has an idea what is that cause = 2 meaning....

 

Thanks so much....

Power Mac G5 (Late 2005), Mac OS X (10.5.8), 5 GB Ram

Posted on Oct 10, 2012 9:19 AM

Close

Q: PowerMac G5 frequent Kernel Panics

  • All replies
  • Helpful answers

Page 1 of 3 last Next
  • by Klaus1,Helpful

    Klaus1 Klaus1 Oct 10, 2012 3:26 PM in response to mynameismyname
    Level 8 (48,858 points)
    Oct 10, 2012 3:26 PM in response to mynameismyname
  • by japamac,Helpful

    japamac japamac Oct 10, 2012 3:58 PM in response to mynameismyname
    Level 7 (24,390 points)
    Oct 10, 2012 3:58 PM in response to mynameismyname

    Old machines are prone to overheat because they are often dirty and have dust buildup.

    Clean out the interior. Remove the CPU cover and clean the radiator fins.

     

    Use compressed air to blow the dust out of the PSU. The PSU can ho;s up to a cup or so of dust which will cause overheat, shutdowns and possibly fire.

    https://discussions.apple.com/thread/2806982?start=0&tstart=0

     

    Check carefully for coolant leaks from the LCS. A leaking LCS will destry a machine with corrosion and shorting.

    PowerMac G5 Coolant Leaks/Repairs

  • by mynameismyname,

    mynameismyname mynameismyname Oct 11, 2012 5:48 PM in response to japamac
    Level 1 (17 points)
    Mac OS X
    Oct 11, 2012 5:48 PM in response to japamac

    Thanks, Guys...

     

    Klaus, I read the material, and already in the past have performed hardware and software tests that were all showing no problems. I also, just lately, purchased 2 new AC adapters to repalce teh notoriously bad ones that were shipped with my Iomega ext. drive and LaCie's DVD drive... I will still read the last article (cnet) and couple others... The problem is (as mentioned in my original post) — those Kernel Panics are random, they happen ocasionally, but always at night, AND ALWAYS FEW HOURS AFTER A RESTART, following running some maintenance software..... Last couple times I had a hard time restarting my Mac, though, which made me really worried..... I have a feeling that if I leave my Mac working all the time, w/o a restart, it will stay stable.

     

    Japamac:  The inside of my Mac is clean, no dust buildup, and no leakage, and looking at the inside temperature, it looks normal, see below.

    Picture 1.jpg

     

    ....But I'm STILL trying to figure out what's the meaning of that  shutdown cause = 2, though... Would anybody know?

  • by japamac,

    japamac japamac Oct 11, 2012 6:02 PM in response to mynameismyname
    Level 7 (24,390 points)
    Oct 11, 2012 6:02 PM in response to mynameismyname

    but always at night, AND ALWAYS FEW HOURS AFTER A RESTART, following running some maintenance software

    Maintenance software?

    That sounds fishy and likely the software is tied to the issue. It would follow, as well, with panics after a restart if the software has startup and/or login commands built in.

     

    I would remove the maintenance software.

     

    Shutdown cause = 2, I believe, is a software commanded shutdown as logged in Unix based systems.

    Shutdown cause = -1 is the scary one, meaning an error occurred; what ewrror being unknown

     

    I'd rid the machine of third party activities........

  • by mynameismyname,

    mynameismyname mynameismyname Oct 11, 2012 7:31 PM in response to japamac
    Level 1 (17 points)
    Mac OS X
    Oct 11, 2012 7:31 PM in response to japamac

    ...But the last panic attack occured after a regular restart, no maintenace was performed prior...  Could you please detail more about what Shutdown cause = 2 is all about?

     

    Thanks...

  • by japamac,

    japamac japamac Oct 12, 2012 1:08 AM in response to mynameismyname
    Level 7 (24,390 points)
    Oct 12, 2012 1:08 AM in response to mynameismyname

    But the last panic attack occured after a regular restart, no maintenace was performed prior...

    That does not eliminate the possibility of third party add-ons being the cause, especially if there are third party items in startup and or login items.

    Troubleshooting Startup and Login Items - The X Lab

     

    Could you please detail more about what Shutdown cause = 2 is all about?

    I will give you a (probably incomplete) overly simplistic explanation...

     

    All that I can tell you is that Unix based systems log everything that occurs normally, with logs of exceptions or abnormal events also occurring.

     

    Shutdown events that occur normally, or, normally within driver/kext flow, are logged as (usually) 0 and 1, with other codes possible (such as 2 and 3).

    I have yet to find a Unix code guide that adequately differentiates which is what, and do not write the language, but cannot find reference to any non-negative numbers being abnormal with regard to the action.

     

    With regard to irregular shut downs, crashes that cause shut downs are typically not logged due to interruption of the CPU write processes.

     

    When a shut down fails or occurs due to a failure, that will be typically be logged as a -1.

     

    Other shutdown causes such as user command or force quit will also have logs but not typically numbered.

     

    Since your shutdown cause = -1 isn't what you have, I believe that your shutdowns are software inflicted, either by the BSD alone (less likely) or due to third party add on action (most likely).

     

    I think that your software, somewhere, is dumping conflicting commands into the system. This is likely what causes the freezes, crashes and shutdowns.

    My first suspect would be any regularly scheduled maintenance software.

     

    I would UNINSTALL it.

     

    Maintenance software really isn't necessary anyhow..... Most all of it simply capitalizes on built in OS X operations and simply provides a UI that allows user manipulation and addition of third party kext scheduling.

    I have used nothing but disk utilities and OS X built in kron scripts for years in all my systems (I currently run 6). Once in a blue moon maybe a cache cleaning utility, but ONLY when there is abnormal behavior. Improper or too deep of a cache cleaning can destabilize a system. Maintenance utilities have this potential... ALL of them.

     

    For the purposes of troubleshooting though, like with anti virus software, uninstalling is a must. It can always be put back if one really wants it.

     

    Not to discount hardware, though. A VERY common source of kernel panics (that is the real issue) is failing or failed RAM.

    Download Rember or Memtest X and test ALL RAM. Memtest X in Single User mode does the best job at testing all RAM at once. This is the best way to find the hard to find random errors that can drive one nuts.....

  • by mynameismyname,

    mynameismyname mynameismyname Oct 12, 2012 8:13 AM in response to japamac
    Level 1 (17 points)
    Mac OS X
    Oct 12, 2012 8:13 AM in response to japamac

    Hi, japamac,

     

    Thanks for your elaborate response...  To start from the last, I've tested my RAM and it's fine.  I don't use any regularly scheduled maintenance software. But lately the few times I did, and restarted afterwould, few hours later, at night -- I got this Panic Attack.... The only scheduled activities I perform are:  nightly back up (using Retrospect) into an ext. drive, a program I've been using for years now, and I also use Tri-BACKUP 5 which is creating a mirror image of my HD on the ext. drive.

     

    But being a graphic designer I have many fonts, and many of them are open.  I actually saved the Console report (I have Console running in the background all the time) from the last crash last weekend, which I could send to you (tell me how)... One can find all kinds of errors there, but not sure how FATAL are those errors...

     

    As mentioned in my original post,  I am contemplating opening my Mac and resetting the SMU button.... What do I have to lose?

     

    Thanks again...

  • by japamac,

    japamac japamac Oct 12, 2012 3:28 PM in response to mynameismyname
    Level 7 (24,390 points)
    Oct 12, 2012 3:28 PM in response to mynameismyname

    I've tested my RAM and it's fine.

    Techtool? Mediocre RAM test..... not definitive, doesn't test all nor catch random errors well.

    I don't use any regularly scheduled maintenance software. But lately the few times I did, and restarted afterwould, few hours later, at night -- I got this Panic Attack

    Don't use it.

    I have many fonts, and many of them are open

    http://www.jklstudios.com/misc/osxfonts.html

    http://theconstellationhypothesis.blogspot.jp/2008/04/os-x-leopard-helvetica-fon t-conflict.html

    One can find all kinds of errors there,

    Errors are often normal and benign. The ones that immediately preceed a crash are the ones of concern.

  • by mynameismyname,

    mynameismyname mynameismyname Oct 12, 2012 6:37 PM in response to japamac
    Level 1 (17 points)
    Mac OS X
    Oct 12, 2012 6:37 PM in response to japamac

    japamac,

     

    I have Rember, I used it couple months ago, and it took FOREVER (I guess I need to chose a shorter test, limit the number of LOOPS to what, 1? 2? 20?), till I stopped it, but it found nothing wrong...

     

    You're saying "The ones that immediately preceed a crash are the ones of concern."  I have that report, but can't figure it out, except for that "Shutdown cause = 2"

  • by BDAqua,

    BDAqua BDAqua Oct 12, 2012 9:06 PM in response to mynameismyname
    Level 10 (123,765 points)
    Oct 12, 2012 9:06 PM in response to mynameismyname

    Hi, quit using Cocktail, & a shorter test is self defeating, even a long/extended RAM test isn't as likely to find a RAM problem as OSX will... just OSX dosn't rport it as a RAM problem.

  • by mynameismyname,

    mynameismyname mynameismyname Oct 12, 2012 9:24 PM in response to BDAqua
    Level 1 (17 points)
    Mac OS X
    Oct 12, 2012 9:24 PM in response to BDAqua

    Hi, BDAqua...  So I just finished running Rember, 1 loop, took more than 1.5 hours — passed OK. 

     

    If OSX will do a better job finding problems with my RAM, if there are such, but won't report it, just cause my Mac to go crazy without explaining why, that's not gonna be much help...

     

    I'm still contemplating opening my Mac and reset the SMU button... What's there to lose?

  • by japamac,

    japamac japamac Oct 12, 2012 9:49 PM in response to mynameismyname
    Level 7 (24,390 points)
    Oct 12, 2012 9:49 PM in response to mynameismyname

    A shut down is not a crash.

    A kext forced shutdown due to overheat will be logged and have a "thermal runaway" notation.

    A kext forced shutdown due to power issues will have a -1** log.

     

    A crash will not have a shut down logged. It may have a process error report just prior to the crash; crash being a locked system, fans blowing full speed or a kernel panic.

     

    You are tying the shutdown and a kernel panic together. Deal with the kernel panic.

    In a kernel panic log, the lines immediately after "backtrace" tell the processes closest to the crash.

    Those lines can provide helpful info.

     

    As well, the type of error; data access, CPU 1 at thread whatever crashed, etc., are important.

     

    A PMU/SMU reset will help with power management issues. These issues include start, sleep, wake from sleep, restart and shutdown issues, typically the inability to do said process.

     

    Go ahead and reset it, but the kernel panic is most likely unrelated.

    Resetting the SMU will not resolve issues in which your computer is unresponsive--in these situations, restarting your computer will generally suffice.

     

    Resetting the SMU can resolve some computer issues such as not starting up, not displaying video, sleep issues, fan noise issues, and so on.

     

    http://support.apple.com/kb/HT1436

  • by mynameismyname,

    mynameismyname mynameismyname Oct 12, 2012 9:58 PM in response to japamac
    Level 1 (17 points)
    Mac OS X
    Oct 12, 2012 9:58 PM in response to japamac

    I opened the Console log I saved after the crash (mentioned in my original post, I now have Console launched and running all the time), looking for "backtrace" but did not find such word in the log.  What other words should I look for?

  • by BDAqua,

    BDAqua BDAqua Oct 12, 2012 10:06 PM in response to mynameismyname
    Level 10 (123,765 points)
    Oct 12, 2012 10:06 PM in response to mynameismyname

    I totally agree, but you can only trust RAM testing if it does find a problem, not if it doesn't.

Page 1 of 3 last Next