PDA

View Full Version : G5 broken :(




boxerchip
Sep 14, 2004, 01:26 AM
So it tuns out that problem i was having in war craft is not a war craft problem but a system problem.... check this out.

Sep 13 16:06:03 Charles-Reynolds-Computer kernel: PowerMac7,3 Thermal Manager: Thermal Runaway Detected: System Will Sleep
Sep 13 16:06:03 Charles-Reynolds-Computer kernel: AFPSleepWakeHandler: going to sleep
Sep 13 16:06:03 Charles-Reynolds-Computer mDNSResponder[219]: mDNSResponder Sleeping at 293499908
Sep 13 16:06:09 Charles-Reynolds-Computer kernel: AppleNMI mask NMI
Sep 13 16:06:16 Charles-Reynolds-Computer kernel: System Sleep
Sep 13 16:06:16 Charles-Reynolds-Computer kernel: System Wake
Sep 13 16:06:16 Charles-Reynolds-Computer kernel: Wake event 0020
Sep 13 16:06:16 Charles-Reynolds-Computer kernel: AppleNMI unmask NMI
Sep 13 16:06:16 Charles-Reynolds-Computer kernel: UniNEnet::monitorLinkStatus - Link is up at 100 Mbps - Full Duplex
Sep 13 16:06:18 Charles-Reynolds-Computer kernel: AFPSleepWakeHandler: waking up


I hear this is a commen problem with G5s and I was just wondering if anyone knows how to fix it or if im gona have to call apple.



BrianKonarsMac
Sep 14, 2004, 01:45 AM
time to call apple i believe.

boxerchip
Sep 14, 2004, 02:07 AM
Happened again :(



Sep 14 02:44:15 localhost kernel: PowerMac7,3 Thermal Manager: Thermal Runaway Detected: System Will Sleep
Sep 14 02:44:15 localhost mDNSResponder[230]: mDNSResponder Sleeping at 36571213
Sep 14 02:44:17 localhost kernel: PowerMac7,3 Thermal Manager: Thermal Runaway Detected: System Will Sleep
Sep 14 02:44:17 localhost kernel: AppleNMI mask NMI
Sep 14 02:44:17 localhost kernel: PowerMac7,3 Thermal Manager: Thermal Runaway Detected: System Will Sleep
Sep 14 02:44:27 localhost kernel: System Sleep
Sep 14 02:44:30 localhost kernel: System Wake
Sep 14 02:44:30 localhost kernel: Wake event 0020
Sep 14 02:44:30 localhost kernel: AppleNMI unmask NMI
Sep 14 02:44:30 localhost kernel: UniNEnet::monitorLinkStatus - Link is up at 100 Mbps - Full Duplex
Sep 14 02:44:34 localhost mDNSResponder[230]: mDNSResponder Waking at 36583116

friarbayliff
Sep 14, 2004, 02:59 AM
man, that sucks.

Time to call apple indeed

boxerchip
Sep 14, 2004, 10:07 AM
Well damn this is not the best expireance for a first time apple person :(

Damn I hope I dont have to send it in.... I hear it takes months.

Sun Baked
Sep 14, 2004, 10:19 AM
As users of Hardware Monitor have found out, applications can cause problems with the new G5s.

But basically the KP is saying the CPU temps got too hot and the machine was shut down.

Of course artcat had this to say on ARS, which may be worth checking out...Originally posted by artcat: (http://episteme.arstechnica.com/eve/ubb.x?a=tpc&s=50009562&f=8300945231&m=9080959175&r=934002406631#934002406631)

Hey, I thought you were going to jump all over the Dual 2.5! Come on in, the water's fine! Well, okay, it's a little toasty...

Regarding 'reduced' processor performance, I had that chosen as my setting, and that's when I had my two thermal runaways (on Sept. 7). However, I also had 'put the hard disk(s) to sleep when possible' checked. I changed both settings and haven't had a therm. runaway event since. If I weren't so squeamish about seeing my die temps soar north of 90C again (and they did just before sleep kicked in), I'd change the settings back in different combinations and see if I could bring the TR event on again.

Maybe as a good Apple/MacAch citizen I should do it anyway. Then we'd/I'd know something -- at least about my machine.

RGunner
Sep 14, 2004, 11:46 AM
If you are running Hardware Monitor (I think the paid version)... the interaction with the Fan speed sensors will cause the machine to hiccup and die.

There is information on the Hardware Monitor site which notes this as well.

QCassidy352
Sep 14, 2004, 11:49 AM
it definitely does not take months to get your computer back if it does have to go in... I had to send in an ibook once, and it was out of my hands less than a week... 4 business days in total, I believe.

FuzzyBallz
Sep 14, 2004, 12:19 PM
Did you put new memory in that system?

boxerchip
Sep 14, 2004, 03:27 PM
none... dident touch it, totally stock.

FuzzyBallz
Sep 14, 2004, 03:44 PM
In that case, you got a lemon. Call Apple right away.

jane doe
Sep 14, 2004, 04:07 PM
Before calling Apple, Boot to the restore CD (holding option) run the extened Apple Hardware Test at least 3 times. If there is an error code or it freezes during the test make sure to tell this to the tech on the phone. Also have your serial number ready and be ready to remove anything that is added.

boxerchip
Sep 14, 2004, 05:44 PM
ok I ran the stuff and it said everything is fine, I also set the system to always run at max performance and i played a few games of war craft.... this seems to have fixed the problem.

Sun Baked
Sep 15, 2004, 04:52 PM
ok I ran the stuff and it said everything is fine, I also set the system to always run at max performance and i played a few games of war craft.... this seems to have fixed the problem.It will probably come down to a conflict between the Warcraft game and Apple's Energy saver, wouldn't be the first time this has happened.

If the machine runs in automatic, the rest of the time, you should probably leave it in automatic.

boxerchip
Sep 15, 2004, 07:02 PM
ok this happened again and i was not in a game or anything, I called apple and my CPU is bad so they are coming to my FRICKING house to replace jesus i never expected that. APPLE RULES

Dr. Dastardly
Sep 15, 2004, 07:44 PM
ok this happened again and i was not in a game or anything, I called apple and my CPU is bad so they are coming to my FRICKING house to replace jesus i never expected that. APPLE RULES
Damn never heard of them coming to the house. Maybe because its stock and easily replaceable, but still pretty sweet service.

jane doe
Sep 15, 2004, 08:06 PM
ok this happened again and i was not in a game or anything, I called apple and my CPU is bad so they are coming to my FRICKING house to replace jesus i never expected that. APPLE RULES

they're not coming to replace the computer, maybe do a repair onsite.

mojohanna
Sep 15, 2004, 08:51 PM
So it tuns out that problem i was having in war craft is not a war craft problem but a system problem.... check this out.

Sep 13 16:06:03 Charles-Reynolds-Computer kernel: PowerMac7,3 Thermal Manager: Thermal Runaway Detected: System Will Sleep
Sep 13 16:06:03 Charles-Reynolds-Computer kernel: AFPSleepWakeHandler: going to sleep
Sep 13 16:06:03 Charles-Reynolds-Computer mDNSResponder[219]: mDNSResponder Sleeping at 293499908
Sep 13 16:06:09 Charles-Reynolds-Computer kernel: AppleNMI mask NMI
Sep 13 16:06:16 Charles-Reynolds-Computer kernel: System Sleep
Sep 13 16:06:16 Charles-Reynolds-Computer kernel: System Wake
Sep 13 16:06:16 Charles-Reynolds-Computer kernel: Wake event 0020
Sep 13 16:06:16 Charles-Reynolds-Computer kernel: AppleNMI unmask NMI
Sep 13 16:06:16 Charles-Reynolds-Computer kernel: UniNEnet::monitorLinkStatus - Link is up at 100 Mbps - Full Duplex
Sep 13 16:06:18 Charles-Reynolds-Computer kernel: AFPSleepWakeHandler: waking up


I hear this is a commen problem with G5s and I was just wondering if anyone knows how to fix it or if im gona have to call apple.

I was having similar problems. Tried everything. Ended up having to have the logic board replaced. They had my machine for a week!!!! I was going thru some sort of withdrawl. I only had my PieceofCrap at work to deal with.

Sun Baked
Sep 15, 2004, 09:05 PM
I was having similar problems. Tried everything. Ended up having to have the logic board replaced. They had my machine for a week!!!! I was going thru some sort of withdrawl. I only had my PieceofCrap at work to deal with.There have been quite a few of these "Thermal Runaways" posts lately, starting to seem like a bad batch.

Though the Hardware Monitor application was causing it's share of problems, people idea of what is a hot chip for the G5s seems to have changed the past couple weeks.

So people probably wouldn't be able to get Apple to replace their "hot" machines replaced -- but experience repeated "Thermal Runaways," and it'll probably be fixed.