AppleInsider › Forums › General › Genius Bar › more f'ing kernel panics now
New Posts  All Forums:Forum Nav:

more f'ing kernel panics now

post #1 of 20
1/15/04 at 1:48pm
Thread Starter 
  • BR
  • Justified Arrogance
here's the log...can someone make any sense out of this?

Wed Jan 14 22:59:17 2004




Unresolved kernel trap(cpu 0): 0x700 - Program DAR=0xe0549000 PC=0x00000c80
Latest crash info for cpu 0:
Exception state (sv=0x0FB66780)
PC=0x00000C80; MSR=0x00081000; DAR=0xE0549000; DSISR=0x42000000; LR=0x90224EE4; R1=0xBFFFFA60; XCP=0x0000001C (0x700 - Program)
Backtrace:

backtrace terminated - frame not mapped or invalid: 0xBFFFFA60

Proceeding back via exception chain:
Exception state (sv=0x0FB66780)
previously dumped as "Latest" state. skipping...

Kernel version:
Darwin Kernel Version 6.8:
Wed Sep 10 15:20:55 PDT 2003; root:xnu/xnu-344.49.obj~2/RELEASE_PPC


panic(cpu 0): 0x700 - Program
Latest stack backtrace for cpu 0:
Backtrace:
0x000857F4 0x00085C24 0x000287B4 0x0008F6A8 0x000927B8
Proceeding back via exception chain:
Exception state (sv=0x0FB66780)
PC=0x00000C80; MSR=0x00081000; DAR=0xE0549000; DSISR=0x42000000; LR=0x90224EE4; R1=0xBFFFFA60; XCP=0x0000001C (0x700 - Program)
Backtrace:

backtrace terminated - frame not mapped or invalid: 0xBFFFFA60


Kernel version:
Darwin Kernel Version 6.8:
Wed Sep 10 15:20:55 PDT 2003; root:xnu/xnu-344.49.obj~2/RELEASE_PPC



*********

Thu Jan 15 01:06:49 2004




Unresolved kernel trap(cpu 0): 0x400 - Inst access DAR=0x007f8000 PC=0x00000000
Latest crash info for cpu 0:
Exception state (sv=0x0FA6A780)
PC=0x00000000; MSR=0x40001030; DAR=0x007F8000; DSISR=0x42000000; LR=0x00000000; R1=0x0925BDB0; XCP=0x00000010 (0x400 - Inst access)
Backtrace:
0x00000000
backtrace terminated - unaligned frame address: 0x0000004B

Proceeding back via exception chain:
Exception state (sv=0x0FA6A780)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x0E74B000)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

Kernel version:
Darwin Kernel Version 6.8:
Wed Sep 10 15:20:55 PDT 2003; root:xnu/xnu-344.49.obj~2/RELEASE_PPC


panic(cpu 0): 0x400 - Inst access
Latest stack backtrace for cpu 0:
Backtrace:
0x000857F4 0x00085C24 0x000287B4 0x0008F6A8 0x000927B8
Proceeding back via exception chain:
Exception state (sv=0x0FA6A780)
PC=0x00000000; MSR=0x40001030; DAR=0x007F8000; DSISR=0x42000000; LR=0x00000000; R1=0x0925BDB0; XCP=0x00000010 (0x400 - Inst access)
Backtrace:
0x00000000
backtrace terminated - unaligned frame address: 0x0000004B

Exception state (sv=0x0E74B000)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

Kernel version:
Darwin Kernel Version 6.8:
Wed Sep 10 15:20:55 PDT 2003; root:xnu/xnu-344.49.obj~2/RELEASE_PPC

 

“The nitrogen in our DNA, the calcium in our teeth, the iron in our blood, the carbon in our apple pies were made in the interiors of collapsing stars. We are made of starstuff.” 
-Sagan
Reply

 

“The nitrogen in our DNA, the calcium in our teeth, the iron in our blood, the carbon in our apple pies were made in the interiors of collapsing stars. We are made of starstuff.” 
-Sagan
Reply
post #2 of 20
1/15/04 at 1:52pm
  • Kickaha
  • Really Fast Typing Member
<soapbox>
Bad RAM.
</soapbox>
My brain is hung like a HORSE!
Reply
My brain is hung like a HORSE!
Reply
post #3 of 20
1/15/04 at 2:03pm
Thread Starter 
  • BR
  • Justified Arrogance
Quote:
Originally posted by Kickaha
<soapbox>
Bad RAM.
</soapbox>

<soapbox>
factory installed ram...nothing else.
</soapbox>

I went a month without any and now I'm getting a flurry of them again.

 

“The nitrogen in our DNA, the calcium in our teeth, the iron in our blood, the carbon in our apple pies were made in the interiors of collapsing stars. We are made of starstuff.” 
-Sagan
Reply

 

“The nitrogen in our DNA, the calcium in our teeth, the iron in our blood, the carbon in our apple pies were made in the interiors of collapsing stars. We are made of starstuff.” 
-Sagan
Reply
post #4 of 20
1/15/04 at 2:05pm
  • Kickaha
  • Really Fast Typing Member
<soapierbox>
RAM can die
</soapierbox>

Seriously, a hardware check is a quick way to narrow down possible problems. Why go through all the hassle of software troubleshooting when you can just replace a SIMM if that's all it is?
My brain is hung like a HORSE!
Reply
My brain is hung like a HORSE!
Reply
post #5 of 20
1/15/04 at 2:15pm
Thread Starter 
  • BR
  • Justified Arrogance
Quote:
Originally posted by Kickaha
<soapierbox>
RAM can die
</soapierbox>

Seriously, a hardware check is a quick way to narrow down possible problems. Why go through all the hassle of software troubleshooting when you can just replace a SIMM if that's all it is?

It's the built in ram. I have an imac 17". I don't want to take it in for repairs again. I'd rather software troubleshoot and find something wrong that way then deal with idiot repairpeople.

 

“The nitrogen in our DNA, the calcium in our teeth, the iron in our blood, the carbon in our apple pies were made in the interiors of collapsing stars. We are made of starstuff.” 
-Sagan
Reply

 

“The nitrogen in our DNA, the calcium in our teeth, the iron in our blood, the carbon in our apple pies were made in the interiors of collapsing stars. We are made of starstuff.” 
-Sagan
Reply
post #6 of 20
1/15/04 at 2:17pm
I ran kpdecode on the panic log. It gives

Wed Jan 14 22:59:17 2004 :
Backtrace 1:
0x000857f4: _print_backtrace
0x00085c24: _Debugger
0x000287b4: _panic
0x0008f6a8: _trap
0x000927b8: .L_call_trap

Now I am not specialist to decrypt that, but it looks like bad RAM. In any case, running hardware test is useful to isolate the problem.
Reply
Reply
post #7 of 20
1/15/04 at 3:48pm
Quote:
Originally posted by PB
I ran kpdecode on the panic log. It gives

Wed Jan 14 22:59:17 2004 :
Backtrace 1:
0x000857f4: _print_backtrace
0x00085c24: _Debugger
0x000287b4: _panic
0x0008f6a8: _trap
0x000927b8: .L_call_trap

Now I am not specialist to decrypt that, but it looks like bad RAM. In any case, running hardware test is useful to isolate the problem.

I don't know how the hell you got 'bad RAM' from that. It's pretty obvious that's a 'voodoo curse' code, probably put on BR by Carol A.

Any burning sensations lately BR?
It's just an object. It doesn't mean what you think.
Reply
It's just an object. It doesn't mean what you think.
Reply
post #8 of 20
1/15/04 at 6:13pm
Thread Starter 
  • BR
  • Justified Arrogance
Quote:
Originally posted by 709
I don't know how the hell you got 'bad RAM' from that. It's pretty obvious that's a 'voodoo curse' code, probably put on BR by Carol A.

Any burning sensations lately BR?

Yeah but I don't think waking up drunk on a campfire has anything to do with Carol's superstitions.

 

“The nitrogen in our DNA, the calcium in our teeth, the iron in our blood, the carbon in our apple pies were made in the interiors of collapsing stars. We are made of starstuff.” 
-Sagan
Reply

 

“The nitrogen in our DNA, the calcium in our teeth, the iron in our blood, the carbon in our apple pies were made in the interiors of collapsing stars. We are made of starstuff.” 
-Sagan
Reply
post #9 of 20
1/15/04 at 6:23pm
Thread Starter 
  • BR
  • Justified Arrogance
Now, zapping the P-RAM and repairing permissions seems to stop the kernel panics but only for a while. They came back this morning after doing it last night and now it's been up for 4 hours straight without a panic.

This symptom consistent with the previous attempts at a diagnosis?

 

“The nitrogen in our DNA, the calcium in our teeth, the iron in our blood, the carbon in our apple pies were made in the interiors of collapsing stars. We are made of starstuff.” 
-Sagan
Reply

 

“The nitrogen in our DNA, the calcium in our teeth, the iron in our blood, the carbon in our apple pies were made in the interiors of collapsing stars. We are made of starstuff.” 
-Sagan
Reply
post #10 of 20
1/15/04 at 6:35pm
I would think that if it's RAM problems, it may be fine for a while after a restart until you use up enough to get to the bad spot. There are programs that will do RAM checks for you. In Classic, there is a program called Gauge Pro that will do it I think.
Reply
Reply
post #11 of 20
1/15/04 at 8:02pm
Kernel panics are almost always caused by hardware problems, either bad RAM, PCI cards, the mobo, poorly written hardware drivers, etc. 4 times out of 5 it's bad RAM.
Reply
Reply
post #12 of 20
1/15/04 at 8:41pm
  • Kickaha
  • Really Fast Typing Member
Yup, and Gauge Pro is the best of the lot...if you can still boot into 9. It performs a couple of critical checks that Apple's RAM checker doesn't.
My brain is hung like a HORSE!
Reply
My brain is hung like a HORSE!
Reply
post #13 of 20
1/15/04 at 8:49pm
I don't know what just happened to me. I was trying to play UT in Classic. It sucks. Anyway I was trimming down the Extensions seeing what I could just barely get away with to see if that goosed it and all of a sudden the screen faded blue. Then I was at the login screen. WTF mate!?
"Overpopulation and climate change are serious shit." Gilsch
"I was really curious how they had managed such fine granularity of alienation." addabox
Reply
"Overpopulation and climate change are serious shit." Gilsch
"I was really curious how they had managed such fine granularity of alienation." addabox
Reply
post #14 of 20
1/16/04 at 1:34am
Aquatic, I KPed playing UT in Classic as well. I decided it wasn't a good idea to play it, and I haven't since then.
PPC4EVER
Reply
PPC4EVER
Reply
post #15 of 20
1/16/04 at 2:57am
Quote:
Originally posted by Aquatic
I don't know what just happened to me. I was trying to play UT in Classic. It sucks. Anyway I was trimming down the Extensions seeing what I could just barely get away with to see if that goosed it and all of a sudden the screen faded blue. Then I was at the login screen. WTF mate!?

The WindowServer crashed. It happens.

You guys do realise there IS an OSX version of the original UT?
Soyons réalistes, Demandons l'impossible.
Reply
Soyons réalistes, Demandons l'impossible.
Reply
post #16 of 20
1/16/04 at 4:53am
Quote:
Originally posted by 709
I don't know how the hell you got 'bad RAM' from that.

As I said, I am not a specialist in decrypting such messages. Simply, in the KP log and the kpdecode output as well, there is no more evidence than errors while accessing some memory addresses.
Reply
Reply
post #17 of 20
1/16/04 at 9:42pm
I had a ridiculous situation a few weeks ago that trashing a certain quicktime DV file would cause a kernel panic each time. Turns out that Norton Systemwerks was installed and the disk tracking option was the culprit.
Reply
Reply
post #18 of 20
1/18/04 at 11:26pm
I know how you guys feel. I've been getting at least one a day (mainly the whole machine just freezes - occasionally scrolling script panic).

Mine happens intermittently. Watching a DVD. Using VPC, or even just with iTunes open listening to music and it just hangs and stutters in one spot.

Hardware tested the bloody PB (15" AlBook BTW). Reset PRAM and power managers. Checked the extra RAM. Nothing.

What to do?
Joecool only answers the phone when he knows it's for him...
Reply
Joecool only answers the phone when he knows it's for him...
Reply
post #19 of 20
1/19/04 at 1:44am
Moving to Genius Bar.
Reply
Reply
post #20 of 20
1/19/04 at 3:02am
Quote:
Originally posted by Joecool

Hardware tested the bloody PB (15" AlBook BTW). Reset PRAM and power managers. Checked the extra RAM. Nothing.

What to do?

Where is your kernel panic log?
Reply
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Genius Bar
AppleInsider › Forums › General › Genius Bar › more f'ing kernel panics now