IMAC G5 (pre-isight) Sick and getting Sicker

[daryl66]

Machine: 1st Generation Imac G5, 1.8mz 512mb 160 ghz OSX 10.4.8.

Issue(s):
 
Found the machine with fan running like a Cessna powering up for take off, could not effect anything with the power switch.  Unplugged the power, assumed it was the much published  PowerSupply issue with 1st gen G5's. There is no Apple Store within 350 miles but we do have an Authorized Apple Dealer in town.( Warantee expired and no Apple care) It took over 4 week and much dialog but they finally got Apple to authorize a PS replacement which was accomplished last week.

SOP is to put the IMAC into a hard sleep when not is use.  Today while it was asleep guess what.  The fan took off again and I could not effect anything with the KBD or power switch. Symptioms the same as before.   I unplugged it waited about a minute then powered it back up and it is running normal right now. I will instruct "her" to "shut down" instead of putting it to sleep when not actually in use, but it looks like there is another problem.

Have everything backed up and awating for the other shoe to drop.


Any Ideas??

Daryl

[gunug]

Did you try resetting the SMU (System Management Unit):

1.  Turn off the computer by choosing Shut Down from the Apple menu, or by   holding the power button until the computer turns off.

2. Unplug all cables from the computer, including the power cord.

3. Wait 10 seconds.

4. Plug in the power cord while simultaneously pressing and holding the power button on the back of the computer.

5. Let go of the power button.

6. Press the power button once more to start up your iMac.

This has occasionally helped with the iSight model G5 iMAC's we have around.  We had one of them that had 2 logic boards and a power supply board changed out!

[Paddy]

You also might want to look in the system logs to see if there is anything unusual there. The thermal overruns that some of the early 2.5GHz dual processor G5s suffered did show up there. Sounds a lot like that, but I've never heard of a G5 iMac suffering from the syndrome!

[daryl66]

QUOTE(Paddy @ Dec 7 2006, 03:31 PM) <{POST_SNAPBACK}>

You also might want to look in the system logs to see if there is anything unusual there. The thermal overruns that some of the early 2.5GHz dual processor G5s suffered did show up there. Sounds a lot like that, but I've never heard of a G5 iMac suffering from the syndrome!

Paddy: Can you point me at the system logs??

GN:  I just got a note back from the AAD, he seems to think that the "logic board"  has probably been had, and thinks that Apple will cover it.  I sent him the SN again so lets see if that bears any fruit.

This is my 8th Mac since 1986, and the first one ever to go to the shop.  Guess I do not have too much to complain about.

Daryl

[Xairbusdriver]

You have at least two places to look for/at crash logs. The System Library and your User Library. The easiest way is to launch "Console" ( should be in the Utilities that Apple installs with the OS ). Click the icon in the upper, left-hand corner of the window that opens ( assuming you have the Toolbar showing ). You'll see a list of at least five "logs", some of which have 'flippy' triangles. The ones you probably want to check for crash logs are "~/Library/Logs/CrashReporter" ( your user crash logs ) and "/Library/Logs/CrashReporter" ( the System crash logs ). Which ones to actually inspect is no my yob! But I would suspect they are in the System logs. Just tell us what logs are in there, is any.

99% of what's in those logs is not English, at least the form that most of us speak! But you should find dates and times near the beginning of each crash and that may indicate what happened to cause the fan speeds to go to max. That is, assuming you can approximate the time of these events. A knowlegable Apple tech might then be able to read the log and find a cause/cure.

Good luck!

[daryl66]

QUOTE(Xairbusdriver @ Dec 7 2006, 07:25 PM) <{POST_SNAPBACK}>

The ones you probably want to check for crash logs are "~/Library/Logs/CrashReporter" ( your user crash logs ) and "/Library/Logs/CrashReporter" ( the System crash logs ). Which ones to actually inspect is no my yob! But I would suspect they are in the System logs. Just tell us what logs are in there, is any.

99% of what's in those logs is not English, at least the form that most of us speak!

I do not recall how to take a screen shot to post it here, however  System"Library logs, CrashReporter has 23 files on the dropdown. Adobe Reader.crash. Applemodemon hold, cache-fonts, Classic Startup, Contendindexing, finder, Help viewer, IcalHelper, IE, Liveupdate host admin,isave, mail, MS (4 different ones) Safari, ScreenSaver Engine, Software Update, Sytem Profiler, TruBlueEnvironment. Yahoo Messenger. (all had a dot crash log)

Librafy/Logs, Crash Reporter has only one. WindowServer.

I don't see anything that would give ME a clue,


Daryl

[RNKIII]

Daryl66,

I too have an iSightless G5 iMac.... and have had 2 power supplies and a Logic board replaced all under warranty and/or Applecare....  IF I remember right the tech told me that often(not always) the LB goes with the PS....

I would keep up any pressure (no matter how little) on Apple to replace the LB if they have replaced the PS 'for cause'....

Best of wishes & luck  with this...


Bob K.   rnkiii

[Xairbusdriver]

Any number of those could be a problem. But the only important thing, right now, is: Did any of them crash just before a runaway fan event? If not, forget about them. You can see the time(s) they crashed by looking at the logs with Console. At the beginning of each crash, there are a few lines that are human consumable:

CODE

**********

Host Name:      Jim-Chaffins-Computer
Date/Time:      2006-11-24 20:37:25.231 -0600
OS Version:     10.4.3 (Build 8F46)
Report Version: 3

Command: BBEdit
Path:    /Applications/Programming/BBEdit 7.1.4/BBEdit.app/Contents/MacOS/BBEdit
Parent:  WindowServer [90]

Version: 7.1.4 (7.1.4)

PID:    29751
Thread: 0

Exception:  EXC_BAD_ACCESS (0x0001)
Codes:      KERN_PROTECTION_FAILURE (0x0002) at 0x00000020

From there it gets extremely geeky! But that date/time part is easy to see. If it not even the same month, don't worry about it. If you find one with the same day, check the time; it could very well be one of the causes. I doubt if it will even be worth checking any application crash log, but those 'system' events might have something worth looking at, especially if you see two for the same problem on the same days as the latest fan events.

No real need for a screen shot, the files are just text, you can copy and paste them into any place that will accept text.

[daryl66]

QUOTE(Xairbusdriver @ Dec 8 2006, 10:57 AM) <{POST_SNAPBACK}>

Any number of those could be a problem.
No real need for a screen shot, the files are just text, you can copy and paste them into any place that will accept text.

XABD:
After looking at all of the "crash reports" in both places this is the only one that seems to have occured yesterday, and I think it happend after the fact when I had it back up and running.  If I am reading things correctly these "crashes" go all the way back to when the computer was first fired up.

What does "crash" really mean??  I just assumed that when something crashed, it REALLY crashed and there would be some indication.  This guy has been running great for almost 2 years until this problem showed up.

Host Name:      Imac-sharing
Date/Time:      2006-12-07 12:34:05.213 -0800
OS Version:     10.4.8 (Build 8L127)
Report Version: 4

Command: Classic Startup
Path:    /System/Library/CoreServices/Classic Startup.app/Contents/MacOS/Classic Startup
Parent:  WindowServer [64]

Version:        1.9 (1.9)
Build Version:  1
Project Name:   Classic
Source Version: 1840000

Found the following in the "system logs"  This seems to be in the correct timeframe:

Dec  7 10:31:43 localhost kernel[0]: NVDANV30HAL loaded and registered.
Dec  7 10:31:43 localhost kernel[0]: SMU_Neo2_PlatformPlugin::initThermalProfile - entry
Dec  7 10:31:43 localhost kernel[0]: SMU_Neo2_PlatformPlugin::initThermalProfile - calling adjust
Dec  7 10:31:43 localhost kernel[0]: IPv6 packet filtering initialized, default to accept, logging disabled
Dec  7 10:31:43 localhost kernel[0]: UniNEnet: Ethernet address 00:0d:93:b6:ba:ce
Dec  7 10:31:43 localhost xinetd[42]: xinetd Version 2.3.11 started with libwrap options compiled in.
Dec  7 10:31:43 localhost xinetd[42]: Started working: 0 available services
Dec  7 10:31:44 localhost diskarbitrationd[45]: disk0s3    hfs      AFE43160-0CCE-323E-82C9-A2511E4B7923 Imac HD                 /
Dec  7 10:31:44 localhost launchd: Server 293b in bootstrap 1103 uid 0: "/usr/sbin/lookupd"[57]: exited abnormally: Hangup
Dec  7 10:31:44 localhost kernel[0]: NVDA,Display-A: vram [a0000000:08000000]
Dec  7 10:31:44 localhost lookupd[67]: lookupd (version 369.5) starting - Thu Dec  7 10:31:44 2006
Dec  7 10:31:45 localhost kernel[0]: NVDA,Display-B: vram [00000000:01000000]
Dec  7 10:31:45 localhost /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow: Login Window Application Started
Dec  7 10:31:46 localhost loginwindow[71]: Login Window Started Security Agent
Dec  7 10:31:46 localhost kernel[0]: UniNEnet::monitorLinkStatus - Link is up at 100 Mbps - Full Duplex
Dec  7 10:31:46 localhost configd[43]: AppleTalk startup
Dec  7 10:31:46 Imac-sharing configd[43]: setting hostname to "Imac-sharing.local"
Dec  7 10:31:49 Imac-sharing launchd: Server 0 in bootstrap 1103 uid 0: "/usr/sbin/lookupd"[67]: exited abnormally: Hangup
Dec  7 10:31:49 Imac-sharing configd[43]: executing /System/Library/SystemConfiguration/Kicker.bundle/Contents/Resources/enable-network
Dec  7 10:31:49 Imac-sharing lookupd[100]: lookupd (version 369.5) starting - Thu Dec  7 10:31:49 2006
Dec  7 10:31:49 Imac-sharing configd[43]: posting notification com.apple.system.config.network_change
Dec  7 10:31:49 Imac-sharing launchd: Server 460b in bootstrap 1103 uid 0: "/usr/sbin/lookupd"[100]: exited abnormally: Hangup
Dec  7 10:31:49 Imac-sharing lookupd[101]: lookupd (version 369.5) starting - Thu Dec  7 10:31:49 2006
Dec  7 10:31:51 Imac-sharing mDNSResponder: Adding browse domain local.
Dec  7 10:31:52 Imac-sharing configd[43]: AppleTalk startup complete
Dec  7 10:31:54 Imac-sharing ntpdate[113]: no server suitable for synchronization found
Dec  7 10:31:54 Imac-sharing configd[43]:   target=enable-network: disabled
Dec  7 10:35:05 Imac-sharing configd[43]: AppleTalk shutdown
Dec  7 10:35:05 Imac-sharing /usr/sbin/AppleFileServer: AFPServer::AbnormalATListenerShutDown - clear listener
Dec  7 10:35:05 Imac-sharing configd[43]: AppleTalk shutdown complete
Dec  7 10:37:27 Imac-sharing kernel[0]: System Sleep
Dec  7 10:37:27 Imac-sharing kernel[0]: System Wake



Daryl

[Xairbusdriver]

I don't try to make 'heads nor tales' from the logs. I don't even look at them very often! And you are correct, they stay there until you delete them. And you can safely delete them when ever you want, their simply text files. I'd say there's not much use in keeping anything over a month old on a smooth running machine. And even one that's crashing may not have any useful info in those logs. If you ever see a little dialog asking if you want to report a crash of some app, what gets sent is the crash log for that app.

As for the one you posted, it seems strange that the time in the 'header' is quite different from the time of the last 'event'. But the fact that the last event is a 'wake-up' one may point to the fact that the system is having trouble making the hardware respond correctly. Maybe an additional indication of a hardware problem? May or may not help your local tech build a case for a replacement. He might also have some CDs from Apple that have programs that run infinite Sleep/Wake up cycles on the machine.

Beyond that, I have no suggestions/solutions. Sorry! :sad:

[daryl66]

QUOTE(Xairbusdriver @ Dec 8 2006, 01:17 PM) <{POST_SNAPBACK}>

Maybe an additional indication of a hardware problem? May or may not help your local tech build a case for a replacement. He might also have some CDs from Apple that have programs that run infinite Sleep/Wake up cycles on the machine.

Beyond that, I have no suggestions/solutions. Sorry! :sad:

Well I will keep my fingers crossed that he can "persuade" Apple to go for the logic board replacement.(he was successful in the PS effort) In the mean time I will continue to have her shut down when not actually using it.

Thanks

Daryl

[gunug]

QUOTE

This is my 8th Mac since 1986, and the first one ever to go to the shop. Guess I do not have too much to complain about.

I guess not!  I hope that you do manage to get this taken care of through a warranty extension!

If you can get to this article it might be useful:

http://docs.info.apple.com/article.html?artnum=303321

If you can't then let me know!

[jcarter]

I had the logic board, power supply cookout problem, its covered in complete by Apple. Everything was replaced for free. See Gunug's post, its there.
But not the smell,,,,,,,its not edible,,,,,
Jane

[daryl66]

QUOTE(gunug @ Dec 8 2006, 05:23 PM) <{POST_SNAPBACK}>

If you can get to this article it might be useful:

http://docs.info.apple.com/article.html?artnum=303321

If you can't then let me know!

GN:  Couldn't get it:       

"Document 303321 not found "

Daryl

[jcarter]

Oh, for some reason it went poof, into Apples dustbin, but it is there somewhere in Apples support pages. I will look further,,,,,,,
http://www.macintouch.com/readerreports/po.../topic4026.html
is where I got a lot of good info.  But I cant imagine what happened to this one,
Maybe Apple has discontinued their repair option.  No it cant be, I shall look in my Applecare thing.
I know Gunug gave me the link last August, but do you think I can find it now?
I have to sign off now, tis late and driving a ways tomorrow morning, but we will come up with this link.
You could call Applecare but thats the slowest way to get this link.
Till tomorrow,,,,,,
Jane

Ive been doing a backwards search, here are some links that will send you to the fix.  Getting closer,,,,,

http://www.apple.com/support/imac/powersup...epairextension/
http://discussions.apple.com/thread.jspa?t...55&tstart=0