Welcome to the MacNN Forums.

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

You are here: MacNN Forums > Software - Troubleshooting and Discussion > Mac OS X > Anyone kind enough to explain this kernel panic log?

Anyone kind enough to explain this kernel panic log?
Thread Tools
Dedicated MacNNer
Join Date: May 2002
Location: Tokyo
Status: Offline
Reply With Quote
Mar 10, 2003, 08:08 PM
 
My (recently 'Switched') boss's 2 week old G4 has started freezing several times a day, and he's not impressed. I've never had any problems with my system, and haven't a clue how to go about fixing his. The problems started around the time Photoshop, Illustrator and some extra RAM were installed. It seems to freeze most often upon waking from sleep.

I'd really appreciate it if someone could point me in the right direction. Thanks. (1GHz G4 768MB 10.2.4)

Panic Log:

Tue Mar 11 10:33:09 2003

Unresolved kernel trap(cpu 0): 0x200 - Machine check DAR=0x11d5bb98 PC=0x0005983c
Latest crash info for cpu 0:
___Exception state (sv=0x1EE12C80)
______PC=0x0005983C; MSR=0x00149030; DAR=0x11D5BB98; DSISR=0x40000000; LR=0x00070E94; R1=0x11D2BC70; XCP=0x00000008 (0x200 - Machine check)
______Backtrace:
_________0x00000008 0x001F52FC 0x000B2F5C 0x001F50D4 0x001F515C 0x001E20A8 0x001E9A48 0x0020E59C
_________0x00092110 0x20834012
Proceeding back via exception chain:
___Exception state (sv=0x1EE12C80)
______previously dumped as "Latest" state. skipping...
___Exception state (sv=0x1F247280)
______PC=0x900485B4; MSR=0x0200F030; DAR=0x19278764; DSISR=0x42000000; LR=0x000028C8; R1=0xBFFFFE40; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 6.4:
Wed Jan 29 18:50:42 PST 2003; root:xnu/xnu-344.26.obj~1/RELEASE_PPC

panic(cpu 0): 0x200 - Machine check
Latest stack backtrace for cpu 0:
______Backtrace:
_________0x00084FAC 0x000853DC 0x00027FA8 0x0008EE68 0x00091F78
Proceeding back via exception chain:
___Exception state (sv=0x1EE12C80)
______PC=0x0005983C; MSR=0x00149030; DAR=0x11D5BB98; DSISR=0x40000000; LR=0x00070E94; R1=0x11D2BC70; XCP=0x00000008 (0x200 - Machine check)
______Backtrace:
_________0x00000008 0x001F52FC 0x000B2F5C 0x001F50D4 0x001F515C 0x001E20A8 0x001E9A48 0x0020E59C
_________0x00092110 0x20834012
___Exception state (sv=0x1F247280)
______PC=0x900485B4; MSR=0x0200F030; DAR=0x19278764; DSISR=0x42000000; LR=0x000028C8; R1=0xBFFFFE40; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 6.4:
Wed Jan 29 18:50:42 PST 2003; root:xnu/xnu-344.26.obj~1/RELEASE_PPC
     
Addicted to MacNN
Join Date: Aug 2000
Location: Retired
Status: Offline
Reply With Quote
Mar 10, 2003, 08:47 PM
 
There isn't much there to work with, sorry.
Power Macintosh Dual G4
SGI Indigo2 6.5.21f
     
Dedicated MacNNer
Join Date: May 2002
Location: Tokyo
Status: Offline
Reply With Quote
Mar 10, 2003, 09:21 PM
 
Oh dear. I've got a couple more, in the hope that these might yield something... If not, can anyone suggest my best plan of action?

Fri Mar 7 10:41:45 2003

Unresolved kernel trap(cpu 0): 0x200 - Machine check DAR=0x0194e3b8 PC=0x0008abb4
Latest crash info for cpu 0:
Exception state (sv=0x1F67D500)
PC=0x0008ABB4; MSR=0x00141000; DAR=0x0194E3B8; DSISR=0x40000000; LR=0x00087B90; R1=0x11D73610; XCP=0x00000008 (0x200 - Machine check)
Backtrace:
0x00087D40 0x00086A20 0x00065C44 0x00065EB4 0x0003857C 0x001DB0F0 0x001E504C 0x0002686C
0x000923F4 0x00028458 0x0008F6B0 0x0008F46C 0x00091F78
Proceeding back via exception chain:
Exception state (sv=0x1F67D500)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x1980BC80)
PC=0x91A88210; MSR=0x0000D030; DAR=0x50415448; DSISR=0x40000000; LR=0x969F3D4C; R1=0xBFFFF3B0; XCP=0x00000003 (Unknown)

Kernel version:
Darwin Kernel Version 6.4:
Wed Jan 29 18:50:42 PST 2003; root:xnu/xnu-344.26.obj~1/RELEASE_PPC


panic(cpu 0): 0x200 - Machine check
Latest stack backtrace for cpu 0:
Backtrace:
0x00084FAC 0x000853DC 0x00027FA8 0x0008EE68 0x00091F78
Proceeding back via exception chain:
Exception state (sv=0x1F67D500)
PC=0x0008ABB4; MSR=0x00141000; DAR=0x0194E3B8; DSISR=0x40000000; LR=0x00087B90; R1=0x11D73610; XCP=0x00000008 (0x200 - Machine check)
Backtrace:
0x00087D40 0x00086A20 0x00065C44 0x00065EB4 0x0003857C 0x001DB0F0 0x001E504C 0x0002686C
0x000923F4 0x00028458 0x0008F6B0 0x0008F46C 0x00091F78
Exception state (sv=0x1980BC80)
PC=0x91A88210; MSR=0x0000D030; DAR=0x50415448; DSISR=0x40000000; LR=0x969F3D4C; R1=0xBFFFF3B0; XCP=0x00000003 (Unknown)

Kernel version:
Darwin Kernel Version 6.4:
Wed Jan 29 18:50:42 PST 2003; root:xnu/xnu-344.26.obj~1/RELEASE_PPC



*********

Fri Mar 7 13:25:39 2003

Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x0000001c PC=0x0025ac1c
Latest crash info for cpu 0:
Exception state (sv=0x19702C80)
PC=0x0025AC1C; MSR=0x00009030; DAR=0x0000001C; DSISR=0x40000000; LR=0x0025AC00; R1=0x11E4BCB0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x0025AC00 0x00214BE4 0x00244900 0x0007D148 0x0002A28C 0x00024C00 0x00024FFC 0x00092318
0x00410041
Proceeding back via exception chain:
Exception state (sv=0x19702C80)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x1981BA00)
PC=0x90073C28; MSR=0x0200F030; DAR=0xE1719000; DSISR=0x42000000; LR=0x90005F70; R1=0xBFFFF160; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 6.4:
Wed Jan 29 18:50:42 PST 2003; root:xnu/xnu-344.26.obj~1/RELEASE_PPC


panic(cpu 0): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x00084FAC 0x000853DC 0x00027FA8 0x0008EE68 0x00091F78
Proceeding back via exception chain:
Exception state (sv=0x19702C80)
PC=0x0025AC1C; MSR=0x00009030; DAR=0x0000001C; DSISR=0x40000000; LR=0x0025AC00; R1=0x11E4BCB0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x0025AC00 0x00214BE4 0x00244900 0x0007D148 0x0002A28C 0x00024C00 0x00024FFC 0x00092318
0x00410041
Exception state (sv=0x1981BA00)
PC=0x90073C28; MSR=0x0200F030; DAR=0xE1719000; DSISR=0x42000000; LR=0x90005F70; R1=0xBFFFF160; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 6.4:
Wed Jan 29 18:50:42 PST 2003; root:xnu/xnu-344.26.obj~1/RELEASE_PPC



*********

Mon Mar 10 10:29:51 2003

Unresolved kernel trap(cpu 0): 0x200 - Machine check DAR=0x11d5bb98 PC=0x0005983c
Latest crash info for cpu 0:
Exception state (sv=0x1EE12C80)
PC=0x0005983C; MSR=0x00149030; DAR=0x11D5BB98; DSISR=0x40000000; LR=0x00070E94; R1=0x11D2BC70; XCP=0x00000008 (0x200 - Machine check)
Backtrace:
0x00000008 0x001F52FC 0x000B2F5C 0x001F50D4 0x001F515C 0x001E20A8 0x001E9A48 0x0020E59C
0x00092110 0x20834012
Proceeding back via exception chain:
Exception state (sv=0x1EE12C80)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x1F247280)
PC=0x900485B4; MSR=0x0200F030; DAR=0x19278764; DSISR=0x42000000; LR=0x000028C8; R1=0xBFFFFE40; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 6.4:
Wed Jan 29 18:50:42 PST 2003; root:xnu/xnu-344.26.obj~1/RELEASE_PPC


panic(cpu 0): 0x200 - Machine check
Latest stack backtrace for cpu 0:
Backtrace:
0x00084FAC 0x000853DC 0x00027FA8 0x0008EE68 0x00091F78
Proceeding back via exception chain:
Exception state (sv=0x1EE12C80)
PC=0x0005983C; MSR=0x00149030; DAR=0x11D5BB98; DSISR=0x40000000; LR=0x00070E94; R1=0x11D2BC70; XCP=0x00000008 (0x200 - Machine check)
Backtrace:
0x00000008 0x001F52FC 0x000B2F5C 0x001F50D4 0x001F515C 0x001E20A8 0x001E9A48 0x0020E59C
0x00092110 0x20834012
Exception state (sv=0x1F247280)
PC=0x900485B4; MSR=0x0200F030; DAR=0x19278764; DSISR=0x42000000; LR=0x000028C8; R1=0xBFFFFE40; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 6.4:
Wed Jan 29 18:50:42 PST 2003; root:xnu/xnu-344.26.obj~1/RELEASE_PPC
     
Mac Elite
Join Date: May 2002
Status: Offline
Reply With Quote
Mar 10, 2003, 09:59 PM
 
Code:
Fri Mar 7 10:41:45 2003: Backtrace 1: 0x00087d40: _mapping_remove 0x00086a20: _pmap_remove 0x00065c44: _vm_map_delete 0x00065eb4: _vm_map_remove 0x0003857c: _task_terminate_internal 0x001db0f0: _exit1 0x001e504c: _bsd_ast 0x0002686c: _ast_taken 0x000923f4: .L_thread_exc_ret_check_ast 0x00028458: _exception 0x0008f6b0: _doexception 0x0008f46c: _trap 0x00091f78: .L_call_trap Backtrace 2: 0x00084fac: _print_backtrace 0x000853dc: _Debugger 0x00027fa8: _panic 0x0008ee68: _trap 0x00091f78: .L_call_trap Backtrace 3: 0x00087d40: _mapping_remove 0x00086a20: _pmap_remove 0x00065c44: _vm_map_delete 0x00065eb4: _vm_map_remove 0x0003857c: _task_terminate_internal 0x001db0f0: _exit1 0x001e504c: _bsd_ast 0x0002686c: _ast_taken 0x000923f4: .L_thread_exc_ret_check_ast 0x00028458: _exception 0x0008f6b0: _doexception 0x0008f46c: _trap 0x00091f78: .L_call_trap Fri Mar 7 13:25:39 2003: Backtrace 1: 0x0025ac00: OSDictionary::serialize(OSSerialize*) const 0x00214be4: IORegistryEntry::serializeProperties(OSSerialize*) const 0x00244900: _is_io_registry_entry_get_properties 0x0007d148: __Xio_registry_entry_get_properties 0x0002a28c: _ipc_kobject_server 0x00024c00: _mach_msg_overwrite_trap 0x00024ffc: _mach_msg_trap 0x00092318: .L_syscall_got_args 0x00410041: _rld_env Backtrace 2: 0x00084fac: _print_backtrace 0x000853dc: _Debugger 0x00027fa8: _panic 0x0008ee68: _trap 0x00091f78: .L_call_trap Backtrace 3: 0x0025ac00: OSDictionary::serialize(OSSerialize*) const 0x00214be4: IORegistryEntry::serializeProperties(OSSerialize*) const 0x00244900: _is_io_registry_entry_get_properties 0x0007d148: __Xio_registry_entry_get_properties 0x0002a28c: _ipc_kobject_server 0x00024c00: _mach_msg_overwrite_trap 0x00024ffc: _mach_msg_trap 0x00092318: .L_syscall_got_args 0x00410041: _rld_env
The 10:41 one sounds like bad RAM. The second one is slightly more confusing - it could be the same thing, but it also could be a device driver issue.
[vash:~] banana% killall killall
Terminated
     
Dedicated MacNNer
Join Date: May 2002
Location: Tokyo
Status: Offline
Reply With Quote
Mar 10, 2003, 10:41 PM
 
Is bad RAM a one-off faulty module, or is it a case of brand incompatability? If it were the RAM, could it be exchanged at the shop it was bought at for the same product again, fixing the issue, or would the problem remain until a different maker's RAM was used?
     
Addicted to MacNN
Join Date: Oct 2001
Location: Yokohama, Japan
Status: Offline
Reply With Quote
Mar 11, 2003, 12:24 AM
 
Originally posted by superblue:
is it a case of brand incompatability?
Uh, I don't think that happens. RAM is RAM. You can have bad RAM, but that's just bad RAM, not an inter-brand problem.
     
Mac Elite
Join Date: Feb 2002
Location: USA
Status: Offline
Reply With Quote
Mar 11, 2003, 12:29 AM
 
All new Macs come with the Apple Hardware Test CD. Use it and see if any errors are encountered. I'd suspect bad RAM though. Replace it and perform a format and restore.
     
   
Thread Tools
Forum Links
Forum Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Top
Privacy Policy
All times are GMT -5. The time now is 07:45 PM.
All contents of these forums © 1995-2011 MacNN. All rights reserved.
Branding + Design: www.gesamtbild.com
vBulletin v.3.8.7 © 2000-2011, Jelsoft Enterprises Ltd., Content Relevant URLs by vBSEO 3.3.2