more f'ing kernel panics now

brbr
Posted:
in Genius Bar edited January 2014
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

Comments

  • Reply 1 of 19
    kickahakickaha Posts: 8,760member
    <soapbox>

    Bad RAM.

    </soapbox>
  • Reply 2 of 19
    brbr Posts: 8,395member
    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.
  • Reply 3 of 19
    kickahakickaha Posts: 8,760member
    <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?
  • Reply 4 of 19
    brbr Posts: 8,395member
    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.
  • Reply 5 of 19
    pbpb Posts: 4,255member
    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 6 of 19
    709709 Posts: 2,016member
    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?
  • Reply 7 of 19
    brbr Posts: 8,395member
    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.
  • Reply 8 of 19
    brbr Posts: 8,395member
    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?
  • Reply 9 of 19
    code mastercode master Posts: 344member
    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 10 of 19
    outsideroutsider Posts: 6,008member
    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 11 of 19
    kickahakickaha Posts: 8,760member
    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.
  • Reply 12 of 19
    aquaticaquatic Posts: 5,602member
    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!?
  • Reply 13 of 19
    big macbig mac Posts: 480member
    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.
  • Reply 14 of 19
    synsyn Posts: 329member
    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?
  • Reply 15 of 19
    pbpb Posts: 4,255member
    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 16 of 19
    mugwumpmugwump Posts: 233member
    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 17 of 19
    joecooljoecool Posts: 97member
    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?
  • Reply 18 of 19
    ghost_user_nameghost_user_name Posts: 22,667member
    Moving to Genius Bar.
  • Reply 19 of 19
    pbpb Posts: 4,255member
    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?
Sign In or Register to comment.