Welcome to the MacNN Forums.

C.J. Moof · Jan 23, 2004, 11:20 AM

My newly-aquired TiBook is KP'ing left and right, nuking Safari Bookmarks along the way, and otherwise making me not like it. Here's my last 3 logs:

Code:
*********

Wed Jan 21 20:24:33 2004




Unresolved kernel trap(cpu 0): 0x400 - Inst access DAR=0x00000000E17F7000 PC=0x0000000000000000
Latest crash info for cpu 0:
   Exception state (sv=0x1F9B6280)
      PC=0x00000000; MSR=0x40009030; DAR=0xE17F7000; DSISR=0x40000000; LR=0x000CD3B0; R1=0x11F434E0; XCP=0x00000010 (0x400 - Inst access)
      Backtrace:
         0x000CD2E4 0x00234990 0x00234740 0x00207614 0x0023DD24 0x00093D20 0x000A0009 
Proceeding back via exception chain:
   Exception state (sv=0x1F9B6280)
      previously dumped as "Latest" state. skipping...
   Exception state (sv=0x1FB08000)
      PC=0x900370AC; MSR=0x0000F030; DAR=0x00004124; DSISR=0x40000000; LR=0x90055F5C; R1=0xF0080A10; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 7.2.0:
Thu Dec 11 16:20:23 PST 2003; root:xnu/xnu-517.3.7.obj~1/RELEASE_PPC


panic(cpu 0): 0x400 - Inst access
Latest stack backtrace for cpu 0:
      Backtrace:
         0x000833B8 0x0008389C 0x0001ED8C 0x000908C0 0x00093B8C 
Proceeding back via exception chain:
   Exception state (sv=0x1F9B6280)
      PC=0x00000000; MSR=0x40009030; DAR=0xE17F7000; DSISR=0x40000000; LR=0x000CD3B0; R1=0x11F434E0; XCP=0x00000010 (0x400 - Inst access)
      Backtrace:
         0x000CD2E4 0x00234990 0x00234740 0x00207614 0x0023DD24 0x00093D20 0x000A0009 
   Exception state (sv=0x1FB08000)
      PC=0x900370AC; MSR=0x0000F030; DAR=0x00004124; DSISR=0x40000000; LR=0x90055F5C; R1=0xF0080A10; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 7.2.0:
Thu Dec 11 16:20:23 PST 2003; root:xnu/xnu-517.3.7.obj~1/RELEASE_PPC



*********

Thu Jan 22 21:34:49 2004




Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x000000000350960C PC=0x000000000008D484
Latest crash info for cpu 0:
   Exception state (sv=0x20419280)
      PC=0x0008D484; MSR=0x00009030; DAR=0x0350960C; DSISR=0x40000000; LR=0x000652A8; R1=0x12703D20; XCP=0x0000000C (0x300 - Data access)
      Backtrace:
         0x00064660 0x00058D5C 0x00090CF0 0x00093B8C 
Proceeding back via exception chain:
   Exception state (sv=0x20419280)
      previously dumped as "Latest" state. skipping...
   Exception state (sv=0x215B6780)
      PC=0x928D4A50; MSR=0x0000F030; DAR=0xA27F91E0; DSISR=0x0A000000; LR=0x9284819C; R1=0xBFFFAFD0; XCP=0x0000000C (0x300 - Data access)

Kernel version:
Darwin Kernel Version 7.2.0:
Thu Dec 11 16:20:23 PST 2003; root:xnu/xnu-517.3.7.obj~1/RELEASE_PPC


panic(cpu 0): 0x300 - Data access
Latest stack backtrace for cpu 0:
      Backtrace:
         0x000833B8 0x0008389C 0x0001ED8C 0x000908C0 0x00093B8C 
Proceeding back via exception chain:
   Exception state (sv=0x20419280)
      PC=0x0008D484; MSR=0x00009030; DAR=0x0350960C; DSISR=0x40000000; LR=0x000652A8; R1=0x12703D20; XCP=0x0000000C (0x300 - Data access)
      Backtrace:
         0x00064660 0x00058D5C 0x00090CF0 0x00093B8C 
   Exception state (sv=0x215B6780)
      PC=0x928D4A50; MSR=0x0000F030; DAR=0xA27F91E0; DSISR=0x0A000000; LR=0x9284819C; R1=0xBFFFAFD0; XCP=0x0000000C (0x300 - Data access)

Kernel version:
Darwin Kernel Version 7.2.0:
Thu Dec 11 16:20:23 PST 2003; root:xnu/xnu-517.3.7.obj~1/RELEASE_PPC


*********

Fri Jan 23 08:50:50 2004


panic(cpu 0): bad dp memory object
Latest stack backtrace for cpu 0:
      Backtrace:
         0x000833B8 0x0008389C 0x0001ED8C 0x0000CC50 0x00057AF8 0x00059928 0x00090D78 0x00093B8C 
Proceeding back via exception chain:
   Exception state (sv=0x1F9AEA00)
      PC=0x966577F0; MSR=0x4200F030; DAR=0xF00FCFE0; DSISR=0x42000000; LR=0x96560000; R1=0xBFFFE490; XCP=0x00000010 (0x400 - Inst access)

Kernel version:
Darwin Kernel Version 7.2.0:
Thu Dec 11 16:20:23 PST 2003; root:xnu/xnu-517.3.7.obj~1/RELEASE_PPC



*********

Since I don't see any drivers referenced, I'm guessing it's a RAM thing. This morning I pulled the 256 added chip from it, but it's too soon to tell if that helps.

These tend to be on wake from sleep more than anything, but not exclusively.

Any and all interpretations are appreciated.

wadesworld · Jan 23, 2004, 12:00 PM

Unresolved kernel trap(cpu 0): 0x400 - Inst access DAR=0x00000000E17F7000 PC=0x0000000000000000

panic(cpu 0): 0x400 - Inst access

Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x000000000350960C PC=0x000000000008D484

panic(cpu 0): 0x300 - Data access

panic(cpu 0): bad dp memory object

So, we panic'd when trying to access an instruction, next when trying to access data, and finally there was some bad data object in memory.

Yep, I'd say it sounds like RAM.

Wade

Detrius · Jan 24, 2004, 04:42 PM

Originally posted by wadesworld:
So, we panic'd when trying to access an instruction, next when trying to access data, and finally there was some bad data object in memory.

Yep, I'd say it sounds like RAM.

Wade

If RAM doesn't fix it, it could be the processor module (L2 cache, etc...).

Gul Banana · Jan 24, 2004, 06:28 PM

I really should polish up and publicise kpdecode... oh well. For now:

Code:
Found 3 kernel panics.
Wed Jan 21 20:24:33 2004:
        Backtrace 1:
                0x000cd2e4: _vn_rdwr
                0x00234990: _load_machfile
                0x00234740: _load_machfile
                0x00207614: _execve
                0x0023dd24: _unix_syscall
                0x00093d20: _shandler
                0x000a0009: _dbgDispLL
        Backtrace 2:
                0x000833b8: _print_backtrace
                0x0008389c: _Debugger
                0x0001ed8c: _panic
                0x000908c0: _trap
                0x00093b8c: _thandler
        Backtrace 3:
                0x000cd2e4: _vn_rdwr
                0x00234990: _load_machfile
                0x00234740: _load_machfile
                0x00207614: _execve
                0x0023dd24: _unix_syscall
                0x00093d20: _shandler
                0x000a0009: _dbgDispLL
Thu Jan 22 21:34:49 2004:
        Backtrace 1:
                0x00064660: _vm_map_lookup_locked
                0x00058d5c: _vm_fault
                0x00090cf0: _trap
                0x00093b8c: _thandler
        Backtrace 2:
                0x000833b8: _print_backtrace
                0x0008389c: _Debugger
                0x0001ed8c: _panic
                0x000908c0: _trap
                0x00093b8c: _thandler
        Backtrace 3:
                0x00064660: _vm_map_lookup_locked
                0x00058d5c: _vm_fault
                0x00090cf0: _trap
                0x00093b8c: _thandler
Fri Jan 23 08:50:50 2004:
        Backtrace 1:
                0x000833b8: _print_backtrace
                0x0008389c: _Debugger
                0x0001ed8c: _panic
                0x0000cc50: _dp_memory_object_data_request
                0x00057af8: _vm_fault_page
                0x00059928: _vm_fault
                0x00090d78: _trap
                0x00093b8c: _thandler

The second and third are in the virtual memory system. The first is a bit more alarming: the kernel died when trying to load an executable, specifically when accessing the filesystem to map it into memory. It does look very very likely that you've got bad RAM...