 |
 |
Help me decipher a panic log.
|
|
|
|
|
Addicted to MacNN
Join Date: Jan 2001
Location: The Sar Chasm
Status:
Offline
|
|
I've had six of these today. So far I've run DiskWarrior, repaired permissions, and run the hardware diagnostic CD. All components passed the hardware test. (the CPU daughter card was replaced in June, by AppleCare, but the machine has been pretty solid with the new CPUs until today. Does this look like a hardware problem? I can roll my system back to 10.3.4, but don't want to mess with it if it's hardware-related.
EDIT: Quicksilver 2002 dual 1 GHZ 1.5 GB RAM, OS 10.3.5
Log: (all six from today are identical)
Wed Sep 15 12:53:34 2004
panic(cpu 1): Uncorrectable machine check: pc = 0000000091561ABC, msr = 000000004000F030, dsisr = 42000000, dar = 00000000E0704000
AsyncSrc = 0000000000000000, CoreFIR = 0000000000000000
L2FIR = 0000000000000000, BusFir = 00000000ffffffff
Latest stack backtrace for cpu 1:
Backtrace:
0x000836E4 0x00083BC8 0x0001EDA4 0x00091634 0x00090DA0 0x0009406C
Proceeding back via exception chain:
Exception state (sv=0x2C6E2280)
PC=0x91561ABC; MSR=0x4000F030; DAR=0xE0704000; DSISR=0x42000000; LR=0x91561A80; R1=0xBFFFF8A0; XCP=0x00000008 (0x200 - Machine check)
Kernel version:
Darwin Kernel Version 7.5.0:
Thu Aug 5 19:26:16 PDT 2004; root:xnu/xnu-517.7.21.obj~3/RELEASE_PPC
Thanks,
CV
|
When a true genius appears in the world you may know him by this sign, that the dunces are all in confederacy against him. -- Jonathan Swift.
|
| |
|
|
|
|
|
|
|
Dedicated MacNNer
Join Date: Dec 2001
Location: Promised Land
Status:
Offline
|
|
Originally posted by chris v:
II can roll my system back to 10.3.4, but don't want to mess with it if it's hardware-related.
EDIT: Quicksilver 2002 dual 1 GHZ 1.5 GB RAM, OS 10.3.5
Log: (all six from today are identical)
Wed Sep 15 12:53:34 2004
panic(cpu 1): Uncorrectable machine check: pc = 0000000091561ABC, msr = 000000004000F030, dsisr = 42000000, dar = 00000000E0704000
AsyncSrc = 0000000000000000, CoreFIR = 0000000000000000
L2FIR = 0000000000000000, BusFir = 00000000ffffffff
The backtrace is a trap hanlder to handle machine exceptions, which then calls panic.
0x1eda4 <panic+472>: lwz r0,-32212(r29)
0x91634 <doexception+592>: lwz r0,136(r1)
0x90da0 <trap+1556>: b 0x911a4 <trap+2584>
0x9406c <thandler+204>: lis r10,512
The exception code is probably located in the MSR (maybe the DAR).
It looks like a hardware problem to me. "Uncorrectable machine check" does not sound good at all. Time to call AppleCare.
|
|
G5 2.5 DP/2GB RAM/NVidia 6800 Ultra
PowerBook Al 1Ghz/768MB RAM
6gb Blue iPod Mini
|
| |
|
|
|
|
|
|
|
Clinically Insane
Join Date: Nov 1999
Status:
Offline
|
|
What model Mac are you using? This looks like a hardware problem, and a bad one at that. I suggest taking the machine in again for repairs.
Whatever you do, DON'T attempt to reinstall the system. I made this mistake once on a Ti/400 with similar problems, and the machine failed mid-install, leaving me with a completely unbootable system. Luckily Target Disk Mode still worked, so I could still back stuff up, but if that hadn't been the case I would have lost everything on the machine.
|
|
You are in Soviet Russia. It is dark. Grue is likely to be eaten by YOU!
|
| |
|
|
|
|
|
|
|
Addicted to MacNN
Join Date: Jan 2001
Location: The Sar Chasm
Status:
Offline
|
|
Well, I've got two internal drives, one being a slightly out-of-date (intentionally one dot-rev back) mirror of the other, so a nuke-and-pave is not a concern.
Here's what appears to have happened, though. I finally got sick of Now Up-To-Date and Contact, and attempted to track down all traces of the scum it spewed all over my drive, and dump it, but apparently, I missed some sort of scheduler that was looking for one of the bits I did dump. Late yesterday, after panic # 7, I fished up the installer, which thankfully had an "uninstall" option, and I ran it, deleting some 250 more items.(!)
It occurred to me after a while that these panics were happening at extremely regular intervals, like exactly one hour after booting. It's been hunky-dory since I ran the uninstaller, and I left SETI going all night, just to see how the proccessors handled an extended run at a full load, and she seems stable.
Lesson 1: Now up-To Date and Contact are crap.
Lesson 2: Don't go around willy-nilly, deleting cruft from your Library folder, unless you really know what you're doing.
|
When a true genius appears in the world you may know him by this sign, that the dunces are all in confederacy against him. -- Jonathan Swift.
|
| |
|
|
|
|
|
|
|
Moderator  Join Date: Apr 2000
Location: Gothenburg, Sweden
Status:
Offline
|
|
Originally posted by chris v:
Lesson 1: Now up-To Date and Contact are crap.
Lesson 2: Don't go around willy-nilly, deleting cruft from your Library folder, unless you really know what you're doing.
Lesson 3: Even if you do know what you're doing, make a backup first.
|
|
|
| |
|
|
|
|
|
|
|
Addicted to MacNN
Join Date: Jan 2001
Location: The Sar Chasm
Status:
Offline
|
|
Originally posted by P:
Lesson 3: Even if you do know what you're doing, make a backup first.
I'm backed up. Always. I just keep my OS backup one dot-release back on purpose, in case I find that an update broke something.
|
When a true genius appears in the world you may know him by this sign, that the dunces are all in confederacy against him. -- Jonathan Swift.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
 
|
|
|
Forum Rules
|
|
|
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
|
HTML code is Off
|
|
|
|
|
|
|
|
|
|
|
|
|
Top
